Bug 26647 - Unable to use the gnome extensions using the firefox plugin
Summary: Unable to use the gnome extensions using the firefox plugin
Status: RESOLVED FIXED
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: 7
Hardware: All Linux
Priority: Normal major
Target Milestone: ---
Assignee: GNOME maintainers
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks: 28788
  Show dependency treegraph
 
Reported: 2020-05-19 21:55 CEST by Olivier FAURAX
Modified: 2021-06-02 09:56 CEST (History)
2 users (show)

See Also:
Source RPM: chrome-gnome-shell-10.1-3.mga7.src.rpm
CVE:
Status comment:


Attachments
Screenshot of the website saying the connector (addon) is not working (27.12 KB, image/png)
2020-08-28 08:20 CEST, Olivier FAURAX
Details
Addon currently available (93.28 KB, image/png)
2020-08-28 08:23 CEST, Olivier FAURAX
Details

Description Olivier FAURAX 2020-05-19 21:55:02 CEST
On https://extensions.gnome.org we should be able to add extensions to gnome.
But I have a red warning that the integration extension is there, but the connector.

However, chrome-gnome-shell is installed so this should work (and worked before).

I will send a screenshot.

I rank it as major as the package is useless.
Comment 1 Lewis Smith 2020-05-20 21:02:48 CEST
Having looked into this, I remain baffled by where it lives and what it is supposed to do. Enable certain Gnome activities from a browser?
"To control GNOME Shell extensions using this site you must install GNOME Shell integration that consists of two parts: browser extension and native host messaging application."
Plus:
"You MUST install native connector for this extension to work.
For Debian, Fedora, Gentoo and Ubuntu you can install package named "chrome-gnome-shell"." Implicitly Mageia also.

These seem to be the current things available:
 gnome-shell-extension-hibernate-status
 gnome-shell-extension-topicons
 gnome-shell-extensions-apps-menu
 gnome-shell-extensions-auto-move-windows
 gnome-shell-extensions-common
 gnome-shell-extensions-drive-menu
 gnome-shell-extensions-launch-new-instance
 gnome-shell-extensions-native-window-placement
 gnome-shell-extensions-onboard
 gnome-shell-extensions-places-menu
 gnome-shell-extensions-screenshot-window-sizer
 gnome-shell-extensions-user-theme
 gnome-shell-extensions-window-list
 gnome-shell-extensions-windowsNavigator
 gnome-shell-extensions-workspace-indicator
 gnome-shell-theme-vertex
 gnome-shell-theme-zukitwo

Your explanation is unclear; can you please re-phrase it:
> warning that the integration extension is there, but the connector.
The screenshot might make things clear.
Also
> chrome-gnome-shell is installed so this should work (and worked before)
This package has not been updated. Can you please explain in what manner it worked previously, and in what circumstance it no longer works? After a Firefox update?

Source RPM: chrome-gnome-shell => chrome-gnome-shell-10.1-3.mga7.src.rpm
CC: (none) => lewyssmith

Comment 2 Aurelien Oudelet 2020-08-26 16:32:47 CEST
According to reporter it no longer runs well with current version of Firefox in Mageia 7. But he never has answered, until now. I'm prone to Close this OLD.

@Olivier, can you answer questions raised by Lewis in Comment-1, please?

Keywords: (none) => NEEDINFO

Comment 3 Olivier FAURAX 2020-08-28 08:20:48 CEST
Created attachment 11846 [details]
Screenshot of the website saying the connector (addon) is not working
Comment 4 Olivier FAURAX 2020-08-28 08:23:21 CEST
Created attachment 11847 [details]
Addon currently available
Comment 5 Olivier FAURAX 2020-08-28 09:24:58 CEST
Gnome includes a system for adding extensions from extensions.gnome.org, and there is an addon for Firefox that enables the capability to install these extensions in Gnome with one click from Firefox.

This is very convenient: you go to the extension website, you "enable" an extension, and it is available in your gnome desktop.

However, since perhaps my update to Mageia 7, the "connector" is not detected by the extension website.

Here are some possible explanations I imagine:
* new version of Firefox had an API change preventing the addon to function correctly (e.g. new security restriction on API)
* addon contains a binary that should be recompiled with new version of Firefox or Gnome
* addon contains a binary that depend on a specific library that has been updated/changed
* Firefox has new restriction, preventing a website to access the addon, or the other way around
* browser extension and "native host messaging application" (error message) are not installed correctly, or not in sync
Comment 6 Aurelien Oudelet 2020-08-28 09:52:53 CEST
Hi, thanks answering,

Assigning to Gnome maintainers as it seems a problem in a package.

Assignee: bugsquad => gnome
Keywords: NEEDINFO => (none)

Aurelien Oudelet 2021-04-16 13:20:43 CEST

Blocks: (none) => 28788

Comment 7 Aurelien Oudelet 2021-06-01 17:34:24 CEST
This now works OK under Mageia 8 Gnome.
Closing.

CC: (none) => ouaurelien
Resolution: (none) => FIXED
Status: NEW => RESOLVED

Comment 8 Olivier FAURAX 2021-06-02 09:56:33 CEST
This bug has been reported on Mageia 7

Note You need to log in before you can comment on or make changes to this bug.