@ Loong Jin

please accept my excuse regarding the statement that "fixing the bug in
Lucid did take too long" - 10 days ist really fast.

On the other hand - and that is probably why people including me get
upset so easily - the real root cause is something different and in no
way addressed to you personally - it is related to plymouth:

I followed the development of Lucid since alpha stage and experienced
that an enormous effort was put into plymouth to get it working somehow.
This eye-candy splash screen had priority over functional features and
still today plymouth is causing troubles (the normal user can't un-
install it because artificially tied to mountall and cryptsetup and
Canonical refuses to correct dependencies).

A lot of bug reports like this one are in my opinion related to plymouth
which requires to patch 'mountall' and 'cryptsetup'. And these are
really patches and no fixes, because they all have to consider not to
disturb buggy plymouth. The logical way to solve this issues/bugs would
be to purge plymouth and set up a good functional system.

Best regards, Ingo

-- 
fsck progress stalls at boot, plymouthd/mountall eats CPU
https://bugs.launchpad.net/bugs/571707
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