Red Hat Bugzilla – Bug 1219669
Using dnf and gnome-software at the same time can break rpm
Last modified: 2016-07-19 15:34:18 EDT
I'm not sure if this is an issue with dnf or gnome-software. But after attempting to use both at the same time, rpm is broken.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Open a root terminal
2. dnf install gimp* -x *-devel*
3. Start gnome-software
4. Start installing something with gnome-software
5. Ctrl+C out of the dnf process in the terminal
gnome-software tells that it can't install the packages you asked it to install
rpm stops working entirely and says: "error: db5 error(-30973) from dbenv->open: BDB0087 DB_RUNRECOVERY: Fatal error, run database recovery"
After Ctrl+C'ing out of dnf, gnome-software should successfully install the packages it was asked to install and rpm should not break
thinks this should be filled against gnome-software, it should check is rpm is already in use
There are two things I can see here. First of all, dnf should properly close the rpmdb when Ctrl+C occurs (not sure if it does). Then there is rpmdb access synchronization from multiple processes at once. Adding Richard to CC, as he might have some insight what's happening.
We should check to close rpm transaction properly in DNF after hitting ctrl+c.
*** Bug 1227401 has been marked as a duplicate of this bug. ***
*** Bug 1227515 has been marked as a duplicate of this bug. ***
*** Bug 1299234 has been marked as a duplicate of this bug. ***
I've just duplicated again(after opening 1299234).
I'm in KDE Plasma Desktop on Fedora 23 x86_64
I do not get any errors, and nothing breaks. However, dnf and gnome-software are able to install/upgrade packages at the same time.
Are any of y'all still able to hit this bug? How about with Fedora 24?
This package has changed ownership in the Fedora Package Database. Reassigning to the new owner of this component.
Fedora 22 changed to end-of-life (EOL) status on 2016-07-19. Fedora 22 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
Thank you for reporting this bug and we are sorry it could not be fixed.