Bug 76835 - installer hangs after account configuration
Summary: installer hangs after account configuration
Keywords:
Status: CLOSED DUPLICATE of bug 75008
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: anaconda
Version: 7.3
Hardware: i586
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Michael Fulbright
QA Contact: Brock Organ
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2002-10-27 21:08 UTC by Tobias Ambjornsson
Modified: 2007-04-18 16:47 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2002-10-27 21:11:07 UTC
Embargoed:


Attachments (Terms of Use)
anacanda dump (43.18 KB, text/plain)
2002-10-27 21:11 UTC, Tobias Ambjornsson
no flags Details

Description Tobias Ambjornsson 2002-10-27 21:08:13 UTC
From Bugzilla Helper:
User-Agent: Mozilla/4.7 [en] (Win98; I)

Description of problem:
When pressing the 'next' button after having done the account configuration during the linux installation process I got the message "an unhandled 
exception has occured". I was adviced to do a crashdump (see attachment) which I also did.

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


How reproducible:
Always

Steps to Reproduce:
1.use fips to create a 2.8 Mb partition.
2.When going through installation procedure (booting from a diskette) I use Disk Druid, which works OK.
3.When pressing the 'next' button after the account configuration I get the error message "an unhandled exception has occured".
	

Actual Results:   I got the error message "an unhandled exception has occured" and the system went into a text mode and after a while it said 
(roughly) " you may reboot the system".

Expected Results:  Should have proceeded to the next step in the installation procedure.

Additional info:

Comment 1 Tobias Ambjornsson 2002-10-27 21:11:01 UTC
Created attachment 82304 [details]
anacanda dump

Comment 2 Michael Fulbright 2002-10-30 22:30:30 UTC

*** This bug has been marked as a duplicate of 75008 ***


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