Description of problem: I hadn't realized Gnome Software had improved so much, so I installed all available updates with DNF form terminal after checking for updates in Gnome Software. Then I opened Gnome software again and it said all the previous updated were still to be installed. SO I clicked "Restart & Installed". The system reset, appeared to install and rebooted back to login. I logged in and was told the updates had failed to install. I opened GNome software again and it still showed updates available, after I checked for updates, it finally released the updated did not need to be installed after all. Version-Release number of selected component (if applicable): Gnome Software: 3.16.1 DNF: 0.6.5 How reproducible: I haven't tried this, but it should reproduce if there are updated available. Steps to Reproduce: 1. Check for updates in Gnome software, once found. Close it. 2. In terminal, run DNF update and install. 3. Reopen gnome software and see it still says updates are available. Actual results: Shows updates previously installed with DNF as available to install. Expected results: Gnome Software should show no updates available. Additional info: Some sort of check should exist between the two processes.
Hm, this is supposed to work. gnome-software has code to detect anything else touching the rpm database and it is supposed to retract the update in that case.
Checked again on another system. Unless you explicitly check for updates after updating with DNF, Gnome Software will still think updates are available to install and try to install them. Whatever checks it has, its not doing them when the app is opened or after DNF runs.
Sorry, I forgot to comment in this bug. I debugged it the other day and it turned out to be a libhif regression - fixed in the pending libhif-0.2.0-3.fc22 update.
libhif-0.2.0-3.fc22 has been submitted as an update for Fedora 22. https://admin.fedoraproject.org/updates/libhif-0.2.0-3.fc22
libhif-0.2.0-3.fc22 has been pushed to the Fedora 22 stable repository. If problems still persist, please make note of it in this bug report.