1444676 - Gnome extensions addon doesn't detect running shell

Status: RESOLVED INVALID

(WebExtensions :: General, defect)

Description

[Sarah Bird]

On Nightly, when I go to extensions.gnome.org to manage my shell extensions it tells me that my shell integration isn't present and that I need to install it as per (https://wiki.gnome.org/Projects/GnomeShellIntegrationForChrome/Installation)

However, it is present and running. 

I do not see the same error when I run FF58 on same machine with same profile.

Comment 1

[Sarah Bird]

The exact error message is "Although GNOME Shell integration extension is running, native host connector is not detected. Refer documentation for instructions about installing connector."

My version of Nightly is: 60.0a1 (2018-03-10) (64-bit)

Comment 2

[Jorge Villalobos [:jorgev] (he/him)]

Have you reported this to the developers of this extension? It's unclear if this is a bug in Firefox.

Comment 3

[Andrew Swan [:aswan]]

(In reply to Jorge Villalobos [:jorgev] from comment #2)
> It's unclear if this is a bug in Firefox.

When an extension uses native messaging but the native application cannot be found or cannot be run, errors are logged to the browser console:
https://developer.mozilla.org/en-US/docs/Tools/Browser_Console

Is there anything that looks relevant there?

Comment 4

[Sarah Bird]

(In reply to Jorge Villalobos [:jorgev] from comment #2)
> Have you reported this to the developers of this extension? It's unclear if
> this is a bug in Firefox.

But it works on 59?


(In reply to Andrew Swan [:aswan] from comment #3)
> 
> When an extension uses native messaging but the native application cannot be
> found or cannot be run, errors are logged to the browser console:
> https://developer.mozilla.org/en-US/docs/Tools/Browser_Console
> 
> Is there anything that looks relevant there?

There's nothing useful in console, there's just a message about the css source map not being available, which is nothing to worry about.

Comment 5

[Sarah Bird]

> But it works on 59?

Sorry, I meant it works on 58.

Comment 6

[Andrew Swan [:aswan]]

It sounds like native messaging is working okay then (either that or its never getting invoked at all).  The problem could be elsewhere in their extension, I guess the next step is for somebody to narrow it down more specifically to what exactly is failing (ideally somebody who is already familiar with the extension and how it is implemented).

Comment 7

[Andrew Swan [:aswan]]

There's not much for us to go on here, if one of the maintainers of the addon in question can narrow this down to an issue with a particular webextension API we can pick it up from there.

Comment 8

[Jorge Villalobos [:jorgev] (he/him)]

Please report this to the add-on developers. If they can confirm it's a compatibility issue, please reopen.