Firefox 122 on Ubuntu (snap): webextensions native messaging broken
Categories
(Firefox Build System :: Third Party Packaging, defect)
Tracking
(firefox-esr115 unaffected, firefox122 verified, firefox123 fixed, firefox124 fixed)
Tracking | Status | |
---|---|---|
firefox-esr115 | --- | unaffected |
firefox122 | --- | verified |
firefox123 | --- | fixed |
firefox124 | --- | fixed |
People
(Reporter: me+bz, Unassigned)
References
(Blocks 1 open bug, )
Details
(Keywords: flatpak, regression, snap)
Attachments
(2 files)
Steps to reproduce:
- Update to Firefox 122 on Ubuntu
- Install Video DownloadHelper and its Companion App.
- In the settings of the addon, see that the Companion App is not recognized
The command:
$ flatpak permission-show snap.firefox
``
Shows that Firefox is allowed to read the manifest.
But it doesn't. The logs say:
Jan 25 12:47:56 ubuntu-linux-22-04-02-desktop firefox[154219]: OnGetManifestDone error: GDBus.Error:org.freedesktop.DBus.Error.UnknownMethod: No such method “GetManifest”
Jan 25 12:47:57 ubuntu-linux-22-04-02-desktop firefox_firefox.desktop[154219]: [Parent 154219, Main Thread] WARNING: OnGetManifestDone error: GDBus.Error:org.freedesktop.DBus.Error.UnknownMethod: No such method “GetManifest”: 'glib warning', file /build/firefox/parts/firefox/build/toolkit/xre/nsSigHandlers.cpp:187
Reporter | ||
Comment 1•2 years ago
|
||
launchpad bug: https://bugs.launchpad.net/ubuntu/+source/ubuntu-release-upgrader/+bug/2051188
@Sylvestre Can you see if you find anyone who could assist?
Reporter | ||
Comment 2•2 years ago
|
||
I'm working on the Video DownloadHelper extension (100_000+ Linux users, mostly Ubuntu), and the Snap sandbox has always been a problem, but that specific update made it worse. We're getting those bug reports since the yesterday.
Reporter | ||
Updated•2 years ago
|
Comment 3•2 years ago
|
||
:me+bz, if you think that's a regression, could you try to find a regression range using for example mozregression?
Comment 4•2 years ago
|
||
The Bugbug bot thinks this bug should belong to the 'Core::Widget: Gtk' component, and is moving the bug to that component. Please correct in case you think the bot is wrong.
Reporter | ||
Comment 5•2 years ago
|
||
(In reply to BugBot [:suhaib / :marco/ :calixte] from comment #3)
:me+bz, if you think that's a regression, could you try to find a regression range using for example mozregression?
That's a little tricky because it's a snap-sandbox specific issue, and mozregression doesn't work with Snap: https://bugzilla.mozilla.org/show_bug.cgi?id=1763188
Reporter | ||
Comment 6•2 years ago
|
||
Reporter | ||
Comment 7•2 years ago
|
||
I've attached the exception from the js console.
Reporter | ||
Comment 8•2 years ago
|
||
More investigation: the code that's throwing comes from a patch by Canonical: https://github.com/canonical/firefox-snap/blob/stable/patches/native-messaging-portal.patch
Reporter | ||
Comment 9•2 years ago
|
||
This is the code that's breaking the extension: https://github.com/canonical/firefox-snap/blob/7f87c2af624891313906abe7fdccfda1ad76a0f7/patches/native-messaging-portal.patch#L748
Commit: https://github.com/canonical/firefox-snap/commit/f1bf0d6dd649e13a1a9a159de63ae74068966c0c
If you guys have a quick access to Canonical, help would be appreciated.
Comment 10•2 years ago
|
||
Thanks for the bug report. The messaging portal patch is indeed part of the snap and not upstream at this point. The patch was refreshed to apply cleaning to 122 and rebased at the same time on the current phabricator version which made it use a new dbus method. We didn't notice that this method hadn't been backported to the Ubuntu 22.04 portal package. We are working now on reverting the patch to not depends on the new method.
Updated•2 years ago
|
Comment 12•2 years ago
|
||
Salut Paul, I hope you are doing great!
Thanks for the ping. We have been discussing with Canonical about it today (here and by email)
Updated•2 years ago
|
Comment 13•2 years ago
|
||
Hello!
I have managed to reproduce the issue with firefox 122.0-2 on Ubuntu 22.04. I can confirm that the issue is fixed with firefox 122.0-2.1.
I would like to mention that there is still an error in the console when intalling the addon mentioned in the description, see attached screen shot
Updating the flags and the status of this bug.
Comment 14•2 years ago
|
||
Comment 15•2 years ago
|
||
Marking this bug as resolved
Comment 16•2 years ago
•
|
||
I've posted a quick post-mortem write up on the Ubuntu Discourse for folks who may be interested in reading what exactly happened:
Firefox 122 snap temporary native messaging breakage for Ubuntu 22.04 users (fixed since)
Updated•2 years ago
|
Description
•