Description of problem:
The Updates section on Gnome Software doesn't show any updates, even though updates are available when checking with 'yum check-update'.
Version-Release number of selected component (if applicable):
Gnome Software 3.10.3
Steps to Reproduce:
1. Clean install from live media iso
2. Check Updates section on Gnome Software
3. Check updates with 'yum check-update'
No updates show on the Updates section of Gnome Software.
The same updates that show on 'yum check-update' were expected to show on the Updates section of Gnome Software.
System updates detected and installed successfully using yum.
I can confirm this bug. Only thing different is that I used Fedup to upgrade from F19 to F20;
Update: After touching /var/lib/PackageKit/prepared-update, gnome-software updates worked for me.
I tried touching /var/lib/PackageKit/prepared-update with no success, this message appears on stdout with or without prepared-update.
(gnome-software:3459): Gs-WARNING **: failed to get updates: no results to show
Seems to be working now though. The warning message disappeared as well.
We only show updates when they are all downloaded, depsolved and ready to be installed. If a repo is in an unstable state, we don't show the updates as we can't get a coherent set.
I'm seeing this too with F20. I've seen updates there previously, but now only show "software is up to date" available with the warning. Can download/check/install updates from yum as per normal.
Same issue here on F20 (x86_64) as comment #6
gnome-software says "Software is up to date" even if updates are listed in 'yum check-update'. This should be fixed. At least, there should be a message stating that "Updates exist and are processed. They will be displayed here only after everything is ready."
Same here. What should I do to fix this problem?
The problem with gnome-software is that it only show "prepared offline updates". The updates are prepared by a gnome component called "gnome-settings-daemon", which will every 24h check/download and prepare available updates. gnome-settings-daemon does this automatically and in the background.
You can force the download/preparation of offline updates via this terminal command: "$ pkcon update -d". this will download and prepare all available updates. After this command has finished you will see the available and prepared updates in gnome-software.
So this bug is not a bug, but rather the user has learned a different expectation in the past, but "$ pkcon update -d" will do the trick for most here, I guess.
Just so I get this right: to use this GUI tool for updating software I first have to open a terminal and run:
$ pkcon update -d
Is it reasonable to expect everyone, including my mom to remember to do this to get updates?
I'm not sure I see how this is a step forward from the previous updating tool which did everything via the one tool.
In 3.12 there's a manual refresh button to force getting the updates in the UI.
can we have a gnome independent mechanism for offline upating? `pkcon updates -d` followed by `pkcon offline-trigger` seems to do the job. But is hard to remember and no UI to remind you from time to time.
As a XFCE user I hope there is a better way than hooking everything into gnome.
(In reply to Aleksandar Kostadinov from comment #13)
> can we have a gnome independent mechanism for offline upating? `pkcon
> updates -d` followed by `pkcon offline-trigger` seems to do the job. But is
> hard to remember and no UI to remind you from time to time.
> As a XFCE user I hope there is a better way than hooking everything into
I think XFCE has to build it's own PackageKit client UI if it doesn't want to use the GNOME UI.
The problem is not the UI. The problem is that it is gnome backend that periodically checks for updates.
I don't believe there's anything specific left here that's fixable for F20; gnome-software in F21 improves the experience by letting you force the refresh, and the question of alternative clients for offline updates is interesting but not a bug for gnome-software. So I think it makes sense to close the bug at this point. If there are issues with updates in Fedora 21 it would be best to file them as new bugs to avoid confusion. Thanks!
Brian: you don't have to do that just to get updates, no. You have to do that if you know there are updates in the repos and you want them to show up in Software *right now*. The expectation behind the design is that users who update via Software don't necessarily need non-security updates to show up really fast; it isn't actually a problem if there's a delay before they appear (and in fact Software intentionally sets things up so non-critical updates show up periodically in a lump, not right away one piece at a time). And of course being able to do a refresh in the GUI helps in F21+.
@Adam: except that gnome-software *never* shows updates until I hit the refresh button.
As an aside, gnome-software is a serious regression over gpk-update-viewer in terms of the number of clicks required to go through the updates and see what they are updating. You first have to click on the OS Updates "section" and then for every update, click each one to open up a dialog to see what is being updated and then click a back button to go back to the list, to have to click again on another package name to see what is updated, etc.
And then there is no indication when you go back which one you clicked,
Additionally, if this is the new UI flow, it would be much more useful if all packages that had the same update reason were grouped together into a single item so that you click once for all of the packages that are in the same update reason.
But I digress -- into what is material for a new bug.
Another digression, but another regression over gpk-update-viewer is that there is no way to get some OS updates but not be forced into taking them all.
This issue is problematic for anyone who is only on their computer occasionally. I have a number of computers and one of them I log into only occasionally. When I do, I want to be able to force an update while logged in. Unfortunately, I have to into a terminal and remember "pkcon update -d". This is a tedious mechanism that is not user friendly. Disappointing.