In my case this happens, when the bluetooth hardware wasn't initialized
by kernel, e.g. it was toggled off by hardware switch (maybe software
off might work as well). In such case /sys/class/bluetooth is not
created, which prevents the bluetooth.service to start:
systemctl status bluetooth
● bluetooth.service - Bluetooth service
Loaded: loaded (/lib/systemd/system/bluetooth.service; enabled; vendor
preset: enabled)
Active: inactive (dead)
Condition: start condition failed at So 2016-02-14 12:37:00 CET; 4s ago
ConditionPathIsDirectory=/sys/class/bluetooth was not met
This means that bluetoothd is not running and thus does not provide the
org.bluez dbus service, which in turn is what blueman is complaining
about.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1533206
Title:
Blueman-applet crash on login: DBusException in call_blocking():
org.freedesktop.DBus.Error.TimedOut: Failed to activate service
'org.bluez': timed out
To manage notifications about this bug go to:
https://bugs.launchpad.net/blueman/+bug/1533206/+subscriptions
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
