Description of problem: This is still happening for me on a squeaky-clean install of Fedora 23 Version-Release number of selected component: livecd-tools-23.3-1.fc23 Additional info: reporter: libreport-2.6.4 backtrace_rating: 4 cmdline: /usr/bin/python -tt /usr/bin/livecd-creator --cache=cache --config=ks.cfg -v --releasever=23 crash_function: __env_alloc executable: /usr/bin/python2.7 global_pid: 13252 kernel: 4.2.3-300.fc23.x86_64 runlevel: N 3 type: CCpp uid: 0 Truncated backtrace: Thread no. 1 (10 frames) #0 __env_alloc at ../../src/env/env_alloc.c:358 #1 __memp_alloc at ../../src/mp/mp_alloc.c:93 #2 __memp_fget at ../../src/mp/mp_fget.c:646 #3 __bam_read_root at ../../src/btree/bt_open.c:326 #4 __bam_open at ../../src/btree/bt_open.c:103 #5 __db_open at ../../src/db/db_open.c:239 #6 __db_open_pp at ../../src/db/db_iface.c:1193 #7 db3_dbiOpen at backend/db3.c:860 #8 indexOpen at rpmdb.c:197 #9 indexIterInit at rpmdb.c:1800
Created attachment 1160743 [details] File: backtrace
Created attachment 1160744 [details] File: cgroup
Created attachment 1160745 [details] File: core_backtrace
Created attachment 1160746 [details] File: dso_list
Created attachment 1160747 [details] File: environ
Created attachment 1160748 [details] File: exploitable
Created attachment 1160749 [details] File: limits
Created attachment 1160750 [details] File: maps
Created attachment 1160751 [details] File: mountinfo
Created attachment 1160752 [details] File: namespaces
Created attachment 1160753 [details] File: open_fds
Created attachment 1160754 [details] File: proc_pid_status
Created attachment 1160755 [details] File: var_log_messages
This appears to be a duplicate of #1179043 from F21
An update: After some messing around I identified the offending line in my kickstart file as: > part / --asprimary --fstype="ext4" --grow --size=1 (this file was generated by system-config-kickstart, which I'm not sure is capable of producing kickstart files that will build correctly with livecd-tools or not, but the current behaviour is certainly quite strange). Changing the size to "2" instead of "1" causes this error to vanish.
Weird, that still shouldn't cause python to crash though. Also, with --grow the --size should really be set to something reasonable instead of tiny, this helps blivet do a better job deciding how to partition the disks.
Agreed on both counts. I normally set this to "1024" as a nominally tiny amount, but I suppose as it's the minimum, it is probably worth setting it to a useful amount. Perhaps system-config-kickstart should choose a different value when one selects "Fill all unused space on disk"?
This message is a reminder that Fedora 23 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 23. It is Fedora's policy to close all bug reports from releases that are no longer maintained. At that time this bug will be closed as EOL if it remains open with a Fedora 'version' of '23'. Package Maintainer: If you wish for this bug to remain open because you plan to fix it in a currently maintained version, simply change the 'version' to a later Fedora version. Thank you for reporting this issue and we are sorry that we were not able to fix it before Fedora 23 is end of life. If you would still like to see this bug fixed and are able to reproduce it against a later version of Fedora, you are encouraged change the 'version' to a later Fedora version prior this bug is closed as described in the policy above. Although we aim to fix as many bugs as possible during every release's lifetime, sometimes those efforts are overtaken by events. Often a more recent Fedora release includes newer upstream software that fixes bugs or makes them obsolete.
Fedora 23 changed to end-of-life (EOL) status on 2016-12-20. Fedora 23 is no longer maintained, which means that it will not receive any further security or bug fix updates. As a result we are closing this bug. If you can reproduce this bug against a currently maintained version of Fedora please feel free to reopen this bug against that version. If you are unable to reopen this bug, please file a new report against the current release. If you experience problems, please add a comment to this bug. Thank you for reporting this bug and we are sorry it could not be fixed.