Public bug reported:
Binary package hint: ubiquity
Booting a system which has been "oem-config-prepare quiet" prepped, or
just touching /var/lib/oem-config/run should enable and run a relevant
oem-config frontend on first boot.
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/oem-config/run did
not exist or whether it ran to completion). This implies a whole new
event, perhaps?
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/oem-config/run and reboot, and see how it doesn't do what you
expect...
** Affects: ubiquity (Ubuntu)
Importance: Undecided
Status: New
--
maverick oem-config gtk frontend does not start on first boot because gdm runs
before it
https://bugs.launchpad.net/bugs/644638
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
