Bug 134449 - /.autofsck causes switch to vt1 without ever switching back
Summary: /.autofsck causes switch to vt1 without ever switching back
Status: CLOSED RAWHIDE
Alias: None
Product: Fedora
Classification: Fedora
Component: initscripts   
(Show other bugs)
Version: rawhide
Hardware: i386
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Bill Nottingham
QA Contact: Brock Organ
URL:
Whiteboard:
Keywords:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2004-10-02 21:02 UTC by Alexandre Oliva
Modified: 2014-03-17 02:48 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2004-10-17 04:52:18 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

Description Alexandre Oliva 2004-10-02 21:02:16 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.3)
Gecko/20040929

Description of problem:
Since current rhgb displays fsck progress in the rhgb window, it is
now safe to switch back to rhgb after the prompt is answered or times
out.  Ideally, the prompt should be displayed in rhgb itself.

Version-Release number of selected component (if applicable):
rhgb-0.13.5-1
initscripts-7.85-1

How reproducible:
Always

Steps to Reproduce:
1.Reboot uncleanly


Actual Results:  rhgb go away for the `force file system check' prompt
and never come back

Expected Results:  rc.sysinit should switch back to vt8 before
starting the actual fsck, or not switch to vt1 if we could prompt
through rhgb

Additional info:

Comment 1 Alexandre Oliva 2004-10-02 21:04:53 UTC
DV says we probably can't feed initscripts any input, so it's tricky
to move the prompt into rhgb.  My suggestion is to intercept the
prompt, open a dialogue in rhgb, and store the result in a file in
/etc/rhgb that rc.sysinit would look for.

Comment 2 Bill Nottingham 2004-10-17 04:52:18 UTC
Fixed in 7.91-1, in that it switches back to rhgb after the fsck
finishes. More complicated fixes later. :)


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