Ubuntu
blueman package

  1. Bug #1754836
  2. Comment #5

Comment 5 for bug 1754836

Revision history for this message
Alistair Buxton (a-j-buxton) wrote : Re: Xubuntu: [pulseaudio] bluez5-util.c: GetManagedObjects() failed: org.freedesktop.DBus.Error.TimedOut: Failed to activate service 'org.bluez': timed out (service_start_timeout=25000ms)

No, we are talking about the errors in xsession-errors.txt:

ERROR:dbus.proxies:Introspect error on org.bluez:/: dbus.exceptions.DBusException: org.freedesktop.DBus.Error.TimedOut: Failed to activate service 'org.bluez': timed out (service_start_timeout=25000ms)
ERROR:dbus.proxies:Introspect error on org.bluez:/org/bluez: dbus.exceptions.DBusException: org.freedesktop.DBus.Error.TimedOut: Failed to activate service 'org.bluez': timed out (service_start_timeout=25000ms)
ERROR:dbus.proxies:Introspect error on org.bluez:/: dbus.exceptions.DBusException: org.freedesktop.DBus.Error.TimedOut: Failed to activate service 'org.bluez': timed out (service_start_timeout=25000ms)

Note that each one of these errors is a separate time out, so the total delay is 75 seconds. This delay blocks the desktop from starting during boot and first login.

The delay can be reproduced any time on the live session by attempting to start blueman-applet from the terminal - it will produce the same errors and then give up after 75 seconds.

The computer under test has no bluetooth hardware and blueman is not running. A patch was added to 16.04 because this situation led to blueman outright crashing there. Now in 18.04 instead of crashing it delays boot up by 75 seconds instead.