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 686038 - GNOME not detected
GNOME not detected
Status: RESOLVED OBSOLETE
Product: website
Classification: Infrastructure
Component: extensions.gnome.org
current
Other Linux
: Normal normal
: ---
Assigned To: Shell extensions maintainer(s)
Shell extensions maintainer(s)
: 733111 734552 736728 741575 744825 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2012-10-12 15:08 UTC by Shadowblade
Modified: 2017-01-29 19:45 UTC
See Also:
GNOME target: ---
GNOME version: ---


Attachments
Screenshot (112.21 KB, image/png)
2012-10-12 15:08 UTC, Shadowblade
Details

Description Shadowblade 2012-10-12 15:08:54 UTC
Created attachment 226337 [details]
Screenshot

On August 23, Ubuntu 12.04.1 was released.
I have since re-installed 3 new PCs with Ubuntu 12.04.1, a clean install from a LiveCD.

As I am not a fan of the Unity shell, I always install the gnome (3) shell.

However, on all 3 installations it has been impossible to install extensions from https://extensions.gnome.org/.

The error message shown at the top of the page is always the same:
"You do not appear to have an up to date version of GNOME3. You won't be able to install extensions from here. See the about page for more information."

According to the system tab of the System Monitor, I am running:
GNOME 3.4.2
This is the specific version of the gnome shell:
apt-cache show gnome-shell | grep Version
Version: 3.4.1-0ubuntu2

As much as I like Gnome3, it is not usable (IMHO) without a couple of extensions.
Personally that makes this issue 'critical' for me.

Kind regards,

Shadowblade
Comment 1 André Klapper 2012-10-13 09:15:54 UTC
Is the "GNOME Shell Integration" plugin installed in your browser?
Comment 2 Shadowblade 2012-10-13 19:54:46 UTC
Yes, the 'Gnome Shell Integration Plugin' is installed.
It is the version from 04/18/2012.
(using Firefox 16 at the moment)

Like I said, I'm afraid I am using a pretty standard install.
- clean Ubuntu 12.04.1 install
- sudo apt-get install gnome-shell
- gnome extensions will not install :(

Looks like there is a bug that makes extensions.gnome.org think that my gnome install is older than it really is.

Shadowblade
Comment 3 Jasper St. Pierre (not reading bugmail) 2012-10-13 20:00:51 UTC
Is click-to-play enabled? Try disabling it.
Comment 4 Shadowblade 2012-10-13 22:43:17 UTC
Hi Jasper,

Yes, 'plugins.click_to_play' was set to 'true' in about:config.
I had been using this feature to replace the add-on 'FlashBlock'.

After setting 'plugins.click_to_play' back to 'false', the error on extensions.gnome.org disappeared. Thank you very much for this solution!

Wouldn't it be good if extensions.gnome.org would show a better error message than:
"You do not appear to have an up to date version of GNOME3. You won't be able
to install extensions from here. See the about page for more information."

Why is the site assuming that the GNOME version is too old, when all that is happening is the "GNOME Shell Integration" plugin isn't being allowed to run automatically?

Or maybe it's an idea to at least make a mention of this issue on:
https://extensions.gnome.org/about/

Any gnome user with a recent Firefox and 'plugins.click_to_play' set to 'true' could face similar problems, right?

Shadowblade
Comment 5 Jasper St. Pierre (not reading bugmail) 2012-10-13 23:11:28 UTC
(In reply to comment #4)
> Hi Jasper,
> 
> Yes, 'plugins.click_to_play' was set to 'true' in about:config.
> I had been using this feature to replace the add-on 'FlashBlock'.
> 
> After setting 'plugins.click_to_play' back to 'false', the error on
> extensions.gnome.org disappeared. Thank you very much for this solution!
> 
> Wouldn't it be good if extensions.gnome.org would show a better error message
> than:
> "You do not appear to have an up to date version of GNOME3. You won't be able
> to install extensions from here. See the about page for more information."
> 
> Why is the site assuming that the GNOME version is too old, when all that is
> happening is the "GNOME Shell Integration" plugin isn't being allowed to run
> automatically?

Because I don't know that. The information I get back is simply that I don't have any API to install extensions, it doesn't tell me why it failed. You could not have the plugin (Windows, OS X, another Linux DE, stupid distribution packages it separately), it could have failed in a mysterious way (unsupported browser, bug in the plugin), the browser could just not have ran it (click-to-play).

I guess the error made sense for the 3.0 => 3.2 transition, but it's been a few releases. I'll adjust the error over the weekend.

Do you have any suggestions for a new wording?
Comment 6 Shadowblade 2012-11-20 16:52:05 UTC
(In reply to comment #5)
> (In reply to comment #4)
> > Hi Jasper,
> > 
> > Yes, 'plugins.click_to_play' was set to 'true' in about:config.
> > I had been using this feature to replace the add-on 'FlashBlock'.
> > 
> > After setting 'plugins.click_to_play' back to 'false', the error on
> > extensions.gnome.org disappeared. Thank you very much for this solution!
> > 
> > Wouldn't it be good if extensions.gnome.org would show a better error message
> > than:
> > "You do not appear to have an up to date version of GNOME3. You won't be able
> > to install extensions from here. See the about page for more information."
> > 
> > Why is the site assuming that the GNOME version is too old, when all that is
> > happening is the "GNOME Shell Integration" plugin isn't being allowed to run
> > automatically?
> 
> Because I don't know that. The information I get back is simply that I don't
> have any API to install extensions, it doesn't tell me why it failed. You could
> not have the plugin (Windows, OS X, another Linux DE, stupid distribution
> packages it separately), it could have failed in a mysterious way (unsupported
> browser, bug in the plugin), the browser could just not have ran it
> (click-to-play).
> 
> I guess the error made sense for the 3.0 => 3.2 transition, but it's been a few
> releases. I'll adjust the error over the weekend.
> 
> Do you have any suggestions for a new wording?

Hi Jasper,

I have just re-read the about page (https://extensions.gnome.org/about/).
Lots of information there, but I find that the big picture about how plugins are installed is missing.
Your explanation seems to suggest this model:

gnome3 <-> browser <-> plugin <-> extensions.gnome.org

Maybe this could be used to a structure a Trouble Shooting section?
1) gnome3: have you got the right version? are you behind a proxy? ...
2) browser: are you using a compatible browser? is it allowing plugins to function automatically? ...
3) plugin: is the Gnome Shell Integration plugin installed? is it enabled? ...
4) extensions.gnome.org: ... ? ...

If extensions.gnome.org detects that the  API to install extensions is missing, it should show a simple but clear warning and redirect to the Trouble Shooting section?

Thanks again for helping out.
Extensions have been working perfectly since I stopped using the new click-to-play functionality build into Firefox.

Shadowblade
Comment 7 Alexandre Franke 2015-07-02 18:32:21 UTC
*** Bug 744825 has been marked as a duplicate of this bug. ***
Comment 8 Alexandre Franke 2015-07-02 18:32:43 UTC
*** Bug 741575 has been marked as a duplicate of this bug. ***
Comment 9 Alexandre Franke 2015-07-02 18:33:05 UTC
*** Bug 734552 has been marked as a duplicate of this bug. ***
Comment 10 Alexandre Franke 2015-07-02 18:33:24 UTC
*** Bug 733111 has been marked as a duplicate of this bug. ***
Comment 11 Alexandre Franke 2015-07-02 19:06:41 UTC
*** Bug 736728 has been marked as a duplicate of this bug. ***
Comment 12 tinnitus 2016-04-29 20:04:33 UTC
Hi,
Impossible to install extensions from https://extensions.gnome.org/.
The system says:
"We cannot detect a running copy of GNOME on this system, so some parts of the interface may be disabled."

Some pieces of information:
$ apt-cache show gnome | grep Version
Version: 1:3.14+3

$ apt-cache show gnome-shell | grep Version
Version: 3.14.4-1~deb8u1

$ dpkg --status gnome-shell-extensions
Package: gnome-shell-extensions
Status: install ok installed

$ uname -ar
Linux debian 3.16.0-4-amd64 #1 SMP Debian 3.16.7-ckt20-1+deb8u4 (2016-02-29) x86_64 GNU/Linux

$ apt-cache show iceweasel | grep Version
Version: 38.7.0esr-1~deb8u1
Version: 38.5.0esr-1~deb8u2

The "GNOME Shell Integration" plugin is installed in Iceweasel and it is allowed to run automatically.

The 'plugins.click_to_play' is set to 'false'.

I am an end-user and I would like to use the gnome-shell extensions.

Best regards,
Tinnitus
Comment 13 Yuri Konotopov 2017-01-29 19:45:21 UTC
NPAPI is deprecated by Mozilla [1].
Try to migrate to chrome-gnome-shell [2].

If you are using Firefox ESR and want to continue using NPAPI plugin until it will be fully dropped, then just allow "GNOME Shell integration" plugin to "always" run at extensions.gnome.org and reload page.

[1] https://blogs.gnome.org/ne0sight/2016/12/25/how-to-install-gnome-shell-extensions-with-firefox-52/
[2] https://wiki.gnome.org/Projects/GnomeShellIntegrationForChrome/Installation