dmesg shows the below output. plymouth is clearly being stopped by lightdm (not by /etc/init/plymouth-stop.conf), so we're not hitting a race in the plymouth jobs. But after stopping plymouth, lightdm hits the problem with the X server and exits.
I think this is clearly a problem with either the kernel or with lightdm. [ 15.801383] init: lightdm goal changed from stop to start [ 15.801430] init: lightdm state changed from waiting to starting [ 15.801559] init: plymouth-splash goal changed from stop to start [ 15.801605] init: plymouth-splash state changed from waiting to starting [...] [ 15.803513] init: plymouth-stop goal changed from stop to start [ 15.803563] init: plymouth-stop state changed from waiting to starting [...] [ 15.806338] init: plymouth-stop state changed from starting to pre-start [ 15.806828] init: plymouth-stop pre-start process (1133) [...] [ 15.809173] init: plymouth-stop pre-start process (1133) exited normally [ 15.809314] init: plymouth-stop state changed from pre-start to spawned [ 15.809398] init: plymouth-stop state changed from spawned to post-start [ 15.809477] init: plymouth-stop state changed from post-start to running [...] [ 15.811474] init: lightdm state changed from starting to pre-start [ 15.811752] init: lightdm state changed from pre-start to spawned [ 15.812406] init: lightdm main process (1136) [ 15.812499] init: lightdm state changed from spawned to post-start [ 15.812818] init: lightdm state changed from post-start to running [...] [ 15.817462] init: plymouth-splash state changed from starting to pre-start [ 15.817511] init: plymouth-splash state changed from pre-start to spawned [ 15.820635] init: plymouth-splash main process (1146) [ 15.820690] init: plymouth-splash state changed from spawned to post-start [ 15.820908] init: plymouth-splash state changed from post-start to running [...] [ 16.573039] init: plymouth-splash main process (1146) exited normally [ 16.573104] init: plymouth-splash goal changed from start to stop [ 16.573184] init: plymouth-splash state changed from running to stopping [ 16.573242] init: Handling stopping event [ 16.573332] init: plymouth-splash state changed from stopping to killed [ 16.573382] init: plymouth-splash state changed from killed to post-stop [ 16.573430] init: plymouth-splash state changed from post-stop to waiting [ 16.573537] init: Handling stopped event [ 16.591136] init: plymouth main process (259) exited normally [ 16.591194] init: plymouth goal changed from start to stop [ 16.591264] init: plymouth state changed from running to stopping [...] [ 17.610321] init: lightdm main process (1136) terminated with status 1 [ 17.610429] init: lightdm goal changed from start to stop [ 17.610490] init: lightdm state changed from running to stopping [...] [ 16.591619] init: plymouth state changed from stopping to killed [ 16.591669] init: plymouth state changed from killed to post-stop [ 16.591721] init: plymouth state changed from post-stop to waiting ** Package changed: plymouth (Ubuntu Quantal) => lightdm (Ubuntu Quantal) -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1066883 Title: [Macmini 5,1] Fatal server error: Can not run in framebuffer mode on reboot To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/lightdm/+bug/1066883/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
