I don't think It's an usplash issue, and mainly that usplash could
'reboot' the machine on his own.
fsck is managed by /lib/init/usplash-fsck-functions.sh (package initscripts)
and is his aim to handling fsck error
Perhaps an error like "UNEXPECTED INCONSISTENCY" isn't handled by initstcripts,
that doesn't show anything about it??
I feel that the right package that should handle this report is initscript.
I'm going to invalid in usplash and assign to initscript. Please feel free
everybody to correct me if i'm not clear or even wrong.
** Changed in: usplash (Ubuntu)
Status: New => Invalid
--
usplash cause reboot when fsck routine check fails
https://bugs.launchpad.net/bugs/197302
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
