The forced fsck is really annoying, and dropping back to text mode and not being able to easily stop the check makes it worse. I like Huygens suggestions and would formulate it as this:
Short-term fix: - don't do the check if laptop runs on battery - make it easier to cancel a check - make it possible to tell the system to not run proposed fsck check now but do it on next boot - maybe integrate progress reporting with usplash Long-term solution: do such checks at shutdown. On shutdown, GNOME shutdown dialog could ask the user whether he'd like the system to do some health checks before switching off (I think asking would be nice so users are not surprised, but exact usability details are another topic). The system could then do fsck, maybe even start memcheck86 afterwards (would probably need some heavy magic), and do whatever other low-level checks there are. It would be important that the user can still switch off the machine during the checks without problems. Results of the checks could then be evaluated by the system after next boot, and a tray notification (or whatever) can tell him that the disk has problems, suggesting a solution. Guess this long-term solution needs an own spec :-) Note: the problem about dropping back to text mode for fsck is also described in bugs 38303 and 67453 , and the problem about not being able to cancel is described in bug 65683 . -- Should be warned of upcoming forced fsck https://bugs.launchpad.net/bugs/22460 You received this bug notification because you are a member of Ubuntu Bugs, which is a direct subscriber. -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
