The following was filed automatically by anaconda: anaconda 12.16-1.fc12 exception report Traceback (most recent call first): File "/usr/lib/anaconda/storage/devicetree.py", line 69, in getLUKSPassphrase raise RuntimeError("device is already mapped") File "/usr/lib/anaconda/storage/devicetree.py", line 1350, in handleUdevLUKSFormat self.__passphrase) File "/usr/lib/anaconda/storage/devicetree.py", line 1650, in handleUdevDeviceFormat self.handleUdevLUKSFormat(info, device) File "/usr/lib/anaconda/storage/devicetree.py", line 1254, in addUdevDevice self.handleUdevDeviceFormat(info, device) File "/usr/lib/anaconda/storage/devicetree.py", line 1868, in populate self.addUdevDevice(dev) File "/usr/lib/anaconda/storage/__init__.py", line 293, in reset self.devicetree.populate() File "/usr/lib/anaconda/storage/__init__.py", line 74, in storageInitialize storage.reset() File "/usr/lib/anaconda/dispatch.py", line 204, in moveStep rc = stepFunc(self.anaconda) File "/usr/lib/anaconda/dispatch.py", line 127, in gotoNext self.moveStep() File "/usr/lib/anaconda/gui.py", line 1201, in nextClicked self.anaconda.dispatch.gotoNext() RuntimeError: device is already mapped
Created attachment 358480 [details] Attached traceback automatically from anaconda.
home was pre-setup in /dev/sda3 install was to use free space before home for default partitions. had just inputted to use Irish keyboard, when exception happened.
https://www.redhat.com/archives/fedora-list/2009-August/msg02201.html Portions of this may be relevant? As I also used gparted to setup the free-space. Palimpsest Disk Utility, havng refused to allow permission.
Solved (Hopefully) When booting from the liveMedia. As a reflex, I always entered luks p\w when asked. If this is skipped, just press enter util boot continues. Partitioning (gparted\Palimpsest) and then install work fine. Maybe is may be the case for other similar events?
That's not a solution, merely a workaround. Feel free to use it to avoid this problem, of course, but the underlying cause for the traceback should still be fixed.
*** This bug has been marked as a duplicate of bug 508796 ***