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 780393 - runtime.sendMessage error on extensions.gnome.org with Firefox Developer Edition
runtime.sendMessage error on extensions.gnome.org with Firefox Developer Edition
Status: RESOLVED FIXED
Product: chrome-gnome-shell
Classification: Other
Component: Browser extension
8.2
Other Linux
: Normal blocker
: ---
Assigned To: Yuri Konotopov
chrome-gnome-shell panel maintainer(s)
https://git.gnome.org/browse/chrome-g...
Depends on:
Blocks:
 
 
Reported: 2017-03-22 12:30 UTC by Sander Lienaerts
Modified: 2017-04-06 08:26 UTC
See Also:
GNOME target: ---
GNOME version: 3.21/3.22


Attachments
Strack trace (7.12 KB, text/plain)
2017-03-22 12:30 UTC, Sander Lienaerts
Details

Description Sander Lienaerts 2017-03-22 12:30:52 UTC
Created attachment 348474 [details]
Strack trace

All pages ('Extensions', 'Add yours', 'Installed extensions', 'About') on extensions.gnome.org produce the following 2 errors in compat-content-script.js:38:8 and require.84b7823d3c10.js:175:17 respectively:

1. firefox-external-messaging: runtime.sendMessage error 
Error: Could not establish connection. Receiving end does not exist.

2. Error: Load timeout for modules: dbus!__unnormalized2,dbus!__unnormalized3,dbus!_
http://requirejs.org/docs/errors.html#timeout () 

makeError https://extensions.gnome.org/static/js/require.84b7823d3c10.js:175:17
checkLoaded https://extensions.gnome.org/static/js/require.84b7823d3c10.js:746:23
checkLoaded/checkLoadedTimeoutId< https://extensions.gnome.org/static/js/require.84b7823d3c10.js:789:25

Firefox Developer Edition version: 54.0a2

Visually no extensions are shown when browsing 'Extensions' or 'Installed extensions'.

Added stack trace below in the attachments for the 1st error.
Comment 2 Yuri Konotopov 2017-03-23 20:59:04 UTC
This is fixed in git master and will be released in 2 weeks
Comment 3 Yuri Konotopov 2017-04-06 03:01:18 UTC
Extension was approved now. You can update
Comment 4 Sander Lienaerts 2017-04-06 08:26:22 UTC
Thanks for the updates. It works like a charm now :)