Description of problem: I allready wrote about this bug and send a report without pass and acc (just to data server). About crush of live cd install process when I created mount points. Version-Release number of selected component: anaconda-20.25.15-1.fc20.x86_64 The following was filed automatically by anaconda: anaconda 20.25.15-1 exception report Traceback (most recent call first): File "/usr/lib64/python2.7/site-packages/pyanaconda/ui/gui/spokes/custom.py", line 1686, in _populate_right_side log.debug("updated device_disks to %s", [d.name for d in self._device_disks]) File "/usr/lib64/python2.7/site-packages/pyanaconda/ui/gui/spokes/custom.py", line 2513, in on_selector_clicked self._populate_right_side(selector) File "/usr/lib64/python2.7/site-packages/pyanaconda/ui/gui/spokes/custom.py", line 2186, in _show_mountpoint self.on_selector_clicked(page.members[0]) File "/usr/lib64/python2.7/site-packages/pyanaconda/ui/gui/spokes/custom.py", line 1027, in _do_refresh self._show_mountpoint(page=firstPage, mountpoint=mountpointToShow) File "/usr/lib64/python2.7/site-packages/pyanaconda/ui/gui/spokes/custom.py", line 884, in refresh self._do_refresh() File "/usr/lib64/python2.7/site-packages/pyanaconda/ui/gui/hubs/__init__.py", line 108, in _runSpoke action.refresh() File "/usr/lib64/python2.7/site-packages/pyanaconda/ui/gui/hubs/__init__.py", line 424, in _on_spoke_clicked self._runSpoke(spoke) File "/usr/lib64/python2.7/site-packages/pyanaconda/ui/gui/hubs/__init__.py", line 442, in _on_spoke_clicked self._on_spoke_clicked(self._spokes[dest].selector, None, self._spokes[dest]) AttributeError: 'NoneType' object has no attribute 'name' Additional info: cmdline: /usr/bin/python /sbin/anaconda --liveinst --method=livecd:///dev/mapper/live-base cmdline_file: BOOT_IMAGE=/syslinux/vmlinuz0 root=live:LABEL=LIVE ro rd.live.image quiet rhgb executable: /sbin/anaconda hashmarkername: anaconda kernel: 3.11.10-301.fc20.x86_64 product: Fedora release: Fedora release 20 (Heisenbug) type: anaconda version: 20
Created attachment 936329 [details] File: anaconda-tb
Created attachment 936330 [details] File: anaconda.log
Created attachment 936331 [details] File: environ
Created attachment 936332 [details] File: journalctl
Created attachment 936333 [details] File: lsblk_output
Created attachment 936334 [details] File: nmcli_dev_list
Created attachment 936335 [details] File: os_info
Created attachment 936336 [details] File: program.log
Created attachment 936337 [details] File: storage.log
Created attachment 936338 [details] File: ifcfg.log
This message is a reminder that Fedora 20 is nearing its end of life. Approximately 4 (four) weeks from now Fedora will stop maintaining and issuing updates for Fedora 20. 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 '20'. 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 20 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 20 changed to end-of-life (EOL) status on 2015-06-23. Fedora 20 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.