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/lib/python3.4/site-packages/dnf/base.py", line 1203, in _add_comps_trans sltr = dnf.selector.Selector(self.sack) File "/usr/lib/python3.4/site-packages/dnf/base.py", line 1288, in group_install return self._add_comps_trans(trans) File "/usr/lib64/python3.4/site-packages/pyanaconda/packaging/dnfpayload.py", line 481, in _select_group self._base.group_install(grp, types, exclude=exclude) File "/usr/lib64/python3.4/site-packages/pyanaconda/packaging/dnfpayload.py", line 316, in _apply_selections self._select_group('core', required=True) File "/usr/lib64/python3.4/site-packages/pyanaconda/packaging/dnfpayload.py", line 589, in checkSoftwareSelection self._apply_selections() File "/usr/lib64/python3.4/site-packages/pyanaconda/ui/gui/spokes/software.py", line 216, in checkSoftwareSelection self.payload.checkSoftwareSelection() File "/usr/lib64/python3.4/threading.py", line 868, in run self._target(*self._args, **self._kwargs) File "/usr/lib64/python3.4/site-packages/pyanaconda/threads.py", line 253, in run threading.Thread.run(self, *args, **kwargs) TypeError: must be _hawkey.Sack, not None 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 dnf.rpm.log: Oct 24 04:30:41 INFO --- logging initialized --- 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 1086041 [details] File: anaconda-tb
Created attachment 1086042 [details] File: anaconda.log
Created attachment 1086043 [details] File: dnf.log
Created attachment 1086044 [details] File: environ
Created attachment 1086045 [details] File: lsblk_output
Created attachment 1086046 [details] File: nmcli_dev_list
Created attachment 1086047 [details] File: os_info
Created attachment 1086048 [details] File: storage.log
Created attachment 1086049 [details] File: syslog
Created attachment 1086050 [details] File: ifcfg.log
Created attachment 1086051 [details] File: packaging.log
Created attachment 1086052 [details] File: program.log
In dnf.log it is possible to see, that sac was loaded. Probably this is not a problem of DNF. Please ensure, that i other thread you do not call base.reset .
*** Bug 1279302 has been marked as a duplicate of this bug. ***
*** Bug 1313610 has been marked as a duplicate of this bug. ***
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.