Red Hat Bugzilla – Bug 492158
Traceback from EFI partitioning
Last modified: 2013-01-09 22:28:49 EST
The following was filed automatically by anaconda:
anaconda 126.96.36.199 exception report
Traceback (most recent call first):
File "/usr/lib/anaconda/storage/partitioning.py", line 870, in growPartitions
if not limited[part.name]:
File "/usr/lib/anaconda/storage/partitioning.py", line 554, in doPartitioning
File "/usr/lib/anaconda/storage/partitioning.py", line 191, in doAutoPartition
File "/usr/lib/anaconda/dispatch.py", line 205, in moveStep
rc = stepFunc(self.anaconda)
File "/usr/lib/anaconda/dispatch.py", line 128, in gotoNext
File "/usr/lib/anaconda/gui.py", line 1317, in nextClicked
Created attachment 336672 [details]
Attached traceback automatically from anaconda.
Created attachment 336674 [details]
This should be fixed with the next build of anaconda.
Ran into the same problem on an IBM HS22 blade and and IBM x3650 M2.
This bug appears to pertain to an important F11 feature, EFI, which the Fedora Community will be testing in an upcoming Fedora Test Day. Your participation in the action would be greatly appreciated!
I can't trigger this on my EFI system. Jesse, is there a specific method to triggering this bug, or can it be closed?
No more tracebacks for me.