Alberto, sure that could work in principle. Good point. - We'd have to not only copy the .service file, but modify its Exec= line to point inside the correct snap and update the file when a new snap version gets installed (or delete it if the new snap doesn't use the file anymore, etc).
- What is the use case that you hit this with? In my use case, both the session dbus daemon and the session dbus .service are all inside a monolithic snap. But it sounds like you want multiple snaps to install session .service files that can be run from another "session" snap? Just curious what you're envisioning. -- 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 Status in snapd 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
