GNOME Bugzilla – Bug 740395
Software claims it checked for updates at a time when it had no Internet connection
Last modified: 2018-01-24 16:54:15 UTC
Today I booted my laptop with no connection to the Internet, opened Software, and visited the updates page. It correctly displayed a message telling me that I was offline, and that I should go online to check for updates. After activating my connection, the message changed immediately to the no updates available message, which was an unbelievable lie as I haven't updated in two weeks. I then noticed that last checked for updates time was 10 minutes prior, when I had activated the Internet connection only a minute or two prior. Software should only present times here if the check was actually successful (which it could not possibly have been, with no Internet connection).
I have a similar problem with gnome-software 3.14. 1. Boot the computer. 2. Open gnome-software and look at the Updates tab, it says "Software is up to date", "Last checked: <a few minutes ago>". 3. Click on the button to check for new updates. -> updates are available. The "Last checked: ..." was wrong. I have this error quite often, if not each time. On Fedora 21.
If we check and have no internet connection it still counts as a check. Perhaps we should only update the counter if we successfully download new updates, although then we'd need one counter for UI and one for the action to avoid doing an update check every hour if it keeps failing.
I see this bug still in current Fedora 25. Since I'm commuting, every morning (i.e., every time I boot my laptop) I don't have an internet connection available. Since software is silently failing to check for updates (because there is no internet connection), I always have to manually check for updates (something that not every user is aware of, I guess). I suggest the following: If there is no internet connection, schedule a new check for updates once internet connection becomes available again (or 10 minutes later).
-- 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/17.