From Bugzilla Helper: User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.5) Gecko/20041111 Firefox/1.0 Description of problem: If kudzu detects new or removed hardware, it prompts you to press a key. If you press a key, but don't answer all its questions within a fairly short period of time, it times out, kudzu disappears. Boot does not continue, but you are stuck on a text screen, with the last message being about enabling swap. Reboot is required at that point. (The timeout is roughly 30 sec. or less, maybe per question.) Version-Release number of selected component (if applicable): kudzu-1.1.95-1 How reproducible: Always Steps to Reproduce: 1. Add or remove hardware that kudzu will notice. 2. Boot/reboot, and press a key when the initial kudzu prompt comes up. 3. When kudzu asks what do do with the hardware, don't do anything. Actual Results: After a short period of time (maybe 30 seconds, give or take), the kudzu screen disappears, replaced by a black and white text screen. The last message on the screen is about enabling swap. Nothing more happens. Boot does not continue, and a reboot is required. Expected Results: The system should wait until all the kudzu questions have been answered. Or, at least, the system should continue to boot after the timeout. Additional info:
Are you using rhgb?
Yes, I'm using rhgb.
Does it recur if you *don't* use rhgb?
This is a rhgb bug; it's randomly switching to tty1. (If you're in this situation, ctrl-alt-f7 or f8 should get you back to rhgb.)
Fedora Core 3 is now maintained by the Fedora Legacy project for security updates only. If this problem is a security issue, please reopen and reassign to the Fedora Legacy product. If it is not a security issue and hasn't been resolved in the current FC5 updates or in the FC6 test release, reopen and change the version to match. Thank you!
The information we've requested above is required in order to review this problem report further and diagnose/fix the issue if it is still present. Since there haven't been any updates to the report in quite a long time now after we've requested additional information, we're assuming the problem is either no longer present in our current OS release, or that there is no longer any interest in tracking the problem. Setting status to CANTFIX, however if you still experience this problem after updating to our latest Fedora Core release and are still interested in Red Hat tracking the issue, and assisting in troubleshooting the problem, please feel free to provide the information requested above, and reopen the report. Thank you in advance. (this message is mass message)