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 781969 - Attempting to update extensions through browser fails and messes everything up
Attempting to update extensions through browser fails and messes everything up
Status: RESOLVED OBSOLETE
Product: chrome-gnome-shell
Classification: Other
Component: Native messaging connector
9
Other Linux
: Normal major
: ---
Assigned To: Yuri Konotopov
chrome-gnome-shell panel maintainer(s)
Depends on:
Blocks:
 
 
Reported: 2017-04-30 13:25 UTC by Inactive account
Modified: 2018-05-22 12:07 UTC
See Also:
GNOME target: ---
GNOME version: 3.23/3.24


Description Inactive account 2017-04-30 13:25:20 UTC 
I have found the same issue with Firefox (though I have not yet been able to test in any other browser not using the NPAPI plugin) as I have with Epiphany in bug #781851. The only real difference between the Firefox and Epiphany experience is that with Firefox I don't get the "ERROR" message on the site and the extensions do actually seem to update properly, but it turns them all on and doesn't allow me to disable them until I restart the system. It also messed the AO up and made the extensions not function properly.

Further information including screenshots can be found at the bug I mentioned as I basically get all the same stuff. I am running the latest version of Arch Linux and have manually v9 of chrome-gnome-shell from the Git repository.
Comment 1 Inactive account 2017-04-30 13:33:08 UTC 
In the description above I meant to say that I have manually compiled v9 of chrome-gnome-shell from the Git repository.
Comment 2 Inactive account 2017-04-30 13:35:52 UTC 
Downstream LP bug: https://bugs.launchpad.net/ubuntu-gnome/+bug/1687288
Comment 3 Yuri Konotopov 2018-03-20 17:35:36 UTC 
Please attach corresponding GNOME Shell log.

If you are using systemd then you can do something like:
1. journalctl -f
2. Reproduce error
Comment 4 GNOME Infrastructure Team 2018-05-22 12:07:10 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/chrome-gnome-shell/issues/1.