Bug 205198 - Anaconda crashes with exception when "back" is clicked at last stage of upgrade
Summary: Anaconda crashes with exception when "back" is clicked at last stage of upgrade
Keywords:
Status: CLOSED RAWHIDE
Alias: None
Product: Fedora
Classification: Fedora
Component: anaconda
Version: rawhide
Hardware: All
OS: Linux
medium
medium
Target Milestone: ---
Assignee: Anaconda Maintenance Team
QA Contact: Mike McLean
URL:
Whiteboard:
Depends On:
Blocks: FC6Blocker
TreeView+ depends on / blocked
 
Reported: 2006-09-05 13:32 UTC by Mayank Jain
Modified: 2007-11-30 22:11 UTC (History)
1 user (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2006-10-04 20:47:09 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
Exception file as saved after crash. (121.61 KB, text/plain)
2006-09-05 13:32 UTC, Mayank Jain
no flags Details

Description Mayank Jain 2006-09-05 13:32:09 UTC
Description of problem:
Anaconda will crash with an exception (see attached file) when "back" is 
clicked during the last stage of upgrade process... ie, the screen with "Click 
next to begin upgrade of fedora core"

Version-Release number of selected component (if applicable):
anaconda-11.1.0.89-1.x86_64.rpm      

How reproducible:
Everytime

Steps to Reproduce:
1. Install FC
2. Again begin the installation process, choose upgrade path, keep boot 
configuration as what was previous, keep on clicking next till you reach final 
screen saying "Click next to begin upgrade of fedora core"
3. Click back button.
  
Actual results:
Anaconda crashes with dump

Expected results:
Previous screen should be displayed.

Additional info:
This *might* be the anaconda version that goes into FC6T3. I was using an NFS 
install.

Comment 1 Mayank Jain 2006-09-05 13:32:13 UTC
Created attachment 135557 [details]
Exception file as saved after crash.

Comment 2 Mayank Jain 2006-09-05 13:39:25 UTC
Let me know if any more information is required.

Comment 3 Jeremy Katz 2006-10-04 20:47:09 UTC
Fixed

Comment 4 Mayank Jain 2006-10-05 06:48:42 UTC
Thanks :)


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