Bug 495584 - Exception when creating custom layout (after previous failure bz 495582)
Summary: Exception when creating custom layout (after previous failure bz 495582)
Keywords:
Status: CLOSED DUPLICATE of bug 495288
Alias: None
Product: Fedora
Classification: Fedora
Component: anaconda
Version: rawhide
Hardware: x86_64
OS: Linux
low
medium
Target Milestone: ---
Assignee: Anaconda Maintenance Team
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: anaconda_trace_hash:7904e6421e3d5b223...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2009-04-13 20:56 UTC by MartinG
Modified: 2009-04-13 21:00 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2009-04-13 21:00:52 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)
Attached traceback automatically from anaconda. (296.13 KB, text/plain)
2009-04-13 20:56 UTC, MartinG
no flags Details

Description MartinG 2009-04-13 20:56:31 UTC
The following was filed automatically by anaconda:
anaconda None exception report
Traceback (most recent call first):
  File "/usr/lib/anaconda/iw/partition_ui_helpers_gui.py", line 334, in createPreExistFSOptionSection
    if not formatcb.get_active() and not origfs.migrate:
  File "/usr/lib/anaconda/iw/lvm_dialog_gui.py", line 491, in editLogicalVolume
    (row, self.fsoptionsDict) = createPreExistFSOptionSection(reallv, maintable, row, mountCombo, self.storage, ignorefs = ["mdmember", "lvmpv", "vfat"], luksdev=templuks)
  File "/usr/lib/anaconda/iw/lvm_dialog_gui.py", line 716, in editCurrentLogicalVolume
    self.editLogicalVolume(lv)
  File "/usr/lib/anaconda/iw/lvm_dialog_gui.py", line 772, in logvolActivateCb
    self.editCurrentLogicalVolume()
AttributeError: 'NoneType' object has no attribute 'get_active'

Comment 1 MartinG 2009-04-13 20:56:40 UTC
Created attachment 339378 [details]
Attached traceback automatically from anaconda.

Comment 2 Chris Lumens 2009-04-13 21:00:52 UTC

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


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