© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
0e1f616
(Get the code!)
No, this is not a re-emergence of bug #532047. Something is causing X to be started on VT1 where it never should be. However, the submitter suggests this is related to disk encryption; I'm using crypted disks here and have never seen this problem with natty. Someone needs to reproduce this and work out why X is starting on the wrong VT.