Thanks for sticking with this even though you guys have found circumventions. If someone can fix this without adding boot parameters, etc. -- if it just works-- it will be better for many Ubuntu users.
@Jamie: It looks like :2.log.1 is what I would expect for the bug we have been hunting. It was started quiet splash and crashed on VT2 after hitting Enter key rather than hitting the 2 key. :0.log.2 started on VT7 and X couldn't get started. It suggests looking at the corresponding Xorg.0.log file and some other files. It says no screens are available. It may mean what you were trying in booting it up wasn't giving you a good graphic environment to use, but I don't know that. The complaint it has is: (EE) Sep 07 22:16:47 NVIDIA(0): Failed to initialize the NVIDIA kernel module. Please see the (EE) Sep 07 22:16:47 NVIDIA(0): system's kernel log for additional error messages and (EE) Sep 07 22:16:47 NVIDIA(0): consult the NVIDIA README for details. (EE) NVIDIA(0): *** Aborting *** (EE) Screen(s) found, but none have a usable configuration. Perhaps it is a non-drm nvidia boot where the X driver and kernel driver don't match? I really don't know, but it isn't what we have been looking at and doesn't appear to have anything to do with plymouth or splash screens. :0.log.3 looks like a good splash start on VT8 :0.log.4 looks like an X crash during one of your VGA= experiments. I can't tell what the crash was and don't know if it is the same as what we have been looking at. It doesn't match :0.log.2, though. :1.log.2 looks like a good session on VT8. :1.log.3 looks like a session on VT2 that ended before it crashed The rest are unremarkable as far as I can tell right now. Here's the thing. The file I was most interested in seeing was your plymouth-debug.log. The one you posted shows the same error message Dino and I have (I'm not crashing). It shows the same variation in error messages we expected (you are using the fourth renderer). It shows gdm knows it is running and asks it to get ready to go away. But then it seems to end rather abruptly, unlike Dino's. If you copies and pasted it could you have missed some of it? Could you put your system back to the original state except for asking for plymouth:debug and attaching another so we can confirm it stops there. If that's all there is then plymouth crashed or was killed by another process before gdm started X, and that differs from Dino's case where it's the same to the point where gdm asks plymouth to get ready to go away (deactivate). THEN Dino's (and mine) ask it if it is controlling the VT you are looking at, and then starts X and later asks plymouth to quit. @Dino: Xorg.0.log looks to me like a Enter key crash on VT1, but when you booted without the splash or quiet parameters. I assume you didn't see a splash screen that time (plymouth would still run, I believe). Good confirming 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
