blueman-applet crashed with DBusException in call_blocking()

Bug #437883 reported by eclick
This bug affects 188 people
Affects Status Importance Assigned to Milestone
blueman (Ubuntu)
Fix Released
High
Micah Gersten
Oneiric
Invalid
High
Unassigned
Precise
Fix Released
High
Micah Gersten

Bug Description

Binary package hint: blueman

sw

ProblemType: Crash
Architecture: i386
Date: Mon Sep 28 01:21:57 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/bin/blueman-applet
InterpreterPath: /usr/bin/python2.6
Package: blueman 1.10-3ubuntu1
ProcCmdline: /usr/bin/python /usr/bin/blueman-applet
ProcEnviron:
 SHELL=/bin/bash
 LANG=cs_CZ.UTF-8
 LANGUAGE=cs_CZ.UTF-8
ProcVersionSignature: Ubuntu 2.6.31-11.36-generic
PythonArgs: ['/usr/bin/blueman-applet']
SourcePackage: blueman
Title: blueman-applet crashed with DBusException in call_blocking()
Uname: Linux 2.6.31-11-generic i686
UserGroups: adm admin audio cdrom dialout dip fax floppy fuse lpadmin plugdev scanner tape video

Related branches

Revision history for this message
eclick (eclick) wrote :
tags: removed: need-duplicate-check
tags: added: bugpattern-needed
Changed in blueman (Ubuntu):
status: New → Confirmed
Revision history for this message
Charlie Kravetz (cjkgeek) wrote :

Thanks for reporting this bug and any supporting documentation. Since this bug has enough information provided for a developer to begin work, I'm going to mark it as confirmed and let them handle it from here. Thanks for taking the time to make Ubuntu better!

visibility: private → public
Changed in blueman (Ubuntu):
importance: Undecided → High
status: Confirmed → Triaged
milestone: none → oneiric-updates
Revision history for this message
Charlie Kravetz (cjkgeek) wrote :

I experienced this crash after installing Xubuntu Oneiric Ocelot using the AMD64 Alternate image dated 2011-09-29. I did not have this same crash with the installations using the AMD64 Desktop image.

Unfortunately, once it crashed, it now crashes on every login.

Changed in blueman (Ubuntu):
status: Triaged → In Progress
Revision history for this message
Valmantas Palikša (walmis) wrote :

This bug should be fixed now since bzr revision 713

Changed in blueman (Ubuntu):
status: In Progress → Fix Committed
Revision history for this message
davis (davis-jazz) wrote :

So, after bug is fixed update should follow?

Revision history for this message
Eliah Kagan (degeneracypressure) wrote :

As shown by the recent duplicates, this crash has been happening a lot. Is more testing needed before the committed fix is released? Is there anything we can do to help testing, besides just enabling oneiric-proposed?

Revision history for this message
sarv jeet singh (sarv-jeet-hotmail) wrote :

i receive following error on selecting browse file. ubuntu11.10 is able to send file but cannot receive or browse phone. following error is received.
Error: DBus error org.freedesktop.DBus.Error.ServiceUnknown: The name :1.109 was not provided by any .service files
Please select another viewer and try again.

log file has following entries
ubuntu bluetoothd[3232]: Can't init device hci0: No such device (19)
Oct 24 18:18:29 ubuntu bluetoothd[3232]: HCI dev 0 unregistered
Oct 24 18:18:29 ubuntu bluetoothd[3232]: Stopping hci0 event socket
Oct 24 18:18:29 ubuntu bluetoothd[3232]: Unregister path: /org/bluez/3232/hci0
Oct 24 18:18:33 ubuntu kernel: [ 759.796110] usb 3-2: new full speed USB device number 4 using uhci_hcd
Oct 24 18:18:33 ubuntu bluetoothd[3232]: HCI dev 0 registered
Oct 24 18:18:33 ubuntu bluetoothd[3232]: Listening for HCI events on hci0
Oct 24 18:18:34 ubuntu bluetoothd[3232]: HCI dev 0 up
Oct 24 18:18:34 ubuntu bluetoothd[3232]: Adapter /org/bluez/3232/hci0 has been enabled
Oct 24 18:18:34 ubuntu pulseaudio[4352]: [pulseaudio] bluetooth-util.c: Error from RegisterEndpoint reply: org.freedesktop.DBus.Error.UnknownMethod

i am using ubuntu 11.10 32 bit with iso mounted on to a usb drive.

Revision history for this message
Antony John (antojk) wrote :

I am facing the same problem with my bluetooth headset which was working perfectly in 11.04.

This happens after pairing the device.. So I am forced to re-discover the device on every reboot.

Nov 23 18:17:12 vinis-laptop kernel: [ 213.831496] usb 1-1.1.3: new full speed USB device number 11 using ehci_hcd
Nov 23 18:17:12 vinis-laptop bluetoothd[2236]: HCI dev 0 registered
Nov 23 18:17:12 vinis-laptop bluetoothd[2236]: Listening for HCI events on hci0
Nov 23 18:17:12 vinis-laptop bluetoothd[2236]: HCI dev 0 up
Nov 23 18:17:12 vinis-laptop bluetoothd[2236]: Adapter /org/bluez/2236/hci0 has been enabled
Nov 23 18:17:12 vinis-laptop pulseaudio[2634]: [pulseaudio] bluetooth-util.c: Error from RegisterEndpoint reply: org.freedesktop.DBus.Error.UnknownMethod
Nov 23 18:17:53 pulseaudio[2634]: last message repeated 2 times

However I am able to successfully pair and use the device post discovery

Nov 23 18:24:59 vinis-laptop bluetoothd[2236]: Discovery session 0x7fea01e92230 with :1.70 activated
Nov 23 18:25:02 vinis-laptop bluetoothd[2236]: Stopping discovery
Nov 23 18:25:13 vinis-laptop bluetoothd[2236]: Badly formated or unrecognized command: AT+CSRSF=1,1,1,1,1,7
Nov 23 18:25:15 vinis-laptop kernel: [ 696.210559] input: 00:1B:B8:00:03:11 as /devices/virtual/input/input18
Nov 23 12:55:15 vinis-laptop rtkit-daemon[2204]: Successfully made thread 4236 of process 2634 (n/a) owned by '1000' RT at priority 5.
Nov 23 12:55:15 vinis-laptop rtkit-daemon[2204]: Supervising 5 threads of 1 processes of 1 users.

My kernel version: 3.0.0-13-generic
bluez package package version: 4.96-0ubuntu4
pulse audio package version: 1:1.0-0ubuntu3.1

Revision history for this message
Brian Murray (brian-murray) wrote :

This certainly doesn't seem fixed given the number of duplicates and the fact that some are still coming in from Oneiric systems.

Changed in blueman (Ubuntu):
status: Fix Committed → Triaged
Micah Gersten (micahg)
Changed in blueman (Ubuntu Oneiric):
importance: Undecided → High
status: New → Triaged
milestone: none → oneiric-updates
Changed in blueman (Ubuntu Precise):
milestone: oneiric-updates → none
Revision history for this message
LAZA (laza74) wrote :

happend today after the updating Precise the package Bluez

Revision history for this message
menner (menner) wrote :

It seems that blueman crashes when bluetooth USB-dongle isn't present. Precise.

Revision history for this message
LAZA (laza74) wrote :

.. and again while updating blueman.

Precise is living in Virtualbox and has NO bluetooth device!

tags: removed: bugpattern-needed
tags: added: bugpattern-written
Bryce Harrington (bryce)
tags: added: natty oneiric precise
Changed in blueman (Ubuntu Precise):
assignee: nobody → Canonical Desktop Team (canonical-desktop-team)
Revision history for this message
norberto (netcaster) wrote :

I'm running Xubuntu 32 bits.

Revision history for this message
Renaud Métrich (renaud-metrich) wrote :

Got this report after stopping the bluetooth Upstart service (I'm not using bluetooth) and disabling bluetooth in right upper corner in a Gnome session.

Revision history for this message
vassilis karamitros (ecatodarcus) wrote :

it happened 2 times when i was updating. only this report occured nothing more nothing less.

i am using ubuntu 12.04 beta.

Revision history for this message
Micah Gersten (micahg) wrote :

This is in universe, so not the Canonical Desktop team's responsibility. This is fixed upstream, we just need to update to the latest release.

Changed in blueman (Ubuntu Precise):
assignee: Canonical Desktop Team (canonical-desktop-team) → Micah Gersten (micahg)
Revision history for this message
Peter Belew (peterbe) wrote :

I had recently installed 12.04 xubuntu alpha-2 and upgraded to today (beta-1 +). I was investigating Bug #949482 and testing keyboard layouts, and then updated the system with apt-get, when this happened.

Ubuntu version and kernel version
DISTRIB_ID=Ubuntu
DISTRIB_RELEASE=12.04
DISTRIB_CODENAME=precise
DISTRIB_DESCRIPTION="Ubuntu precise (development branch)"
Linux compaq 3.2.0-18-generic #28-Ubuntu SMP Fri Mar 2 20:02:50 UTC 2012 x86_64 x86_64 x86_64 GNU/Linux
model name : AMD Athlon(tm) 64 Processor 3800+
cpu MHz : 1000.000

Revision history for this message
Mark Timbers (timbers-mark) wrote :

Bug popped up while running Update Manager.

I'm hopping the updates are not installed wrong...

Revision history for this message
Dmitry G. (hint) wrote :

Bug appeared after update.
Xubuntu Precise.

Revision history for this message
Guillaume Romagny (golfromeo.ovh) wrote :

Crashed appeared during an apt-get update of 12.04
working on Ubuntu 2D

Revision history for this message
Guillaume Romagny (golfromeo.ovh) wrote :

apparently the update reactivated the bluetooth (disconnected before the update), so the crash occured

Revision history for this message
norberto (netcaster) wrote :

same as Dmitry #19

Revision history for this message
stu green (stugreen-h) wrote :

notification appeared during a synaptic upgrade session of 12.4

Revision history for this message
Neil Martinsen-Burrell (nmb) wrote :

Same as Dmitry #19 for me too. Xubuntu 12.04 32 bit, doing an update

Revision history for this message
Paul Gorski (pauliegras) wrote :

Affects: Lubuntu precise-desktop-powerpc.iso 20120312, fresh install, applied updates via "Update Manager" bluetooth updates downloading, then crash.
Occured on eMac G4 800 MHz, 1 GB RAM, 80 GB HD

Revision history for this message
rogueclown (rogueclown) wrote :

this happened to me...Xubuntu 12.04, updated from 11.10 about a week ago (didn't happen until an update this morning, though), 64 bits, doing an upgrade through Synaptic.

Revision history for this message
Michał Krawczyk (mkkrawiec) wrote :

Got at Xubuntu 12.04 while I was trying update system.

Revision history for this message
timmillwood (ww3ib0sg9-tim) wrote :

I also had this issues on Xubuntu 12.04 when trying to apply updates.

(Brief tech spec: 64-bit, i5-2500k, 8GB ram, ATI 6870, OCZ Agility3)

Revision history for this message
Sebastian Mitterle (mathume) wrote :

ubuntu 12.04:

it's curious it crashed. i don't dispose of any connected bluetooth receiver.
i use to connect a bluetooth usb dongle, but it wasn't connected when the crashreport came up, not even connected since i upgraded to 12.04.

Revision history for this message
Luigi Calderone (lugligino) wrote :

I don't use bluetooth at all. I would know how deactivate it.

Revision history for this message
Ken Speakman (ken-speakman) wrote :

I've just installed 12.04 Beta1 32bit in virtualbox (64 bit 10.04 system).
I got the error message during apt-get upgrade. I used synaptic to download the updates (342 of them).
I then did the upgrade from the keyboard. This appears to have worked as I have just been advised to restart firefox.

Revision history for this message
menner (menner) wrote :

 Xubuntu 12.04, bluetooth USB dongle currently not plugged in, no bluetooth activity.

Revision history for this message
Roy H Huddleston (archspader) wrote :

I have a bluetooth adapter attached to my USB port. I am updating my 12.04 Beta1 Precise Lubuntu but in the Update Manager it has the date right but is calling it still Alpha.

Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package blueman - 1.23-0ubuntu1

---------------
blueman (1.23-0ubuntu1) precise; urgency=low

  * New upstream release (FFe: LP: #961873)
    - fixes LP: #437883, #709171

  [ Julien Lavergne <email address hidden> ]
  * debian/patches:
    - 01_dont_autostart_lxde.patch: Don't autostart applet on LXDE (LP: #958890)
  * debian/rules:
    - Don't use simple-patchsys.mk as the package is 3.0 (quilt)
 -- Micah Gersten <email address hidden> Sun, 18 Mar 2012 05:34:05 -0500

Changed in blueman (Ubuntu Precise):
status: Triaged → Fix Released
Revision history for this message
BALTHAZAR Jean-Robert (balthazarprestations) wrote :

This bug always occurs during Updates when asking for Distributioin Update

Revision history for this message
Prx (info-productivix) wrote :

still the problem on 12.04 with xubuntu, even after updates

Revision history for this message
hamish (hamish-b) wrote :

I'm still seeing it on xubuntu 12.04 too, with all updates.

Actually I've seen it on every xubuntu 12.04 install I've done, which is dozens of machines, both desktop and laptops, and in dozens of xubuntu installs to VMs.

Usually I just uninstall the package and be done with it, but the laptop I'm seeing the crash on today has bluetooth and I'd like to use it.

It has blueman package version 1.23-0ubuntu2.1.

The error title is the same DBusException in call_blocking(): but with "org.openobex.Error.InvalidArguements: Invalid path"

it also says it's a duplicate of bug #433741, but that bug report can't be found. (huh?)
someone else noticed that here:

https://answers.launchpad.net/launchpad/+question/149550

see also #919649

thanks,
Hamish

Revision history for this message
ATIpro (somebody2112) wrote :

I've solved this issue by installing python-gconf.

Revision history for this message
penalvch (penalvch) wrote :

Declined for Oneiric as EOL.

Changed in blueman (Ubuntu Oneiric):
status: Triaged → Invalid
Revision history for this message
hamish (hamish-b) wrote :

The python-gocnf is installed in precise, but still happening here at login time.

:-(
Hamish

Revision history for this message
penalvch (penalvch) wrote :

hamish, thank you for your comment. Unfortunately, as this bug report is closed, it is not scoped to you, your problem, or your hardware. So your hardware and problem may be tracked, could you please file a new report with Ubuntu by executing the following in a terminal while booted into the default Ubuntu kernel (not a mainline one) via:
ubuntu-bug linux

For more on this, please read the official Ubuntu documentation:
Ubuntu Bug Control and Ubuntu Bug Squad: https://wiki.ubuntu.com/Bugs/BestPractices#X.2BAC8-Reporting.Focus_on_One_Issue
Ubuntu Kernel Team: https://wiki.ubuntu.com/KernelTeam/KernelTeamBugPolicies#Filing_Kernel_Bug_reports
Ubuntu Community: https://help.ubuntu.com/community/ReportingBugs#Bug_reporting_etiquette

When opening up the new report, please feel free to subscribe me to it.

Thank you for your understanding.

Helpful bug reporting tips:
https://wiki.ubuntu.com/ReportingBugs

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

Duplicates of this bug

Other bug subscribers

Remote bug watches

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