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 757137 - No update description post-install
No update description post-install
Status: RESOLVED OBSOLETE
Product: gnome-software
Classification: Applications
Component: General
3.18.x
Other Linux
: Normal normal
: ---
Assigned To: GNOME Software maintainer(s)
GNOME Software maintainer(s)
Depends on:
Blocks:
 
 
Reported: 2015-10-26 11:58 UTC by Andreas Nilsson
Modified: 2018-01-24 16:59 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Andreas Nilsson 2015-10-26 11:58:49 UTC 
I did an update today and one of the applications was gnome-builder.
I'm pretty sure it said it had fixed vala autocompletion before I hit "reboot and install". However, when I was done with the update and brought up the window to review the install, gnome-builder only showed "No update description available.". Same for all the other updates.
Comment 1 Kalev Lember 2015-10-26 12:21:30 UTC 
What I think happened here was that you got a gnome-builder update from updates-testing together with a fedora-repos update that disabled updates-testing. After the fedora-repos update, gnome-software no longer sees any metadata for packages that came from updates testing, including updateinfo for gnome-builder.

One way to fix it might be to write the update description to /var/cache/update-competed during the offline update so that it doesn't need to read the repo metadata to review installed updates. Perhaps it would make sense to fix it together with the "competed" typo and and switch to an xml format at the same time, /var/cache/update-completed.xml or so.
Comment 2 Michael Catanzaro 2015-10-26 16:05:40 UTC 
(In reply to Kalev Lember from comment #1)
> One way to fix it might be to write the update description to
> /var/cache/update-competed during the offline update so that it doesn't need
> to read the repo metadata to review installed updates.

Then you could also get rid of the weird spinner delay before the installed update descriptions are available.
Comment 3 GNOME Infrastructure Team 2018-01-24 16:59:06 UTC 
-- 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/34.