Bug 145086 - Installer crashed when I choose automalically partition
Summary: Installer crashed when I choose automalically partition
Keywords:
Status: CLOSED DUPLICATE of bug 138419
Alias: None
Product: Fedora
Classification: Fedora
Component: anaconda
Version: 2
Hardware: i386
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Anaconda Maintenance Team
QA Contact: Mike McLean
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2005-01-14 09:06 UTC by pedram motlagh
Modified: 2007-11-30 22:10 UTC (History)
0 users

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2006-02-21 19:07:55 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
Installer crashed when I choose automalically partition (34.00 KB, text/plain)
2005-01-14 09:10 UTC, pedram motlagh
no flags Details

Description pedram motlagh 2005-01-14 09:06:16 UTC
From Bugzilla Helper:
User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1)

Description of problem:
When i choose kyboard this massage is shown:
unable to align partition property . This probably means that another 
partitioning tool generated an incorrect partition table , because it 
didn't have the correct Bios geometry.
It is fafe ti ignore , but ignoring may cause (fixable)problems with 
some boot loader .

when I choose Ignore and autonatically partition and remove all Linux 
partition this massage is shown :
Exceptio occurred
an unhandled exception has occurred . this is most likly bug . please 
copythe ful text ......



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


How reproducible:
Always

Steps to Reproduce:

    

Additional info:

Comment 1 pedram motlagh 2005-01-14 09:10:17 UTC
Created attachment 109771 [details]
Installer crashed when I choose automalically partition

when I choose autonatically partition and remove all Linux partition this
massage is shown :

Comment 2 Jeremy Katz 2005-01-14 14:31:39 UTC

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

Comment 3 Red Hat Bugzilla 2006-02-21 19:07:55 UTC
Changed to 'CLOSED' state since 'RESOLVED' has been deprecated.


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