1898283 - Use full profile path to compute DBus name

Status: NEW

(Core :: Widget: Gtk, defect)

Description

[:gerard-majax]

If one has multiple installations using the same profile name (but at difference places) e.g., like a packaged firefox (or snap) + tarball, this will clash on DBus names (broke me in bug 1897907)

Comment 1

[Martin Stránský [:stransky] (ni? me)]

Does Snap sandbox allow to get profile directory? I mean without sandbox we may be able to get profile name like /home/user/.mozilla/profile but but which profile patch we can get for sandboxed apps?

Comment 2

[:gerard-majax]

(In reply to Martin Stránský [:stransky] (ni? me) from comment #1)

Does Snap sandbox allow to get profile directory? I mean without sandbox we may be able to get profile name like /home/user/.mozilla/profile but but which profile patch we can get for sandboxed apps?

my current WIP just adds the profile path to compute the dbus name, I'm not changing anything else

Comment 3

[Martin Stránský [:stransky] (ni? me)]

Attachment: Bug 1898283 [Linux] Use profile directory to identify remote application instance r?emilio

Comment 4

[:gerard-majax]

ok you were too fast, i was also changing some code around nsDbusRemote* so we dont duplicate client/server side of the identifier computation

Comment 5

[:gerard-majax]

Attachment: Capture d’écran du 2024-05-23 10-48-11.png

my nightly running from tarball with default profile used, and a Snap install started with a default profile as well