Bug 100894 - confirm and graphical boot together cause problems
confirm and graphical boot together cause problems
Product: Red Hat Linux Beta
Classification: Retired
Component: initscripts (Show other bugs)
i386 Linux
medium Severity high
: ---
: ---
Assigned To: Bill Nottingham
Brock Organ
Depends On:
Blocks: CambridgeBlocker
  Show dependency treegraph
Reported: 2003-07-26 17:32 EDT by Jay Berkenbilt
Modified: 2014-03-16 22:37 EDT (History)
4 users (show)

See Also:
Fixed In Version: 7.41-1
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2003-10-22 15:59:22 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

  None (edit)
Description Jay Berkenbilt 2003-07-26 17:32:17 EDT
Description of problem:

If you have GRAHPICAL boot enabled and boot into runlevel 5 with "confirm" on
the commandline, the boot hangs once the graphical boot starts.

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

9.0.93, initscripts 7.28-1

How reproducible:

always, I assume...

Steps to Reproduce:
1. with GRAHPICAL=yes in /etc/sysconfig/init, boot into runlevel 5 appending
"confirm" to kernel comandline

Actual results:

Graphical boot starts and then fails to make progress.

Expected results:

I would expect "confirm" to automatically apply "nogui".  It seems to me that
this would be an easy fix.  I think this is better than disregarding confirm
since a commandline argument should always take precedence over a configuration
file, and I think it's silly to have to type both confirm and nogui.

Additional info:

I had already added DontZap to my XF86Config file, so I don't know whether
CTRL-ALT-Backspace would have shut down the X server that was showing the
graphical bootup status since I know it wouldn't work for my configuration.
Comment 1 Bill Nottingham 2003-10-22 15:59:22 EDT
Will be fixed in initscripts-7.41-1, in combination with rhgb-0.11 or later.

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