thanks Bryce. One question: this workaround results in a flip-flap between console mode / graphical mode during boot, and a 5 to 20 seconds delay in the boot. This is better than lightdm failing to start, but not the best we can aim... So my question is: should I open another bug report, maybe mentioning EACCESS error code ? Are we just going on with this workaround, waiting for Mir to fix everything (and probably break some also :-) ) ?
-- You received this bug notification because you are a member of Ubuntu-X, which is subscribed to libdrm in Ubuntu. https://bugs.launchpad.net/bugs/982889 Title: X trying to start before plymouth has finished using the drm driver To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/libdrm/+bug/982889/+subscriptions _______________________________________________ Mailing list: https://launchpad.net/~ubuntu-x-swat Post to : ubuntu-x-swat@lists.launchpad.net Unsubscribe : https://launchpad.net/~ubuntu-x-swat More help : https://help.launchpad.net/ListHelp