Package: bluez-obexd Followup-For: Bug #1123793 Dear Maintainer,
I can confirm this bugreport. I spent a while today trying to receive a file from an Android phone on my Debian forky install with bluez-obexd 5.84-1 in use. The OBEX Object Push profile did not appear to be advertised by the Debian system. Inspecting the obexd.service logs uncovered the following logs: Jan 04 12:18:38 laptop dbus-daemon[1305]: [session uid=1000 pid=1305 pidfd=5] Activating via systemd: service name='org.gnome.evolution.dataserver.Sources5' unit='evolution-source-registry.service' requested by ':1.91' (uid=> Jan 04 12:18:38 laptop dbus-daemon[1305]: [session uid=1000 pid=1305 pidfd=5] Activation via systemd failed for unit 'evolution-source-registry.service': Unit evolution-source-registry.service not found. Jan 04 12:18:38 laptop obexd[5677]: Unable to acquire registry: Error calling StartServiceByName for org.gnome.evolution.dataserver.Sources5: Unit evolution-source-registry.service not found. Despite the large dependency-set it requires, I installed evolution-data-server because it provides the evolution-source-registry.service file, and then I began a new user session. With the dependency installed, the OBEX Object Push profile was advertised by the Debian system from the new user session, the system became visible for the Android device as a file push destination, and I was able to transfer files over bluetooth. Thanks, James
