abrt version: 2.0.5
reason: FormatSetupError: invalid device specification
time: Wed Sep 7 15:53:39 2011
:The following was filed automatically by anaconda:
:anaconda 16.14.6 exception report
:Traceback (most recent call first):
: File "/usr/lib64/python2.7/site-packages/pyanaconda/storage/formats/__init__.py", line 334, in setup
: raise FormatSetupError("invalid device specification")
: File "/usr/lib64/python2.7/site-packages/pyanaconda/storage/formats/swap.py", line 132, in setup
: DeviceFormat.setup(self, *args, **kwargs)
: File "/usr/lib64/python2.7/site-packages/pyanaconda/storage/__init__.py", line 2043, in turnOnSwap
: File "/usr/lib64/python2.7/site-packages/pyanaconda/storage/__init__.py", line 1305, in turnOnSwap
: File "/usr/lib64/python2.7/site-packages/pyanaconda/packages.py", line 151, in turnOnFilesystems
: File "/usr/lib64/python2.7/site-packages/pyanaconda/dispatch.py", line 348, in dispatch
: self.dir = self.steps[self.step].target(self.anaconda)
: File "/usr/lib64/python2.7/site-packages/pyanaconda/dispatch.py", line 235, in go_forward
: File "/usr/lib64/python2.7/site-packages/pyanaconda/gui.py", line 1198, in nextClicked
:FormatSetupError: invalid device specification
There is a file that matches /tmp/anaconda-tb-* which you can get to by switching to tty2 (ctl+alt+f2). Please transfer it out using scp or other means and attach it to this bug as an attachment of type text/plain. Thank you.
Created attachment 522618 [details]
What steps did you take that resulted in this problem? Is it at all reproducible?
for me it is reproducible.
I'm working with LVM and the SWAP partition is also on an LVM volume.
The problem occurs when there is already a SWAP partition on LVM and I select this and go to "Edit" and close the dialog without doing any changes.
When I then go to "Next" the bug occur.
But when I go to "Edit" and say format, it's working.
I hope this helps.
This appears to be a duplicate of bug 723303. The difference is that in this case the device is formatted as swap space while the other was a filesystem. This should be resolved in the F16 beta.
*** This bug has been marked as a duplicate of bug 723303 ***