Blueman-applet crash on login: DBusException in call_blocking(): org.freedesktop.DBus.Error.TimedOut: Failed to activate service 'org.bluez': timed out

Bug #1533206 reported by David Pearson on 2016-01-12
This bug affects 70 people
Affects Status Importance Assigned to Milestone
blueman (Ubuntu)
Nominated for Xenial by Alberto Salvia Novella

Bug Description

Blueman-apport crash warning on login to fresh xenial daily iso

ProblemType: Bug
DistroRelease: Ubuntu 16.04
Package: blueman 2.0.3-1ubuntu1
ProcVersionSignature: Ubuntu 4.3.0-5.16-generic 4.3.3
Uname: Linux 4.3.0-5-generic i686
ApportVersion: 2.19.3-0ubuntu2
Architecture: i386
CurrentDesktop: XFCE
Date: Tue Jan 12 13:28:52 2016
InstallationDate: Installed on 2016-01-12 (0 days ago)
InstallationMedia: Xubuntu 16.04 LTS "Xenial Xerus" - Alpha i386 (20160112)
SourcePackage: blueman
UpgradeStatus: No upgrade log present (probably fresh install)

David Pearson (akxwi-dave) wrote :
Ubuntu QA Website (ubuntuqa) wrote :

This bug has been reported on the Ubuntu ISO testing tracker.

A list of all reports related to this bug can be found here:

tags: added: iso-testing
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in blueman (Ubuntu):
status: New → Confirmed
Changed in blueman (Ubuntu):
importance: Undecided → High
Martin Wimpress (flexiondotorg) wrote :

The following duplicate includes a traceback:


Set Hallstrom (sakrecoer) wrote :

In fact, the machine it crashed on has no Bluetooth device.


1. Report to <>.
2. Paste the new report link here.
3. Set this bug status back to "confirmed".

Thank you.

Changed in blueman (Ubuntu):
status: Confirmed → Incomplete
Forest (foresto) on 2016-02-01
summary: - Blueman-apport crash on login
+ Blueman-applet crash on login: DBusException in call_blocking():
+ org.freedesktop.DBus.Error.TimedOut: Failed to activate service
+ 'org.bluez': timed out
Forest (foresto) wrote :

The current version of blueman-applet does not exhibit this bug, so there would seem to be no point in filing a report upstream. Looks like it's up to the ubuntu team to either patch it or update to a new version in 15.10 (wily).

Changed in blueman (Ubuntu):
status: Incomplete → Confirmed
Forest (foresto) wrote :

(Specifically, the version of blueman-applet as packaged in blueman 2.0.3-1ubuntu1 does not trigger the crash report on my xubuntu wily system, while the one in 2.0-1ubuntu1 does.)

Tobias (ulbricht-tobias) wrote :

It does affect people running 2.0.3-1ubuntu1, see duplicate #1538409

b3nmore (b3nmore) wrote :

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.

Nairwolf (nairwolf) wrote :

Thus bug affects also on an amd64 architecture.

Ross Gammon (rosco2) wrote :

I observed this bug (actually 1538409) after upgrading from Ubuntu Studio Wily (14.10) to Xenial using update manager.

I have reported this issue upstream.


Ivor (rhozeta) wrote :

Experienced this on Raspberry Pi 3 running Ubuntu Mate ubuntu-mate-15.10.3-desktop-armhf-raspberry-pi-2 image.

Kev Bowring (flocculant) wrote :

I'm only seeing this with 32bit images now.

seems still to happen on amd64

Launchpad Janitor (janitor) wrote :

This bug was fixed in the package blueman - 2.0.4-1ubuntu2

blueman (2.0.4-1ubuntu2) xenial; urgency=medium

  * debian/patches/02_lp1533206.patch
    - Fix startup crash for systems without bluetooth (LP: #1533206)

 -- Sean Davis <email address hidden> Wed, 30 Mar 2016 20:03:33 -0400

Changed in blueman (Ubuntu):
status: Confirmed → Fix Released

I have blueman-2.0.4-1ubuntu1 amd64 installed on my system, but still after reboot and login this problem occurs.

oh sorry, I have blueman-2.0.4-1ubuntu1, not blueman-2.0.4-1ubuntu2 as you mentioned..

Michael Lueck (mlueck) wrote :

Issue confirmed resolved in Xubuntu daily 20160408 amd64 ISO. Thank you so much! :-)

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers