Bug 107121 - rhgb doesn't display fsck output
Summary: rhgb doesn't display fsck output
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Fedora
Classification: Fedora
Component: rhgb
Version: rawhide
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Daniel Veillard
QA Contact:
URL:
Whiteboard:
: 129881 (view as bug list)
Depends On: 132665
Blocks:
TreeView+ depends on / blocked
 
Reported: 2003-10-15 07:47 UTC by Jens Petersen
Modified: 2007-11-30 22:10 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2004-09-15 17:41:04 UTC


Attachments (Terms of Use)

Description Jens Petersen 2003-10-15 07:47:52 UTC
Description of problem:
After every N boots, fsck.ext3 gets run at startup.  In this case rhgb doesn't
give any indication of what is going on on either the undetailed or detailed
screens.  Since running fsck is rather time-consuming these days, some kind
of visual feedback for this would be very nice to have.

Version-Release number of selected component (if applicable):
rhgb-0.10.2-1

Comment 1 Nils O. Selåsdal 2004-05-03 11:28:52 UTC
I was just about to report this as well.
It's rather nasty cause the machine appears hung, no feed back
on anything(except HD flashlight is on). rhgb just shows nothing,
and after a couple of reboots I realized switching (ctrl+alt+f1) might
help, and there it was, doing a fsck..

Comment 2 Alexandre Oliva 2004-09-06 14:59:35 UTC
Unfortunately (bug 131899) Ctrl-Alt-F1 doesn't work any more.

Comment 3 Daniel Veillard 2004-09-15 17:41:04 UTC
Ctrl-Alt-F1 should be fixed on rhgb-0.13.1-1
it also should fix this issue assuming the patch from #132665
is also applied. In which case the fsck progresses and results
are shown in the rhgb detailed view.
Anyway rhgb-0.13.1-1 is being pushed to rawhide and should fix this
issue.

Daniel

Comment 4 Daniel Veillard 2004-09-15 17:47:40 UTC
*** Bug 129881 has been marked as a duplicate of this bug. ***


Note You need to log in before you can comment on or make changes to this bug.