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 741506 - GUI thinks restart is needed to install updates that are already installed
GUI thinks restart is needed to install updates that are already installed
Status: RESOLVED OBSOLETE
Product: gnome-software
Classification: Applications
Component: General
3.14.x
Other Linux
: Normal normal
: ---
Assigned To: GNOME Software maintainer(s)
GNOME Software maintainer(s)
Depends on:
Blocks: 741715
 
 
Reported: 2014-12-14 12:41 UTC by Samael
Modified: 2015-09-20 12:25 UTC
See Also:
GNOME target: ---
GNOME version: ---

Attachments
screenshot showing the problem (401.95 KB, image/jpeg)
2014-12-14 12:45 UTC, Samael 		Details

Description Samael 2014-12-14 12:41:15 UTC 
after installing the Latest Fedora that has gnome-software 3.14.2 I ran an update using yum in thew terminal to get my system up to date.

I later opened gnome-software to find new packages. the GUI says there are 13 updates pending that require a restart. odd seeing as I'd already updated my system prior to opening the app but I decided to go with it and do reboot.

After reboot gnome has a message from software that shows failed updates due to the packages already being installed. 

There are two problems though:

- the window that lists the failed packages is too tall to even fit the screen and has no way to get closed without exiting the application all togther. A scrollable widget would be better.

- even though my software is up to date and gnome-software still states that a restart is required to install pending updates.

Hope this is helpful - first time I've logged a gnome bug
Comment 1 Samael 2014-12-14 12:45:21 UTC 
Created attachment 292692 [details]
screenshot showing the problem
Comment 2 Alexandre Franke 2015-09-20 12:25:28 UTC 
I don't notice that issue anymore on F22 with 3.16, and I did when I was still on F21, so I think the situation has been improved. Feel free to reopen if you still notice the issue.