@bytebro

The challenge will be finding out whence the Desktop Bus service definition for org.bluez.obex is installed on your operating system.

/usr/local/share/dbus-1/services or /usr/share/dbus-1/services is the starting point.

"Helpfully", the Desktop Bus service file does not have to be named anything appropriate, but just has to have Name=org.bluez.obex in the file itself.

Equally helpfully, Debian et al. have decided that *next* name that you get to look up is not dbus-org.bluez.obex.service , but Debian's own (long-standing) name for this.

https://sources.debian.org/src/bluez/5.82-1.1/debian/patches/org.bluez.obex.service.in.patch

#DesktopBus #BusActivation #Debian

@bytebro

It's trying and failing to "D-Bus activate" a Desktop Bus service named org.bluez.obex.

#DesktopBus bus activation is not a good thing. For starters, you now get to poke around in your dbus-1 tree to find out whether there's a Desktop Bus service file for that name.

Here's how it actually works when one is using my service manager:

http://jdebp.info/Softwares/nosh/guide/per-user-dbus-demand-start.html

systemd actually got to put hooks into Desktop Bus, but the same essentials happen. The bus broker finds a DBus service definition, and that then points to an actual service manager's separate service definition.

http://jdebp.info/Softwares/nosh/avoid-dbus-bus-activation.html

The challenge will be finding out whence the Desktop Bus service definition for org.bluez.obex is installed on your operating system. And installing it if it is missing.

Only some operating systems let one search for packages by what files they install.

#DesktopBus #BusActivation