[regression] Bluetooth audio devices are not connected
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
bt-autoconnect |
Won't Fix
|
Undecided
|
Unassigned | ||
stream2ip |
Won't Fix
|
Undecided
|
Unassigned | ||
bluez (Ubuntu) |
Invalid
|
Undecided
|
Unassigned |
Bug Description
Binary package hint: bluez
A known Bluetooth headset is not connected any more in Ubuntu 10.04 LTS. Security and recommended Ubuntu updates were installed last on Dec 22 2010. Before that the device worked as it should.
The device can be browsed using 'sdptool browse MAC' but does not show up in in the bluetooth-applet drop down menu and is not shown in bold letters from the properties menu. Scanning for new devices also does not see the device thus re-pairing is not possible. Connecting the device as audio sink to PulseAudio fails (device not listed).
By running 10.10 in VirtualBox on the same hardware the headset was connected as usual, proofing that there is no hardware defect.
ProblemType: Bug
DistroRelease: Ubuntu 10.04
Package: bluetooth 4.60-0ubuntu8
ProcVersionSign
Uname: Linux 2.6.32-27-generic x86_64
Architecture: amd64
Date: Wed Dec 29 17:39:04 2010
InstallationMedia: Ubuntu 9.10 "Karmic Koala" - Release amd64 (20091027)
InterestingModules: rfcomm sco bnep l2cap btusb bluetooth
MachineType: Gigabyte Technology Co., Ltd. GA-MA78GM-UD2H
PackageArchitec
ProcCmdLine: BOOT_IMAGE=
ProcEnviron:
LANG=de_DE.utf8
SHELL=/bin/bash
SourcePackage: bluez
dmi.bios.date: 04/29/2009
dmi.bios.vendor: Award Software International, Inc.
dmi.bios.version: F3
dmi.board.name: GA-MA78GM-UD2H
dmi.board.vendor: Gigabyte Technology Co., Ltd.
dmi.board.version: x.x
dmi.chassis.type: 3
dmi.chassis.vendor: Gigabyte Technology Co., Ltd.
dmi.modalias: dmi:bvnAwardSof
dmi.product.name: GA-MA78GM-UD2H
dmi.sys.vendor: Gigabyte Technology Co., Ltd.
hciconfig:
hci0: Type: USB
BD Address: 00:19:15:49:E2:75 ACL MTU: 1017:8 SCO MTU: 64:8
UP RUNNING PSCAN
RX bytes:3728 acl:28 sco:0 events:120 errors:0
TX bytes:1060 acl:24 sco:0 commands:51 errors:0
rfkill:
4: hci0: Bluetooth
Soft blocked: no
Hard blocked: no
As a wokaround reconfiguring a device by removing the device and re-setup makes it operate again as usual.