More test results, log, and another workaround:
- booting with "plymouth:debug" added to boot line, but "quiet splash" removed, 
results in booting to VT7 every time, and no crashes (sample plymouth debug log 
attached).
- booting with "quiet plymouth:debug" (but no "splash"), same results--boots to 
VT7 every time, and no crashes.
- booting with "quiet splash plymouth:debug" results in a frozen splash 
screen--splash logo, 5 dots turn red, then nothing at all.
- simply removing the "quiet splash" from boot line (and no "plymouth:debug" 
either) results in bug behavior--boots to VT2 and eventually crashes on 
pressing enter (again, rarely the first time though, maybe once).

@John: Unfortunately, this means I really can't provide the plymouth-
debug.log you're looking for. The only condition that allows me to boot
with plymouth debugging seems to be another mysterious workaround to
this issue. Again, is it possible that simply adding the plymouth:debug
option may be just enough to delay whatever race condition might be
causing this bug? I'm clueless to why I'm getting a splash freeze with
plymouth:debug.

** Attachment added: "plymouth-debug_20100908-1347.log"
   
https://bugs.launchpad.net/ubuntu/+source/xserver-xorg-video-ati/+bug/625239/+attachment/1558112/+files/plymouth-debug_20100908-1347.log

-- 
X starts on wrong tty: pressing enter after 5 minutes crashes X
https://bugs.launchpad.net/bugs/625239
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to