Red Hat Bugzilla – Bug 471089
fscking makes it seem like the computer has crashed
Last modified: 2009-12-18 01:48:59 EST
If the system decides it needs to fsck, the plymouth progress bar reaches 100% and then just stays there for a very very long time with no further feedback, making it seem like the system has crashed
how old is your plymouth? that shouldn't be true.
I've just had a fsck with plymouth-0.6.0-0.2008.11.11.2.fc11.i386 and the solar plugin. The progressbar reaches to the end, the flares are flaring, and the disk is spinning for quite a while. I don't feel like only the flares and the disk activity are enough to give the user a good feeling about what's going on.
I'd done a yum update almost immediately before rebooting.
(This is with text-mode plymouth, but I guess from comment #2 it happens with graphical plymouth too.)
oh I see, you mean the fsck adds an unexpected delay to boot up that makes the progress indicator unreliable.
I thought you meant it was hanging indefinitely while an emergency shell was active in the background or something.
We probably need to expose fsck as another hook that the splash plugins can key off of and then make them do something different. We also probably need to discount fsck time from boot progress.
I don't think we'll get to either before GA though.
thinking about this more, maybe for F10 we could just always --hide-splash / --show-splash around the fsck calls.
Bill, what do you think?
Due to how fsck works, that would involve a hide/show cycle on every reboot - we don't know that it's going to be a 'long' fsck until after it's already started.
Might be worth playing with some of the fsck options to see if we can do a check-but-dont-fix call first.
Anyway, probably not going to make the F10 boat at this point, and we can probably do something more integrated for F11.
Currently the progress bar only changes progress speed when it recieves an event either earlier or later than expected. So when no events arrive for a long while, it dumbly continues to the end having no evidence that anything is wrong.
What I could do is to record when we are expecting the next event and if it doesn't happen on time to slow down the progress bar more and more.
Does this seem sensible:
When an event is more than 1 second late the progress bar turns to crawl mode where it still progresses but very very slowly (fully paused progress bar is worrying to many). Any time over the expected time plus 1 second the boot task took up is considered dead-time and not relevant to estimating the rest of the boot progress (fsck, network/ypbind timeout, etc.). So once that task finishes the progress assumes a return to the previous boot progress speed.
Sounds reasonable to me.
Pushed into git.
This is built now. (moved to F10Target since the work was already done)
It seems this bug is headed toward closing but if I may suggest, slowing down the progress bar would not really help the ordinary user feel more comfortable after waiting 5, 10 or more minutes for the computer to boot.
Right, for F11 we need to do better fsck integration.
Having this patch for F10 would be an improvement over not having it though (for F10)
yeah, I think if the progress bar had stopped early on, I would have guessed it was fscking. (The machine had just crashed, after all.) It was confusing because the progress bar made it look like it had actually completely finished booting and *then* got stuck.
This bug appears to have been reported against 'rawhide' during the Fedora 10 development cycle.
Changing version to '10'.
More information and reason for this action is here:
This message is a reminder that Fedora 10 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 10. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as WONTFIX if it remains open with a Fedora
'version' of '10'.
Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version prior to Fedora 10's end of life.
Bug Reporter: Thank you for reporting this issue and we are sorry that
we may not be able to fix it before Fedora 10 is end of life. If you
would still like to see this bug fixed and are able to reproduce it
against a later version of Fedora please change the 'version' of this
bug to the applicable version. If you are unable to change the version,
please add a comment here and someone will do it for you.
Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.
The process we are following is described here:
Fedora 10 changed to end-of-life (EOL) status on 2009-12-17. Fedora 10 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.
If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version.
Thank you for reporting this bug and we are sorry it could not be fixed.