GTK mini-iso can't start X
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
kickseed (Ubuntu) |
Fix Released
|
High
|
Colin Watson |
Bug Description
When I boot the GTK version of mini-iso (http://
The same problem emerges when I build debian-installer package manually.
The X.log.0 errors with:
(EE) Failed to load module "Intel" (on real hardware)
(EE) Failed to load module "vboxvideo" (on a VirtualBox VM)
(EE) Failed to load module "vesa" (module does not exist, 0)
(EE) FBDEV(0): FBIOBLANK: Invalid argument
(EE) FBDEV(0): FBIOBLANK: Invalid argument
The driver related messages are expected to be there - the mini-iso does not contain all the Xorg drivers, but is expected to start with FBDEV. However, it seems that either FBDEV has some issues, or there is something else that crashes the X server.
The problem is not hardware related, as I managed to run the X server on a fully-installed system with the fbdev driver. Also, the Debian squeeze/wheezy GTK mini-isos work flawlessly (aside from the fact you can't install Ubuntu with that).
So, I believe that the debian-installer package or some of the udebs it pulls has a bug that causes this behaviour. I can try some more digging, but I would need to know where to dig.
Related branches
affects: | debian-installer (Ubuntu) → kickseed (Ubuntu) |
Changed in kickseed (Ubuntu): | |
assignee: | nobody → Colin Watson (cjwatson) |
importance: | Undecided → High |
status: | New → Triaged |
This bug was fixed in the package kickseed - 0.57ubuntu1
---------------
kickseed (0.57ubuntu1) precise; urgency=low
* Resynchronise with Debian. Remaining changes:
- Add basic RAID support. (LVM-on-RAID won't quite work yet.)
- Add basic iSCSI support.
kickseed (0.57) unstable; urgency=low
* Disable kickseed for now when using the GTK frontend, as otherwise it
starts up an initial X client which exits quickly and causes the Xserver
to exit (LP: #939278).
-- Colin Watson <email address hidden> Tue, 06 Mar 2012 11:40:10 +0000