*** This bug is a duplicate of bug 982889 ***
https://bugs.launchpad.net/bugs/982889
At any rate I think the fix is going to be one and the same...
** This bug has been marked a duplicate of bug 982889
X trying to start before plymouth has finished using the drm driver
--
You received
Finally this is not a duplicate of #982889, although it belongs to the
same class of race condition in X bugs. So I removed duplicate info.
** This bug is no longer a duplicate of bug 982889
X trying to start before plymouth has finished using the drm driver
--
You received this bug
It is that bug. What's changed in the meantime is Xorg now has a
platform probe first so hits the error even earlier.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1129220
Title:
Fails to boot to
*** This bug is a duplicate of bug 982889 ***
https://bugs.launchpad.net/bugs/982889
Thanks Chris. After searching a bit, I guess my bug is a duplicate of #982889.
Notice this is concomitent with me upgrading my SSD to a faster one (840pro).
Might explain why I now meet the race condition...
Here is the Xorg.0.log file just after it fails.
Error lines are:
[ 8.460] (EE) Screen 0 deleted because of no matching config section.
[ 8.460] (II) UnloadModule: vesa
[ 8.460] (EE) Screen 0 deleted because of no matching config section.
[ 8.460] (II) UnloadModule: modesetting
[
Here is a Xorg.0.log after a successful 'sudo start lightdm'.
** Attachment added: Successful Xorg.0.log
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-intel/+bug/1129220/+attachment/3535131/+files/Xorg.0.log
--
You received this bug notification because you are a member of
[ 3.648] setversion 1.4 failed = plymouth race
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1129220
Title:
Fails to boot to X, but starting lightdm afterward works
To manage notifications
