Bug 683982 - Anaconda crashes when going back to the initial storage device exploration
Summary: Anaconda crashes when going back to the initial storage device exploration
Keywords:
Status: CLOSED DUPLICATE of bug 681267
Alias: None
Product: Fedora
Classification: Fedora
Component: anaconda
Version: 15
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Anaconda Maintenance Team
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-03-10 20:41 UTC by Hedayat Vatankhah
Modified: 2011-03-10 20:47 UTC (History)
3 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2011-03-10 20:47:55 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
Anaconda Backtrace (75.65 KB, application/x-bzip2)
2011-03-10 20:41 UTC, Hedayat Vatankhah
no flags Details

Description Hedayat Vatankhah 2011-03-10 20:41:00 UTC
Created attachment 483560 [details]
Anaconda Backtrace

Description of problem:
When installing Fedora 15 Alpha if I go a few screens forward and then go backwards until reaching where the installer tries to detect storage devices (in the initial steps), anaconda crashes with the attached output.

Comment 1 Chris Lumens 2011-03-10 20:47:02 UTC
Please attach tracebacks as plain text so we can search them in the future.

anaconda 15.20.1 exception report
Traceback (most recent call first):
  File "/usr/lib64/python2.7/site-packages/pyanaconda/iw/examine_gui.py", line 101, in getScreen
    (self.anaconda.rootParts, notUpgradable) = upgrade.findExistingRoots(self.anaconda,
  File "/usr/lib64/python2.7/site-packages/pyanaconda/gui.py", line 1338, in setScreen
    new_screen = self.currentWindow.getScreen(anaconda)
  File "/usr/lib64/python2.7/site-packages/pyanaconda/gui.py", line 1249, in prevClicked
    self.setScreen ()
AttributeError: 'module' object has no attribute 'findExistingRoots'

Comment 2 Chris Lumens 2011-03-10 20:47:55 UTC

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


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