FS#32427 - [bluez] org.bluez.service should be named dbus-org.bluez.service
Attached to Project:
Arch Linux
Opened by Greg (dolby) - Saturday, 03 November 2012, 18:06 GMT
Last edited by Ionut Biru (wonder) - Sunday, 04 November 2012, 00:16 GMT
Opened by Greg (dolby) - Saturday, 03 November 2012, 18:06 GMT
Last edited by Ionut Biru (wonder) - Sunday, 04 November 2012, 00:16 GMT
|
Details
/usr/share/dbus-1/system-services/org.bluez.service should
be named
/usr/share/dbus-1/system-services/dbus-org.bluez.service As can be seen in /usr/lib/systemd/system/bluetooth.service: Alias=dbus-org.bluez.service or the /usr/share/dbus-1/system-services/org.bluez.service" file itself: SystemdService=dbus-org.bluez.service Otherwise pulseaudio and probably other things cant start bluez: pulseaudio[253]: [pulseaudio] bluetooth-util.c: org.bluez.Manager.ListAdapters() failed: org.freedesktop.systemd1.LoadFailed: Unit dbus-org.bluez.service failed to load: No such file or directory. See system logs and 'systemctl status dbus-org.bluez.service' for details. pulseaudio[253]: [pulseaudio] module-gconf.c: Unable to read or parse data from client. pulseaudio[253]: [pulseaudio] module.c: Failed to load module "module-gconf" (argument: ""): initialization failed. pulseaudio[253]: [pulseaudio] main.c: Module load failed. |
This task depends upon
dbus-daemon[206]: dbus[206]: [system] Activation via systemd failed for unit 'dbus-org.bluez.service': Unit dbus-org.bluez.service failed to load: No such file or directory. See system logs and 'systemctl status dbus-org.bluez.service' for details.
dbus[206]: [system] Activating via systemd: service name='org.bluez' unit='dbus-org.bluez.service'
dbus[206]: [system] Activation via systemd failed for unit 'dbus-org.bluez.service': Unit dbus-org.bluez.service failed to load: No such file or directory. See system logs and 'systemctl status dbus-org.bluez.service' for details.
dbus interfaces are not regular systemd daemons.
Not the interface. Sorry if that wasnt clear.
dbus-daemon[206]: dbus[206]: [system] Activating via systemd: service name='org.freedesktop.Avahi' unit='dbus-org.freedesktop.Avahi.service'
dbus[206]: [system] Activating via systemd: service name='org.freedesktop.Avahi' unit='dbus-org.freedesktop.Avahi.service'
dbus-daemon[206]: dbus[206]: [system] Activation via systemd failed for unit 'dbus-org.freedesktop.Avahi.service': Unit dbus-org.freedesktop.Avahi.service failed to load: No such file or directory. See system logs and 'systemctl status dbus-org.freedesktop.Avahi.service' for details.
dbus[206]: [system] Activation via systemd failed for unit 'dbus-org.freedesktop.Avahi.service': Unit dbus-org.freedesktop.Avahi.service failed to load: No such file or directory. See system logs and 'systemctl status dbus-org.freedesktop.Avahi.service' for details.
The situation is slightly confusing as both dbus and systemd use the .service postfix. However, the naming of both are correct.
The error message should be improved (though I don't know what wording would be better).
Try "systemctl enable bluetooth.service", that should make it work, as it creates the missing Alias (symlink) dbus-org.bluez.service in /etc/systemd/system. Assuming that works, this is not a bug.