Bug 507078 - Anaconda crashes during grub config after changing Other OS to Vista and trying to default back to Fedora
Summary: Anaconda crashes during grub config after changing Other OS to Vista and tryi...
Keywords:
Status: CLOSED DUPLICATE of bug 504969
Alias: None
Product: Fedora
Classification: Fedora
Component: anaconda
Version: 11
Hardware: x86_64
OS: Linux
low
high
Target Milestone: ---
Assignee: Anaconda Maintenance Team
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2009-06-20 16:19 UTC by Davide Rossetti
Modified: 2009-06-22 14:37 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2009-06-22 14:37:19 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)
anaconda crash dump (198.42 KB, text/plain)
2009-06-20 16:19 UTC, Davide Rossetti 		no flags Details
View All

Description Davide Rossetti 2009-06-20 16:19:13 UTC 
Created attachment 348748 [details]
anaconda crash dump

Description of problem:
while installing F11, after disk partitioning and during grub configuration, tried to rename 'other' OS to Vista. it removed the 'default' check box from fedora. trying to re-default fedora clicking on the 'fedora' check box, I got the crash.

Version-Release number of selected component (if applicable):
Fedora 11 installer from X86_64 Gnome DVD

How reproducible:
got it just once. following time, I avoided to touch the grub config and the installation went on.

Steps to Reproduce:
1. buy a HDX16, shrink the C: partition to leave space for Fedora
2. install fedora on it, choosing 'install on free space'
3. try to change the name of 'Other' OS to 'Vista', you loose the default boot check mark on 'Fedora', so try setting it back and you get the crash
  
Actual results:
anaconda crash

Expected results:


Additional info:
attaching the anaconda dump
Comment 1 Andy Lindeberg 2009-06-22 14:37:19 UTC 

*** This bug has been marked as a duplicate of bug 504969 ***
Note You need to log in before you can comment on or make changes to this bug.