bluez-test-adapter crashed with DBusException in call_blocking(): org.bluez.Error.NoSuchAdapter: No such adapter

Bug #939220 reported by bakytn
This bug report is a duplicate of:  Edit Remove
16
This bug affects 2 people
Affects Status Importance Assigned to Milestone
bluez (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

Just tried to launch bluez-test-adapter

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: bluez 4.98-2ubuntu1
ProcVersionSignature: Ubuntu 3.2.0-17.26-generic 3.2.6
Uname: Linux 3.2.0-17-generic x86_64
ApportVersion: 1.92-0ubuntu1
Architecture: amd64
Date: Thu Feb 23 08:27:39 2012
DuplicateOf: https://bugs.launchpad.net/bugs/837321
ExecutablePath: /usr/bin/bluez-test-adapter
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release amd64 (20110427.1)
InterestingModules: rfcomm bnep bluetooth
InterpreterPath: /usr/bin/python2.7
MachineType: FUJITSU LIFEBOOK E751
ProcCmdline: /usr/bin/python /usr/bin/bluez-test-adapter
ProcKernelCmdLine: BOOT_IMAGE=/boot/vmlinuz-3.2.0-17-generic root=UUID=44080ad6-a57f-4942-8121-24cccd2bc4d7 ro quiet splash vt.handoff=7
PythonArgs: ['/usr/bin/bluez-test-adapter']
SourcePackage: bluez
Title: bluez-test-adapter crashed with DBusException in call_blocking(): org.bluez.Error.NoSuchAdapter: No such adapter
UpgradeStatus: Upgraded to precise on 2012-02-19 (3 days ago)
UserGroups: adm admin cdrom dialout libvirtd lpadmin plugdev root sambashare sudo vboxusers
dmi.bios.date: 04/25/2011
dmi.bios.vendor: FUJITSU // Phoenix Technologies Ltd.
dmi.bios.version: Version 1.13
dmi.board.name: FJNB223
dmi.board.vendor: FUJITSU
dmi.board.version: B1
dmi.chassis.type: 10
dmi.chassis.vendor: FUJITSU
dmi.chassis.version: LIFEBOOK E751
dmi.modalias: dmi:bvnFUJITSU//PhoenixTechnologiesLtd.:bvrVersion1.13:bd04/25/2011:svnFUJITSU:pnLIFEBOOKE751:pvr10601115935:rvnFUJITSU:rnFJNB223:rvrB1:cvnFUJITSU:ct10:cvrLIFEBOOKE751:
dmi.product.name: LIFEBOOK E751
dmi.product.version: 10601115935
dmi.sys.vendor: FUJITSU
hciconfig:

rfkill:
 0: phy0: Wireless LAN
  Soft blocked: no
  Hard blocked: no

Revision history for this message
bakytn (bakytn) 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 this software better. This particular crash has already been reported and is a duplicate of bug #837321, 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
visibility: private → public
Revision history for this message
jhoechtl (johann-hoechtl) wrote :

The particular bug is marked as private, why? I am as well affected by this bug.

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

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

Changed in bluez (Ubuntu):
status: New → Confirmed
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
  • Duplicate of a private bug Remove

Other bug subscribers

Remote bug watches

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