GNOME Bugzilla – Bug 763566
Software provides incorrect information regarding availability of updates
Last modified: 2018-01-24 17:01:48 UTC
Created attachment 323792 [details] Screenshot of bug See attached screenshot. I opened the Updates tab at 9:50. Software said it is up to date, last checked 9:50. I then clicked Refresh, and it said it's up to date, last checked 9:51. But dnf finds 80 updates. The "last checked" claim is obviously BS. Please *actually* check for updates when I click the refresh button without returning early for whatever reason. Related: After running 'dnf update' but not proceeding with the dnf update, and clicking the Refresh button in Software again, it's then on the third try, eight minutes later, finally able to find the updates.
Lets just say the title of the bug is nonconductive to fixing this. 'lie' implies bad intent. I think you should tone that down a little if you are interested in a constructive solution instead of bickering
(In reply to Matthias Clasen from comment #1) > Lets just say the title of the bug is nonconductive to fixing this. 'lie' > implies bad intent. I think you should tone that down a little if you are > interested in a constructive solution instead of bickering Sorry, let's go with "Software provides incorrect information regarding availability of updates"
Any plans to look into this? Fedora has been dinged for this ever since we switched to GNOME Software. It's still broken in Fedora 24. For instance, today on my computer that had not been updated in a week, Software said it was up to date, and that the last check for updates was one minute ago. However, pressing the refresh button caused it to immediately begin downloading updates. So this is not just some state tracking difference between PackageKit and dnf.
An easy, almost 100% reproducer is to do a fresh install of F23 and visit the updates tab in GNOME Software... it will say all software is up to date. Click the refresh button, it will spin for a bit and then report all software up to date. Something's wrong there; of course there are hundreds of updates since F23 was released. Wait about 10 minutes and then the check will finally work.
See also: PackageKit issue #157
(In reply to Michael Catanzaro from comment #5) > See also: PackageKit issue #157 where is this PackageKit issue #157 ? I think this is a problem of cache age , when you click refresh you call: pkcon refresh but if you run at terminal as root: pkcon refresh force you will get the updates, so set cache age lower will help you , in apper I can setup it but in gnome-software I don't find it . bottom line, if when we press refresh it call "pkcon refresh force" should fix this issue, the question is if we should have 2 refresh buttons , one light refresh and other force refresh to regenerate all cache.
(In reply to Sergio from comment #6) > where is this PackageKit issue #157 ? https://github.com/hughsie/PackageKit/issues/157 > the question is if we should have 2 refresh buttons Definitely not. Users have no clue what a cache is. Refresh just needs to work. :)
(In reply to Michael Catanzaro from comment #7) > (In reply to Sergio from comment #6) > > where is this PackageKit issue #157 ? > > https://github.com/hughsie/PackageKit/issues/157 > > > the question is if we should have 2 refresh buttons > > Definitely not. Users have no clue what a cache is. Refresh just needs to > work. :) but do you get updates ? if you run at terminal as root: pkcon refresh force
Today I noticed that if I run 'dnf update' to update a single package while the Updates page is shown, Software goes from showing the updates to showing "all up to date" which is totally wrong, it should have gone back to "checking for updates." (In reply to Sergio from comment #8) > but do you get updates ? if you run at terminal as root: > pkcon refresh force My comment was about the desired behavior of the refresh button in the UI, I wasn't intending to contradict your observation!
(In reply to Michael Catanzaro from comment #9) > (In reply to Sergio from comment #8) > > but do you get updates ? if you run at terminal as root: > > pkcon refresh force > > My comment was about the desired behavior of the refresh button in the UI, I > wasn't intending to contradict your observation! but if you confirm that running: pkcon refresh force fix your problem, we may have more information .
-- GitLab Migration Automatic Message -- This bug has been migrated to GNOME's GitLab instance and has been closed from further activity. You can subscribe and participate further through the new bug through this link to our GitLab instance: https://gitlab.gnome.org/GNOME/gnome-software/issues/42.