Bug 132353 - Error while partitioning
Summary: Error while partitioning
Alias: None
Product: Fedora
Classification: Fedora
Component: anaconda (Show other bugs)
(Show other bugs)
Version: 2
Hardware: i386 Linux
Target Milestone: ---
Assignee: Jeremy Katz
QA Contact: Mike McLean
Depends On:
TreeView+ depends on / blocked
Reported: 2004-09-11 08:15 UTC by Need Real Name
Modified: 2007-11-30 22:10 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2004-10-07 19:05:09 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
the dump file (29.05 KB, text/plain)
2004-09-11 08:17 UTC, Need Real Name
no flags Details

Description Need Real Name 2004-09-11 08:15:10 UTC
From Bugzilla Helper:
User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; 

Description of problem:
Whilethe installer is setting up the partitions a window comes up 
saying something like an unexpected error occurred, this is most 
likely a bug, please save this dumpfile onto a floppy and report it 
to Bugzilla. Then the installer exits. The dump is attached.

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

How reproducible:

Steps to Reproduce:
1. Install fedora core 2 using graphical installer
2. Get to the partitioning section, choosing automatic
3. Change partition setup and then press next
4. The window with the message pops up

Actual Results:  The error described above occurs. This only happens 

Expected Results:  Installer continues with next step.

Additional info:

Comment 1 Need Real Name 2004-09-11 08:17:38 UTC
Created attachment 103721 [details]
the dump file

Comment 2 Jeremy Katz 2004-09-13 15:24:06 UTC
Can you verify your media according to the instructions at

Comment 3 Jeremy Katz 2004-10-07 19:05:09 UTC
Closing due to inactivity.  Please reopen if you have further
information to add to this report.

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