The following was filed automatically by anaconda: anaconda 11.5.0.37 exception report Traceback (most recent call first): File "/usr/lib/anaconda/storage/formats/fs.py", line 1015, in _deviceCheck if not ":" in devspec: File "/usr/lib/anaconda/storage/formats/fs.py", line 1023, in _setDevice self._deviceCheck(devspec) File "/usr/lib/anaconda/storage/formats/fs.py", line 1030, in <lambda> lambda f,d: f._setDevice(d), File "/usr/lib/anaconda/storage/formats/__init__.py", line 163, in __init__ self.device = kwargs.get("device") File "/usr/lib/anaconda/storage/formats/fs.py", line 150, in __init__ DeviceFormat.__init__(self, *args, **kwargs) File "/usr/lib/anaconda/iw/partition_ui_helpers_gui.py", line 199, in createFSTypeMenu format = device_formats[name]() File "/usr/lib/anaconda/iw/partition_dialog_gui.py", line 321, in __init__ availablefstypes = restrictfs) File "/usr/lib/anaconda/iw/partition_gui.py", line 1118, in editPartition restrictfs = restrictfs) File "/usr/lib/anaconda/iw/partition_gui.py", line 976, in newCB self.editPartition(device, isNew=1) TypeError: argument of type 'NoneType' is not iterable
Created attachment 336615 [details] Attached traceback automatically from anaconda.
... quark collision (**kwargs) with an Solaris partition ... lambda,quarks, ..., quantum physics ? seriously: it was a native (non VM) install via boot.iso. chosen was a manual partitioning on free space on sdaN with N > 3 Disk /dev/sda: 200.0 GB, 200049647616 bytes Device Boot Start End Blocks Id System /dev/sda1 * 1 1044 8385898+ 83 Linux /dev/sda2 1045 3477 19543072+ bf Solaris /dev/sda3 3478 10773 58605120 8e Linux LVM Disk /dev/sdb: 40.0 GB, 40060403712 bytes Device Boot Start End Blocks Id System /dev/sdb1 * 1 765 6144831 7 HPFS/NTFS /dev/sdb2 766 3377 20980890 7 HPFS/NTFS /dev/sdb3 3378 3403 204800 7 HPFS/NTFS /dev/sdb4 3403 4871 11788288 7 HPFS/NTFS
Created attachment 336622 [details] Attached traceback automatically from anaconda.
Created attachment 336625 [details] Attached traceback automatically from anaconda.
This should be fixed in the next build of anaconda. Thanks for the report.
*** Bug 492044 has been marked as a duplicate of this bug. ***
*** Bug 492141 has been marked as a duplicate of this bug. ***
Created attachment 336780 [details] Attached traceback automatically from anaconda.
*** Bug 492512 has been marked as a duplicate of this bug. ***
This is fixed in anaconda 11.5.0.38 and over
when does "over" hit the mirror's ?
@ Ronald Warsow This was fixed in 11.5.0.38 you don't need the next release. I test it using the net install iso image: http://download.fedora.redhat.com/pub/fedora/linux/development/$basearch/os/images/boot.iso replace $basearch with x86_64 or i386 according to your system.
@Vinagre Thanks for the hint. Each morning I look at this link since ~10 days..., and koji (anaconda), and in the directory "Packages". Frustrating ! But you are right I'm in the wrong anaconda bug - one of my ~5 -. the remaining/todays bug/trace is called "Unable to satisfy all constraints ..." So it looks like I need anaconda version "over"
to be closed !