Bug 125860 - Anaconda / disk druid crashed when creating a partiton
Summary: Anaconda / disk druid crashed when creating a partiton
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Red Hat Enterprise Linux 3
Classification: Red Hat
Component: anaconda
Version: 3.0
Hardware: x86_64
OS: Linux
medium
high
Target Milestone: ---
Assignee: Jeremy Katz
QA Contact: Mike McLean
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2004-06-12 17:26 UTC by reubendb
Modified: 2007-11-30 22:07 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2005-02-01 23:33:47 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)
anaconda crash dump (47.83 KB, text/plain)
2004-06-12 17:28 UTC, reubendb
no flags Details
syslog (9.04 KB, text/plain)
2004-06-12 17:28 UTC, reubendb
no flags Details

Description reubendb 2004-06-12 17:26:41 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.6)
Gecko/20040207 Firefox/0.8

Description of problem:
When trying to create a new partition in disk druid, Anaconda suddenly
crashed with unhandled exceptions, and give me a crash dump which I
could save in floppy (which is good). The crash dump file is attached.

I think I may have unintentionally tryed to create a new partition in
a disk that has no free space, which may caused the crash, but I don't
quite remember. Rebooting the system and tried the install again
worked fine. 

In anycase, user's ignorance or incompetency should not crash the
system :).



Version-Release number of selected component (if applicable):
RHEL 3 WS Update 2

How reproducible:
Didn't try

Steps to Reproduce:
1.
2.
3.
    
I did not try to reproduce the crash, as the next try of the install
worked fine. 

Additional info:

Comment 1 reubendb 2004-06-12 17:28:08 UTC
Created attachment 101084 [details]
anaconda crash dump

Comment 2 reubendb 2004-06-12 17:28:34 UTC
Created attachment 101085 [details]
syslog

Comment 3 Jeremy Katz 2005-02-01 23:33:47 UTC
This is fixed in CVS now


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