Version-Release number of selected component: system-config-kickstart-2.9.0-1.fc18 Additional info: cmdline: /usr/bin/python2 /usr/bin/system-config-kickstart executable: /usr/bin/system-config-kickstart kernel: 3.8.1-201.fc18.x86_64 uid: 1000 Truncated backtrace: partWindow.py:191:edit_partition:UnboundLocalError: local variable 'fsType' referenced before assignment Traceback (most recent call last): File "/usr/share/system-config-kickstart/partition.py", line 145, in editPartition self.partWindow.edit_partition(iter) File "/usr/share/system-config-kickstart/partWindow.py", line 191, in edit_partition self.fsTypeCombo.entry.set_text(fsType) UnboundLocalError: local variable 'fsType' referenced before assignment Local variables in innermost frame: part_object: <partEntry.partEntry instance at 0x493e3f8> self: <partWindow.partWindow instance at 0x326ef38> type: 'RAID de software' iter: <GtkTreeIter at 0x3030b00>
Created attachment 714485 [details] File: backtrace
Created attachment 714486 [details] File: core_backtrace
Created attachment 714488 [details] File: environ
Created attachment 714489 [details] File: smolt_data
What steps did you take to reach this traceback?
It was the automatic reporting application on the task bar of kde.
No, I mean what did you do with system-config-kickstart?
Created attachment 714701 [details] Kickstart file
I was editing the hand-made kickstart file I have attached.
Ah, I see it now. This is going to be a really lame answer, but system-config-kickstart right now does not support LVM at all. When you go to edit the LVM partition, that's what's causing the crash. I have long term plans for fixing this by creating a new UI, but it's certainly not going to happen any time soon. Sorry.