Bug 520601 - Changing default in boot loader operating list twice causes anaconda crash
Summary: Changing default in boot loader operating list twice causes anaconda crash
Alias: None
Product: Fedora
Classification: Fedora
Component: anaconda
Version: 11
Hardware: All
OS: Linux
Target Milestone: ---
Assignee: Anaconda Maintenance Team
QA Contact: Fedora Extras Quality Assurance
Depends On:
Blocks: F12Target
TreeView+ depends on / blocked
Reported: 2009-09-01 12:23 UTC by Robert Scheck
Modified: 2010-01-20 18:50 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Last Closed: 2010-01-20 18:50:26 UTC
Type: ---

Attachments (Terms of Use)

Description Robert Scheck 2009-09-01 12:23:42 UTC
Description of problem:
Assume the screenshot from http://docs.fedoraproject.org/install-guide/f11/
en-US/html/images/x86-bootloader/x86-bootloader.png with the difference, that 
there are simply two entries in the list, Fedora and Windows. If you change
the default (Fedora) to the "Other" (Windows) and then back, this won't work.
If you click to the "Edit" button behind "Fedora" and set there the tick for
default boot target and "OK", Anaconda simply crashes. Note that no LVM setup
was in use, just plain partitioning with crypto partitions and /boot.

Version-Release number of selected component (if applicable):
Anaconda of Fedora 11 (i386) final via Netinstall.

How reproducible:
Everytime, see above.

Actual results:
Changing default in boot loader operating list twice causes anaconda crash

Expected results:
No crash, everything working, switching default operating system how often I
ever want and via both ways (list and edit button).

Comment 1 Joel Andres Granados 2009-09-02 12:40:04 UTC
I recently tested this functionality with anaconda rawhide and it worked for me.  Can you pls test with the latest anaconda (12-18 or greater) and confirm this behavior?

Comment 2 Robert Scheck 2009-09-02 12:45:11 UTC
If you could try to reproduce it with Fedora 11 as released, you will see
very fast whether it's fixed in Rawhide or not...

Comment 3 Chris Lumens 2009-09-02 14:14:18 UTC
Not really, no.  We've got a related bug about a crash on the bootloader screen that we've never been able to reproduce on F11 or any rawhide, so it's worth you also testing it out and seeing what the status is.

Comment 4 Joel Andres Granados 2009-09-03 08:37:35 UTC
To add to comment #3.  Some bugs are really hard to reproduce because they are related to very specific Hardware configurations or very specific states.  Since we don't have your exact hardware nor your configuration, we might not see what you see.  This is also the reason your feedback is so important to actually get this solved.

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