Ok, so how do I re enable bluetooth?
[bpm]$ sudo systemctl status bluetooth.target bluetooth.target - Bluetooth Loaded: loaded (/lib/systemd/system/bluetooth.target) Active: active since Thu, 07 Apr 2011 09:07:56 -0500; 2s ago
/var/log/messages shows: Apr 7 09:16:23 dufus dbus-daemon: [system] Activating via systemd service name='org.bluez' unit='dbus-org.bluez.service' Apr 7 09:16:23 dufus dbus-daemon: [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' for details. Apr 7 09:16:23 dufus dbus-daemon: [system] Activating via systemd service name='org.bluez' unit='dbus-org.bluez.service' Apr 7 09:16:23 dufus dbus-daemon: [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' for details.
So, is it a systemd, bluetooth, or dbus bug?
On 04/07/2011 07:48 PM, Brian Millett wrote:
Ok, so how do I re enable bluetooth?
[bpm]$ sudo systemctl status bluetooth.target bluetooth.target - Bluetooth Loaded: loaded (/lib/systemd/system/bluetooth.target) Active: active since Thu, 07 Apr 2011 09:07:56 -0500; 2s ago
/var/log/messages shows: Apr 7 09:16:23 dufus dbus-daemon: [system] Activating via systemd service name='org.bluez' unit='dbus-org.bluez.service' Apr 7 09:16:23 dufus dbus-daemon: [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' for details. Apr 7 09:16:23 dufus dbus-daemon: [system] Activating via systemd service name='org.bluez' unit='dbus-org.bluez.service' Apr 7 09:16:23 dufus dbus-daemon: [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' for details.
So, is it a systemd, bluetooth, or dbus bug?
File it against systemd and we can take it from there
Rahul
On 04/07/2011 03:11 PM, Rahul Sundaram wrote:
File it against systemd and we can take it from there
It's better that reporters file failing services against the relevant component and the maintainer move it to systemd if it applies to systemd then to have them file it against systemd.
It could just as be that bluetooth has not cought up to recent changes in D-Bus response codes for a service it's communicating with.
JBG