maverick oem-config gtk frontend does not start on first boot because gdm runs before it
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Genesi EfikaMX Support Project |
Confirmed
|
Medium
|
Matt Sealey | ||
ubiquity (Ubuntu) |
Confirmed
|
Undecided
|
Unassigned | ||
Bug Description
Binary package hint: ubiquity
Booting a system which has been "oem-config-prepare quiet" prepped, or just touching /var/lib/
However, this does not happen. The scripts for oem-config and gdm conflict such that gdm starts first and takes on an Xorg instance, which then when oem-config starts, simply cannot run (because gdm is running on Xorg already and it cannot create another one on VT7).
Ideally oem-config should be run by upstart before gdm has had a chance to get there, maybe by making sure that gdm depends on oem-config having already been run (whether it gave up because /var/lib/
syslog, Xorg.log etc. do not show any of the information I saw spewed to VT1 once GDM had started up and oem-config had bailed out, but it was basically the usual messages you get when Xorg has been started twice. Since I cannot paste from the framebuffer console here, I guess this will have to be as much information as I can give.
To reproduce: probably make yourself a rootstock that has xubuntu-desktop or install a minimal or standard system and then aptitude install xubuntu-desktop on top. Then, install oem-config-gtk and touch /var/lib/
Changed in efikamx: | |
status: | New → Confirmed |
assignee: | nobody → Matt Sealey (mwsealey) |
importance: | Undecided → Medium |
The oem-config upstart job is set to "start on gdm", which means that GDM should never start before it. Can you please make sure you have the latest oem-config, then boot with --debug on the kernel command line? This will add upstart job debugging information to your logs (/var/log/syslog, /var/log/ oem-config. log, etc), which I would then ask you to attach to this bug report.
Thanks!