Bug 157408 - Post-install configuration takes too long, no mouse movement
Post-install configuration takes too long, no mouse movement
Product: Fedora
Classification: Fedora
Component: anaconda (Show other bugs)
i386 Linux
medium Severity medium
: ---
: ---
Assigned To: Anaconda Maintenance Team
Mike McLean
Depends On:
  Show dependency treegraph
Reported: 2005-05-11 09:22 EDT by Jon Davidson
Modified: 2007-11-30 17:11 EST (History)
0 users

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2005-09-21 17:06:42 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 Jon Davidson 2005-05-11 09:22:40 EDT
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.2; en-US; rv:1.7.7) Gecko/20050414 Firefox/1.0.3

Description of problem:
The post-install configuration screen is up way too long. During this time, the mouse also goes dead.  If i wait long enough, it comes back.

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

How reproducible:
Didn't try

Steps to Reproduce:
1.  install fedora core 4 test 3

Actual Results:  post-install configuration took too long and prevented user interaction.

Expected Results:  should have taken less time and let the mouse move so i didn't think it died.

Additional info:
Comment 1 Raghu 2005-05-11 12:55:40 EDT
How long did you wait.. I waited for half an hour to one hour before giving up.
Comment 2 Jeremy Katz 2005-05-18 21:29:10 EDT
Can you switch ttys?  If so, what processes are running from tty2?
Comment 3 Jeremy Katz 2005-09-21 17:06:42 EDT
Since there are insufficient details provided in this report for us to
investigate the issue further, and we have not received the feedback we
requested, we will assume the problem was not reproduceable or has been fixed in
a later update for this product.  If you have further details, feel free to
reopen the report with the additional details attached.

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