Version-Release number of selected component: dnf-3.5.1-1.fc29 Additional info: reporter: libreport-2.9.5 cmdline: /usr/bin/python3 /usr/bin/dnf history list crash_function: __init__ exception_type: RuntimeError executable: /usr/bin/dnf interpreter: python3-3.7.0-9.fc29.x86_64 kernel: 4.18.5-300.fc29.x86_64 runlevel: N 5 type: Python3 uid: 1000 Truncated backtrace: transaction.py:729:__init__:RuntimeError: C++ std::exception: Failed to open backup database: /var/lib/dnf/history/history-2016-06-14.sqlite Traceback (most recent call last): File "/usr/bin/dnf", line 58, in <module> main.user_main(sys.argv[1:], exit_code=True) File "/usr/lib/python3.7/site-packages/dnf/cli/main.py", line 179, in user_main errcode = main(args) File "/usr/lib/python3.7/site-packages/dnf/cli/main.py", line 64, in main return _main(base, args, cli_class, option_parser_class) File "/usr/lib/python3.7/site-packages/dnf/cli/main.py", line 95, in _main cli.configure(list(map(ucd, args)), option_parser()) File "/usr/lib/python3.7/site-packages/dnf/cli/cli.py", line 913, in configure self.command.configure() File "/usr/lib/python3.7/site-packages/dnf/cli/commands/__init__.py", line 849, in configure if not os.access(self.base.history.path, os.R_OK): File "/usr/lib/python3.7/site-packages/dnf/db/history.py", line 310, in path return self.swdb.getPath() File "/usr/lib/python3.7/site-packages/dnf/db/history.py", line 291, in swdb self._swdb = libdnf.transaction.Swdb(self.dbpath) File "/usr/lib64/python3.7/site-packages/libdnf/transaction.py", line 729, in __init__ this = _transaction.new_Swdb(*args) RuntimeError: C++ std::exception: Failed to open backup database: /var/lib/dnf/history/history-2016-06-14.sqlite Local variables in innermost frame: self: <libdnf.transaction.Swdb; > args: ('/var/lib/dnf/history.sqlite',)
Created attachment 1488537 [details] File: _var_log_dnf.log
Created attachment 1488538 [details] File: backtrace
Created attachment 1488539 [details] File: cgroup
Created attachment 1488540 [details] File: cpuinfo
Created attachment 1488541 [details] File: dnf-makecache.log
Created attachment 1488542 [details] File: environ
Created attachment 1488543 [details] File: mountinfo
Created attachment 1488544 [details] File: namespaces
Created attachment 1488545 [details] File: open_fds
This happens when a non-privileged user runs dnf before root runs it. Dnf attempts to migrate the history database and fails on write permissions.
PR: https://github.com/rpm-software-management/libdnf/pull/765
This message is a reminder that Fedora 29 is nearing its end of life. Fedora will stop maintaining and issuing updates for Fedora 29 on 2019-11-26. 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 '29'. 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 29 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 29 changed to end-of-life (EOL) status on 2019-11-26. Fedora 29 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.