After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 722924 - Allow manual checking for updates
Allow manual checking for updates
Status: RESOLVED FIXED
Product: gnome-software
Classification: Applications
Component: General
3.11.x
Other Linux
: Normal enhancement
: ---
Assigned To: GNOME Software maintainer(s)
GNOME Software maintainer(s)
ux 3.12
Depends on:
Blocks:
 
 
Reported: 2014-01-24 18:15 UTC by Allan Day
Modified: 2014-02-05 14:09 UTC
See Also:
GNOME target: ---
GNOME version: 3.11/3.12



Description Allan Day 2014-01-24 18:15:10 UTC
Until now, we have only shown updates when they have been downloaded, and we haven't provided a way to manually check for updates. There are a number of problems with this:

 * Sometimes people might need a particular update for something, and want a way to check if it is available.
 * Most operating systems provide a way to manually check for updates - it is something of a convention.
 * When you go to the updates view and it says "software is up to date", sometimes it is a lie.
 * In the past we used to provide a way to manually check for updates (and we have an unresolved bug about this in the control center - see bug 720946).

So it might be desirable to have a way to manually check for updates, for which we now have mockups:

https://raw.github.com/gnome-design-team/gnome-mockups/master/software/version2/wire-updates-updates.png

One thing I am uneasy about with this design is the presence of the "refresh" button when a list of updates already exists [1] (meaning that they have been downloaded and are ready to be installed). The whole point of downloading updates in the background is to avoid people having to manually check and watch a slow progress bar, yet if we provide a refresh button many people will instinctively use it.

I'd like to get some design feedback before proceeding.

[1] Unfortunately it is hard to be 100% up-to-date and download updates in the background.
Comment 1 Michael Catanzaro 2014-01-26 16:29:57 UTC
(In reply to comment #0)
>  * When you go to the updates view and it says "software is up to date",
> sometimes it is a lie.

Today I opened GNOME Software to install an application.  I searched for the application, then noticed that I had updates available: the updates tab was pulsing blue and even indicated the number of updates there were. I clicked Install to install the application, then switched over to the updates page to install my updates, but of course installing the application invalidated my updates, so Software claimed that everything was up-to-date, even though it was presenting me with updates just a few seconds ago.

With or without the refresh button, those wireframes address all of my concerns.
Comment 2 Allan Day 2014-01-27 13:47:27 UTC
(In reply to comment #0)
...
> One thing I am uneasy about with this design is the presence of the "refresh"
> button when a list of updates already exists [1] (meaning that they have been
> downloaded and are ready to be installed). The whole point of downloading
> updates in the background is to avoid people having to manually check and watch
> a slow progress bar, yet if we provide a refresh button many people will
> instinctively use it.
> 
> I'd like to get some design feedback before proceeding.

I discussed this with Jon Mccann last Friday. He agreed that the situation I described above isn't great, but also that there might not be a better solution.

Also, I've updated the wireframes:

https://raw.github.com/gnome-design-team/gnome-mockups/master/software/version2/wire-updates-updates.png
Comment 3 Richard Hughes 2014-02-05 14:09:04 UTC
All implemented now, thanks. There are a few visual nits still to clean up, but certainly good enough for closing this bug. Thanks all.