Bug 136106
Summary: | In case of unclean shutdown, during fsck during bootup, progress bar is not shown | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Uttiya Chowdhury <chowdhury_uttiya> |
Component: | rhgb | Assignee: | Ray Strode [halfline] <rstrode> |
Status: | CLOSED CANTFIX | QA Contact: | |
Severity: | low | Docs Contact: | |
Priority: | medium | ||
Version: | 3 | ||
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | x86_64 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2006-10-30 15:55:31 UTC | Type: | --- |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Uttiya Chowdhury
2004-10-17 22:26:34 UTC
Are you using rhgb? I have the same problem. I am using rhgb, and when it gets to the point where it recognizes that the machine was shutdown improperly, it switches to text mode and asks whether to do a fsck. When you answer yes, it just sits there -- no output is produced (note, you are still in text mode). Eventually it finishes and goes along with the rest of the boot, switching to graphical mode. Some status is really needed here, otherwise, you think that the machine is hung. An fsck can take quite a while. Seems to be a problem with rhgb. Assigning to rhgb. Closing per lack of response to previous request for information. This bug was originally filed against a much earlier version of Fedora Core, and significant changes have taken place since the last version for which this bug is confirmed. Note that FC3 and FC4 are supported by Fedora Legacy for security fixes only. Please install a still supported version and retest. If it still occurs on FC5 or FC6, please reopen and assign to the correct version. Otherwise, if this a security issue, please change the product to Fedora Legacy. Thanks, and we are sorry that we did not get to this bug earlier. |