"Could snapd be so smart to copy the .service file into /usr/share/dbus/services/ when the interface gets connected, and unlink it when it gets disconnected?"
Yes it could and that sounds like a reasonable approach if it is properly designed, but I think that is a different problem than what PR #1613 is trying to solve. I mention "properly designed" because "when the interface gets connected" would have to be expressed as a plug so that it could be connected/disconnected and as such, likely a different interface, such as 'dbus-activation-support' or something. -- You received this bug notification because you are a member of Ubuntu Touch seeded packages, which is subscribed to dbus in Ubuntu. https://bugs.launchpad.net/bugs/1633520 Title: Support dbus runtime relocation Status in D-Bus: Unknown Status in dbus package in Ubuntu: New Bug description: For example, when running in a snap. I ran into this while testing a unity8 desktop session snap. Session services were being dbus-activated, but dbus was running the hardcoded paths in the session desktop files. Which weren't pointed into the snap. DBus has support for relocating those paths, but it only does so on Windows. I've added a patch to support $DBUS_ROOT on Unix and relocate paths as needed. I've linked the upstream bug here. We may want to consider patching Ubuntu while we wait for it to land upstream. I've attached the patch here too. To manage notifications about this bug go to: https://bugs.launchpad.net/dbus/+bug/1633520/+subscriptions -- Mailing list: https://launchpad.net/~touch-packages Post to : touch-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~touch-packages More help : https://help.launchpad.net/ListHelp
