Description of problem: Selected "Bios Parition" accidentally when making a patition under a LVM volume group in blivet Version-Release number of selected component: anaconda-core-28.22.10-1.fc28.x86_64 The following was filed automatically by anaconda: anaconda 28.22.10 exception report Traceback (most recent call first): File "/usr/lib/python3.6/site-packages/blivetgui/dialogs/size_chooser.py", line 188, in max_size_limit raise ValueError("Size limit for maximum size cannot be smaller than current minimum size.") File "/usr/lib/python3.6/site-packages/blivetgui/dialogs/add_dialog.py", line 790, in on_filesystems_combo_changed self.size_area.max_size_limit = self._get_max_size_limit() ValueError: Size limit for maximum size cannot be smaller than current minimum size. Additional info: addons: com_redhat_kdump cmdline: /usr/bin/python3 /sbin/anaconda --liveinst --method=livecd:///dev/mapper/live-base cmdline_file: BOOT_IMAGE=vmlinuz initrd=initrd.img root=live:CDLABEL=Fedora-MATE-Live-28-1-1 rd.live.image quiet executable: /sbin/anaconda hashmarkername: anaconda kernel: 4.16.3-301.fc28.x86_64 other involved packages: blivet-gui-runtime-2.1.8-4.fc28.noarch product: Fedora release: Fedora release 28 (Twenty Eight) type: anaconda version: 28
Created attachment 1471101 [details] File: anaconda-tb
Created attachment 1471102 [details] File: anaconda.log
Created attachment 1471103 [details] File: blivet-gui-utils.log
Created attachment 1471104 [details] File: dbus.log
Created attachment 1471105 [details] File: environ
Created attachment 1471106 [details] File: journalctl
Created attachment 1471107 [details] File: lsblk_output
Created attachment 1471108 [details] File: lvm.log
Created attachment 1471109 [details] File: nmcli_dev_list
Created attachment 1471110 [details] File: os_info
Created attachment 1471111 [details] File: program.log
Created attachment 1471112 [details] File: storage.log
Created attachment 1471113 [details] File: ifcfg.log
Looks like an issue in blivet-gui. Reassigning.
This message is a reminder that Fedora 28 is nearing its end of life. On 2019-May-28 Fedora will stop maintaining and issuing updates for Fedora 28. 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 '28'. 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 28 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 28 changed to end-of-life (EOL) status on 2019-05-28. Fedora 28 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.