© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
1b1ed1a
(Get the code!)
TJ wrote:
"Well it gets more confusing! Both logs show the device nodes created. Are you *sure* the failed_log isn't accidentally a successful run?"
No, I'm not sure. That's what I was saying in #49. After spending several hours doing reboot cycles, I got a a few failures to boot properly, but most of them were cases where I didn't even get a login prompt after my system was done booting. As I said in #49, the case I posted was one of the ones from early on, where I wasn't paying proper attention and wasn't sure I noticed correctly what was going on. That was the only one where it failed to start X, but also gave me a login prompt.
Recently when I've rebooted normally (not in recovery mode), the failure to start x had been happening fairly often. Here are some statistics from a few days ago:
34 successful boots
2 boots that didn't result in a login prompt
6 boots that gave a login prompt but didn't start X
I see several possibilities here:
(a) There are two separate bugs, one of which causes X to fail, and one which causes me not even to get a login prompt.
(b) Same as a, but the X bug doesn't occur in recovery mode.
(c) There is only one bug, and I was just "unlucky" in not being able to reproduce it today after several hours of rebooting.
It takes less time for me to simply reboot that it does to go through the whole procedure involving recovery mode and logging. I'm going to try doing 30 cycles the quick way, and see if the X problem is still occurring or not.