Description of problem: I booted off a usb thumb drive for installing Fedora. I hit OK on the initial screen. I plugged in an ethernet cable, then clicked on partitioning, then clicked Done to use the default partitioning. It was when I clicked Done that I hit this error. Version-Release number of selected component: anaconda-23.19.10-1 The following was filed automatically by anaconda: anaconda 23.19.10-1 exception report Traceback (most recent call first): File "/usr/lib64/python3.4/site-packages/pyanaconda/packaging/dnfpayload.py", line 550, in spaceRequired for (key, val) in self.storage.mountpoints.items(): File "/usr/lib64/python3.4/site-packages/pyanaconda/ui/gui/spokes/storage.py", line 817, in _check_space_and_get_dialog required_space = self.payload.spaceRequired File "/usr/lib64/python3.4/site-packages/pyanaconda/ui/gui/spokes/storage.py", line 964, in on_back_clicked dialog = self._check_space_and_get_dialog(disks) AttributeError: 'NoneType' object has no attribute 'mountpoints' Additional info: addons: com_redhat_kdump cmdline: /usr/bin/python3 /sbin/anaconda cmdline_file: BOOT_IMAGE=vmlinuz initrd=initrd.img inst.stage2=hd:LABEL=Fedora-WS-23-x86_64 quiet executable: /sbin/anaconda hashmarkername: anaconda kernel: 4.2.3-300.fc23.x86_64 product: Fedora release: Cannot get release name. type: anaconda version: 23
Created attachment 1120877 [details] File: anaconda-tb
Created attachment 1120878 [details] File: anaconda.log
Created attachment 1120879 [details] File: dnf.log
Created attachment 1120880 [details] File: dnf.rpm.log
Created attachment 1120881 [details] File: environ
Created attachment 1120882 [details] File: lsblk_output
Created attachment 1120883 [details] File: nmcli_dev_list
Created attachment 1120884 [details] File: os_info
Created attachment 1120885 [details] File: program.log
Created attachment 1120886 [details] File: storage.log
Created attachment 1120887 [details] File: syslog
Created attachment 1120888 [details] File: ifcfg.log
Created attachment 1120889 [details] File: packaging.log
*** This bug has been marked as a duplicate of bug 1271657 ***
*** Bug 1339701 has been marked as a duplicate of this bug. ***