On Sat, Sep 11, 2010 at 08:01:10AM -0000, István Miklós Antal wrote: > > What version of ureadahead do you have installed on this system?
> Latest up to date version. (dist-upgrade) Please tell me the version number, don't just tell me you have "the latest". > I assume it should be some issue with plymouth and my proprietary nvidia > driver. As I said, nuking plymouthd(see temp. fix) works so it's gotta > be some plymouth related issue. No, having the kernel OOM-kill plymouthd is *a bug in whatever triggers the OOM killer*. If the kernel hard-kills the process that's controlling the console, it's no surprise that the console is left in an inconsistent state. If you want to eliminate all possibility of plymouth leaving the console in an unusable state when some external bug causes it to be hard-killed, you can boot without the 'splash' option to disable plymouth graphics. But if you want to fix the bug, we need to find out why the OOM killer is triggering in a situation where this should never occur. > This is not only a bug that makes a machine hang on boot, this is also a > design flaw, as I pointed out it's wrong for unrelated packages to > depend on this, It is no more a design flaw that you cannot remove plymouth than it is that you cannot remove upstart. -- Steve Langasek Give me a lever long enough and a Free OS Debian Developer to set it on, and I can move the world. Ubuntu Developer http://www.debian.org/ slanga...@ubuntu.com vor...@debian.org -- 2 out of 3 boots crash probably because of plymouth https://bugs.launchpad.net/bugs/613027 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
