Here is the start on:
start on ((filesystem
and runlevel [!06]
and started dbus
and (drm-device-added card0 PRIMARY_DEVICE_FOR_DISPLAY=1
or stopped udev-fallback-graphics))
or runlevel PREVLEVEL=S)
I suspect drm-device-added card0 PRIMARY_DEVICE_FOR_DISPLAY=1 or stopped
udev-fallback-graphics is emitting too soon.
here is udev-fallback-graphics:
start on (startup and
(graphics-device-added PRIMARY_DEVICE_FOR_DISPLAY=1
or drm-device-added PRIMARY_DEVICE_FOR_DISPLAY=1
or stopped udevtrigger or container))
That bare 'card0' on the drm-device-added event is quite puzzling. Is it
possible that it is simply matching as 'drm-device-added' and a second,
non primary graphics chip is causing the issue? That might explain it.
The timeline for these events is pretty complex so it will likely take
some deep thought.
Nothing in the upstart man pages suggests this syntax, event, bareword,
variable, is valid or what it might mean. It seems to have been cargo
culted to KDM as well, and come from gdm in lucid originally.
Can somebody who is affected try removing 'card0' and see if that fixes
the problem?
I suspect this might be related to bug #936552 which also has to do with
lightdm seemingly starting too soon.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/969489
Title:
lightdm tries (and fails) to start too early?
To manage notifications about this bug go to:
https://bugs.launchpad.net/upstart/+bug/969489/+subscriptions
--
ubuntu-bugs mailing list
[email protected]
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
