Closed Bug 1754951 Opened 2 years ago Closed 2 years ago

Firefox beta/nightly snap fails to claim DBus name at startup

Categories

(Core :: Widget: Gtk, defect)

Product:
Core
Component:
Widget: Gtk
Version:
Firefox 98
Type:
defect

Tracking

()

Status:
RESOLVED FIXED

People

(Reporter: olivier, Unassigned)

References

(Blocks 1 open bug)

Details

User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:98.0) Gecko/20100101 Firefox/98.0

Steps to reproduce:

When installed from the stable channel, the firefox snap successfully claims the name org.mozilla.firefox.$PROFILEID on the session bus (where PROFILEID is a base64-encoded string based on the name of the profile directory), which allows communication between running instances.

When installed from the beta channel though, it tries to claim the name org.mozilla.firefox_beta.$PROFILEID (org.mozilla.firefox_nightly.$PROFILEID for the edge channel), and fails to do so because the apparmor profile for the snap denies it.

Blocks: snap

Two possible solutions come to mind:

  • Update snapd's dbus interface to be more permissive and allow claiming ###DBUS_NAME###-*.*

  • Change MOZ_APP_REMOTINGNAME to firefox for all snap builds at build time (not sure whether this would have undesired side effects?)

Changing the value of MOZ_APP_REMOTINGNAME would likely interfere with the ability to run several instances of the snap from different channels (see https://snapcraft.io/docs/parallel-installs).

The Bugbug bot thinks this bug should belong to the 'Core::Widget: Gtk' component, and is moving the bug to that component. Please revert this change in case you think the bot is wrong.

Component: Untriaged → Widget: Gtk
Product: Firefox → Core

Well, the fix was much more straightforward: https://git.launchpad.net/~mozilla-snaps/+git/firefox-snap/commit/?id=fbc97faa65da91c20b84b39ffd5a0beb02321a3e.

Builds have been triggered for the beta channel, and nightly will pick it up at the next scheduled build, in about 10 hours from now.

The fix is now live in the beta and edge channels. This bug can be marked fixed, but despite being the reporter it looks like I can't set its status to FIXED.

Thanks!

Status: UNCONFIRMED → RESOLVED
Closed: 2 years ago
Resolution: --- → FIXED

(It was weird that you don't have editbugs Olivier, so I requested the permission to be added in bug 1756086 :))

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