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 724076 - Extension should not be enabled after update if it was disabled before
Extension should not be enabled after update if it was disabled before
Status: RESOLVED OBSOLETE
Product: gnome-shell
Classification: Core
Component: extensions
3.20.x
Other Linux
: Normal normal
: ---
Assigned To: gnome-shell-maint
gnome-shell-maint
Depends on:
Blocks:
 
 
Reported: 2014-02-10 22:32 UTC by Nazar Mokrynskyi
Modified: 2021-07-05 14:43 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Nazar Mokrynskyi 2014-02-10 22:32:10 UTC
Bug in title, and fix should be pretty simple.
Comment 1 Yuri Konotopov 2017-02-12 09:02:25 UTC
Fixed
Comment 2 Yuri Konotopov 2017-02-12 09:22:21 UTC
Please note, that this will not work with NPAPI plugin, but will work with chrome-gnome-shell browser extension.

For some reason NPAPI plugin do not calls Deferred callback, so I redirecting this issue to GNOME Shell devs
Comment 3 Yuri Konotopov 2017-02-12 09:26:56 UTC
NPAPI object method "installExtension" is called by website [1], passing 2 js function - success and fail callbacks.
For some reason success callback newer called by NPAPI plugin, but it should [2] as I see.

[1] https://git.gnome.org/browse/extensions-web/tree/sweettooth/static/js/versions/common/common.js#n71
[2] https://git.gnome.org/browse/gnome-shell/tree/browser-plugin/browser-plugin.c#n478
Comment 4 Pander 2017-05-12 09:51:37 UTC
Still disabled extensions which are upgraded via https://extensions.gnome.org/local/ get enabled after the upgrade. As far as I am concerned this is even a security issue as some extensions work with your location and other posisble sensitive data. Please increase the priority of this bug.
Comment 5 Florian Müllner 2017-11-25 06:33:55 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-test.gnome.org/fmuellner/gnome-shell-extensions/issues/107.
Comment 6 Florian Müllner 2017-11-25 08:59:46 UTC
Sorry for the noise, I "found" a bug in the migration script:
https://gitlab.gnome.org/External/bugzilla-to-gitlab-migrator/issues/2
Comment 7 GNOME Infrastructure Team 2021-07-05 14:43:02 UTC
GNOME is going to shut down bugzilla.gnome.org in favor of  gitlab.gnome.org.
As part of that, we are mass-closing older open tickets in bugzilla.gnome.org
which have not seen updates for a longer time (resources are unfortunately
quite limited so not every ticket can get handled).

If you can still reproduce the situation described in this ticket in a recent
and supported software version, then please follow
  https://wiki.gnome.org/GettingInTouch/BugReportingGuidelines
and create a new ticket at
  https://gitlab.gnome.org/GNOME/gnome-shell/-/issues/

Thank you for your understanding and your help.