I'm having this same bug whenever I reboot. The hardware is a PowerEdge T110 Tower Server with wired Ethernet. It has no WiFi nor Bluetooth. I'm running MATE version.
Turning off the Bluetooth Manager from loading in the Startup Applications Preferences, stops the error, as is to be expected. Since it is the Bluetooth manager and many of configurations with this problem are older hardware that predate Bluetooth or in my case a server, I thought it might simply be a problem that there were no Bluetooth devices. Whenever I plug in a USB Bluetooth dongle, and the error no longer happens. >From the outside without looking at the code, it appears that this might be as simple as the BlueMan app needs to exit gracefully without raising an error condition when there are no Bluetooth devices. When there are no devices, the Bluetooth drivers are not loaded, so the Bluetooth Manager fails to find them. It may appear as a WiFi error, since the Bluetooth BNEP drivers for Ethernet Emulation over are not available. Hope this might help. If at all possible, this really should be fixed before the release next month, otherwise novice users will worry that it is something serious. Thank you for your hard work supporting Ubuntu, Greg -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1553609 Title: blueman-applet crashed with dbus.exceptions.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/ubuntu/+source/blueman/+bug/1553609/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
