> What version of ureadahead do you have installed on this system? Latest up to date version. (dist-upgrade)
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. > You would stand a better chance of getting a response to your bug report if > you didn't lead with comments like: > You aren't exactly encouraging developers to focus their attention on your > bug with this attitude, and if it's not simply a duplicate of the ureadahead > problem, this is likely to be a bug that requires a lot of attention to > resolve. I am not reporting bugs like these for myself, I can easily hack around them, I am reporting bugs like these, so that the developers know that they have a problem. The developers can simply ignore me it's really their decision, but then they will be the ones who get bad reputation from people who are bitten by the same issues. I didn't have much luck here with other "attitudes" either, LP is really a bad place to report bugs, still I am doing it in hopes that it will get better if people use it. 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, if I would manually remove plymouth every other package would still work, so in reality those packages do not depend on it. Overall I feel that plymouth was rushed in just like a lot of other software(PulseAudio,GRUB2 etc.). -- 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
