FS#45816 - [bluez] Unable to send files, dbus can't find dbus-org.bluez.obex.service
Attached to Project:
Arch Linux
Opened by AnAkkk (AnAkkk) - Tuesday, 28 July 2015, 18:18 GMT
Last edited by Andreas Radke (AndyRTR) - Thursday, 24 September 2015, 15:43 GMT
Opened by AnAkkk (AnAkkk) - Tuesday, 28 July 2015, 18:18 GMT
Last edited by Andreas Radke (AndyRTR) - Thursday, 24 September 2015, 15:43 GMT
|
Details
Description:
While trying to send a file through KDE's Bluedevil applet on Plasma 5, it never worked for me. I can find the following errors in journalctl on every try: dbus-daemon[1304]: Activating via systemd: service name='org.bluez.obex' unit='dbus-org.bluez.obex.service' dbus-daemon[1304]: Activation via systemd failed for unit 'dbus-org.bluez.obex.service': Unit dbus-org.bluez.obex.service failed to load: No such file or directory. kded5[1310]: BluezQt unknown: PendingCall Error: "Unit dbus-org.bluez.obex.service failed to load: No such file or directory. Additional info: bluez 5.32 |
This task depends upon
systemctl --user start obex
Is it normal this is required? It doesn't seem to be mentioned in the wiki.
I think this is a packaging problem.
obex.service should probably be in /etc/systemd/user/ instead of /usr/lib/systemd/user/, this way the bluetooth file transfers would work for all users (as soon as something request it) without the need to manually enable the service on every user.
systemctl --global enable obex
in the post install script.
linking /usr/lib/systemd/user/dbus-org.bluez.obex.service to obex.service.
FS#37773- is 0001-Allow-using-obexd-without-systemd-in-the-user-session.patch now fully obsolete with new DBus?I couldn't find Fedore or Gentoo changing anything so far and also upstream seems not aware of it.
Note that other distributions (Debian especially) tend to run systemctl enable on package install.
BTW, when using kdbus, I always get an error related to the bluez dbus service, I'm not sure if it's related or not. If not, I can create a new bug report if needed:
systemd[1]: org.bluez.busname: Bus service dbus-org.bluez.service not loaded, refusing.
systemd[1]: Failed to listen on DBUS1: org.bluez.
It does succeed for org.bluez.obex though:
systemd[773]: Listening on DBUS1: org.bluez.obex.
systemd[1385]: Listening on DBUS1: org.bluez.obex.
I'm not sure what's the difference between the two.
● org.bluez.busname - DBUS1: org.bluez
Loaded: loaded (/usr/share/dbus-1/system-services/org.bluez.service)
Active: inactive (dead)
Docs: man:systemd-dbus1-generator(8)
sept. 23 22:23:43 pc systemd[1]: org.bluez.busname: Bus service dbus-org.bluez.service not loaded, refusing.
sept. 23 22:23:43 pc systemd[1]: Failed to listen on DBUS1: org.bluez.
Should I report this to systemd?
Any further change required or is it now fixed?
The original issue is fixed.