Hide Forgot
Version-Release number of selected component: dnf-1.1.7-2.fc23 Additional info: reporter: libreport-2.6.4 cmdline: /usr/bin/python3 -OO /bin/dnf update executable: /bin/dnf kernel: 4.2.3-300.fc23.x86_64 runlevel: N 5 type: Python3 uid: 0 Truncated backtrace: rpmtrans.py:558:_scriptError:AttributeError: 'NoneType' object has no attribute 'name' Traceback (most recent call last): File "/usr/lib/python3.4/site-packages/dnf/yum/rpmtrans.py", line 427, in callback self._scriptError(bytes, total, h) File "/usr/lib/python3.4/site-packages/dnf/yum/rpmtrans.py", line 558, in _scriptError name = pkg.name AttributeError: 'NoneType' object has no attribute 'name' Local variables in innermost frame: _: None bytes: 262144 pkg: None self: <dnf.yum.rpmtrans.RPMTransaction object at 0x7fc13ab83da0> scriptlet_name: '<unknown>' total: 0 h: None
Created attachment 1143149 [details] File: _var_log_dnf.log
Created attachment 1143150 [details] File: backtrace
Created attachment 1143151 [details] File: dnf-makecache.log
Created attachment 1143152 [details] File: environ
We'll take a look.
This package has changed ownership in the Fedora Package Database. Reassigning to the new owner of this component.
I would like to investigate the bug, but somehow I don't know how to reproduce it. It fails when RPMCALLBACK_SCRIPT_ERROR appear, but I don't know which package has triggered this error. Please any information to reproduce it will be very useful. The best would be exact package name and from which version to which version it appears. Probably the information that I am looking for is in dnf.rpm.log but it is long time ago gone.
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.
*** This bug has been marked as a duplicate of bug 1397047 ***