Comment 2 for bug 495085
Revision history for this message
| Scott James Remnant (Canonical) (canonical-scott) wrote | #2 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
0e1f616
(Get the code!)
This is caused by plymouth actually restarting while X is trying to start, and the two colliding - if you press some Alt+Fn keys, you find your X server on one of them ;)