blueman-applet crashed with DBusException in call_blocking(): org.freedesktop.DBus.Error.ServiceUnknown: The name :1.105 was not provided by any .service files

Bug #762965 reported by geonel
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
blueman (Ubuntu)
New
Undecided
Unassigned

Bug Description

Binary package hint: blueman

very flaky. does not see bluetooth dinovo adapter after reboot. error when reinstalling bluez

ProblemType: Crash
DistroRelease: Ubuntu 11.04
Package: blueman 1.21-4.1build1
ProcVersionSignature: Ubuntu 2.6.38-8.42-server 2.6.38.2
Uname: Linux 2.6.38-8-server x86_64
NonfreeKernelModules: nvidia
Architecture: amd64
Date: Sat Apr 16 13:51:58 2011
ExecutablePath: /usr/bin/blueman-applet
InstallationMedia: Ubuntu-Server 10.10 "Maverick Meerkat" - Release amd64 (20101007)
InterpreterPath: /usr/bin/python2.7
ProcCmdline: /usr/bin/python /usr/bin/blueman-applet
ProcEnviron:
 LANGUAGE=en_US:en
 LANG=en_US.UTF-8
 SHELL=/bin/bash
PythonArgs: ['/usr/bin/blueman-applet']
SourcePackage: blueman
Title: blueman-applet crashed with DBusException in call_blocking(): org.freedesktop.DBus.Error.ServiceUnknown: The name :1.105 was not provided by any .service files
UpgradeStatus: Upgraded to natty on 2011-04-04 (12 days ago)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

Revision history for this message
geonel (nginnh) wrote :
Revision history for this message
Apport retracing service (apport) wrote : This bug is a duplicate

Thank you for taking the time to report this crash and helping to make Ubuntu better. This particular crash has already been reported and is a duplicate of bug #437883, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.

tags: removed: need-duplicate-check
visibility: private → public
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.