Comment 3 for bug 197302

Revision history for this message
Andrea Gasparini (gaspa) wrote :

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.