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 783469 - Unable to check for extension updates notification too verbose
Unable to check for extension updates notification too verbose
Status: RESOLVED FIXED
Product: chrome-gnome-shell
Classification: Other
Component: Browser extension
unspecified
Other Linux
: Normal normal
: ---
Assigned To: Yuri Konotopov
chrome-gnome-shell panel maintainer(s)
https://git.gnome.org/browse/chrome-g...
Depends on:
Blocks:
 
 
Reported: 2017-06-06 11:35 UTC by Inactive account
Modified: 2017-06-12 18:00 UTC
See Also:
GNOME target: ---
GNOME version: 3.23/3.24


Attachments
Verbose_extension_update_notification.png (28.58 KB, image/png)
2017-06-06 11:35 UTC, Inactive account
Details

Description Inactive account 2017-06-06 11:35:14 UTC
Created attachment 353255 [details]
Verbose_extension_update_notification.png

On my Arch Linux installation with GNOME 3.24.2 I have found that if my system can't check for updates to my GNOME Shell extensions due to the lack of an internet connection that I get a rather big and unnecessarily verbose notification:

    Verbose_extension_update_notification.png

This might be useful in a log, but certainly not in one of these notifications. This is really debugging information, it is only likely to confuse and concern normal users. In fact, I don't think that the solution would even be to make the message more user friendly, but I think that although this could be recorded in a log somewhere, that actually it should just fail silently given that it's not a very important thing and could just try again in 5 minutes or something. For instance, when gnome-software checks for updates it doesn't display something like this, but rather fails silently and then tries again later.

I am not entirely clear on which application deals with this, so I'm just going to put this bug initially under gnome-shell, please move it to the appropriate place, unless that is it of course.
Comment 1 Florian Müllner 2017-06-06 13:17:20 UTC
Apparently it's the chrome-gnome-shell plugin ...
Comment 2 Yuri Konotopov 2017-06-12 18:00:08 UTC
Fixed in commit ea33e2e0