blueman-applet crashed with dbus.exceptions.DBusException in call_blocking(): org.freedesktop.DBus.Error.TimedOut: Failed to activate service 'org.bluez': timed out

Bug #1538409 reported by Lyn Perrine
92
This bug affects 18 people
Affects Status Importance Assigned to Milestone
blueman (Ubuntu)
Confirmed
Medium
Unassigned

Bug Description

blueman crashed and I did not realize it but it I had the additional drivers part of the new ubuntu mate welcome part of 16.04

This is a bit supring as I do not have any bluetooth adapaters on this desktop so this is a bit supring. Maybe something is trying to acess a non existant device.

ProblemType: Crash
DistroRelease: Ubuntu 16.04
Package: blueman 2.0.3-1ubuntu1
ProcVersionSignature: Ubuntu 4.3.0-7.18-generic 4.3.3
Uname: Linux 4.3.0-7-generic x86_64
ApportVersion: 2.19.4-0ubuntu1
Architecture: amd64
CurrentDesktop: MATE
Date: Tue Jan 26 21:59:23 2016
ExecutablePath: /usr/bin/blueman-applet
InstallationDate: Installed on 2016-01-27 (0 days ago)
InstallationMedia: Ubuntu-MATE 16.04 LTS "Xenial Xerus" - Alpha amd64 (20160127)
InterpreterPath: /usr/bin/python3.5
ProcCmdline: /usr/bin/python3 /usr/bin/blueman-applet
ProcEnviron:
 LANGUAGE=en_US
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_US.UTF-8
 SHELL=/bin/bash
PythonArgs: ['/usr/bin/blueman-applet']
SourcePackage: blueman
Title: blueman-applet crashed with dbus.exceptions.DBusException in call_blocking(): org.freedesktop.DBus.Error.TimedOut: Failed to activate service 'org.bluez': timed out
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

Revision history for this message
Lyn Perrine (walterorlin) wrote :
tags: removed: need-duplicate-check
Changed in blueman (Ubuntu):
importance: Undecided → Medium
information type: Private → Public
Revision history for this message
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:
http://iso.qa.ubuntu.com/qatracker/reports/bugs/1538409

tags: added: iso-testing
Revision history for this message
Launchpad Janitor (janitor) wrote :

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

Changed in blueman (Ubuntu):
status: New → Confirmed
Revision history for this message
gembo (gembogm) wrote :

       did not notice anything only got mezzage after leaving full screen video had 16.04 installed for less than 30 minutes [painless] was just checking sound and video on facebook all working tip top ok resolution and vga better than 15.10 did not know i had blueman app

Revision history for this message
HolyHoundz (me5066448452) wrote :

my labtop doesnt have bluetooth hardware so why it installing in first place

Revision history for this message
Forest (foresto) wrote : Re: [Bug 1538409] Re: blueman-applet crashed with dbus.exceptions.DBusException in call_blocking(): org.freedesktop.DBus.Error.TimedOut: Failed to activate service 'org.bluez': timed out

>my labtop doesnt have bluetooth hardware so why it installing in first place

My computer doesn't have built-in bluetooth hardware either, but I'm glad
the software is installed, because I want my bluetooth dongle to work when I
plug it in.

Revision history for this message
oldrocker99 (fhwri99) wrote :

I got it upon booting the live USB.

Revision history for this message
AdamH (adam-sundew) wrote :

I got this error message from my Ubuntu MATE 16.04 (64-bit) fresh install inside a VirtualBox VM (VirtualBox version: 5.0.14, i.e. latest at time of writing), with no Bluetooth hardware connected to the VM.

Revision history for this message
H I Murphy (him610) wrote :

Received crash report after booting up on Xubuntu 16.04 Beta-1 from an external DVD. I have no Bluetooth devices on this machine. The MD5SUM of the downloaded ISO file checked good.

Revision history for this message
David Bonnie (thewacokid) wrote :

Same problem here. No Bluetooth, but a crash/error report popped up as soon as I booted from a USB thumb drive.

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

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.