Bug 506549

Summary:	Cannot hear audio from Motorola H350 bluetooth headset.
Product:	[Fedora] Fedora	Reporter:	Bryan Christ <bryan.christ>
Component:	pulseaudio	Assignee:	Lennart Poettering <lpoetter>
Status:	CLOSED WORKSFORME	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	high	Docs Contact:
Priority:	low
Version:	11	CC:	lkundrak, lpoetter, wtogami
Target Milestone:	---
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2009-07-22 23:49:57 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Bryan Christ 2009-06-17 17:54:21 UTC

Description of problem:

Although I am able to pair my Motorola H350 headset with my system and the volume controls show up in the PulseAudio Volume control, I cannot hear audio.  In fact, when the output device is set to the H350, Totem will not even play the first frame of a video clip. 

Version-Release number of selected component (if applicable):

pulseaudio-0.9.15-14.fc11.x86_64
pulseaudio-module-bluetooth-0.9.15-14.fc11.x86_64
gnome-bluetooth-libs-2.27.5-1.fc11.x86_64
gnome-bluetooth-2.27.5-1.fc11.x86_64

How reproducible: 100%

Steps to Reproduce:
1.  Pair Motorola H350 bluetooth device with system.
2.  Change output device in PulseAudio Volume control to H350.
3.  Try to play a video clip with Totem.

Additional info:

lsusb showing bluetooth dongle:

Bus 004 Device 003: ID 0a12:0001 Cambridge Silicon Radio, Ltd Bluetooth Dongle (HCI mode)

Comment 1 Lennart Poettering 2009-06-25 16:14:28 UTC

Please be more elaborate. What happens exactly? Does playback seem to freeze? Does it play but the volume seems to be completely off? Do you get dmesg messages? What does pulseaudio -vvvvv say when this happens? What does bluetooth -nd say when this happens?

Comment 2 Bryan Christ 2009-07-02 20:37:35 UTC

Lennart,

I am now using a different bluetooth USB dongle and have installed the latest bluez/gnome-bluetooth packages from "updates-testing".  The combination of these two appear to have remedied my problem.

The only issue I see now is that if I walk out of range with the headset I have to do a pulseaudio --kill and --start in order to see the device again as an output device.  I suppose this issue should be filed under a different BZ though.

Comment 3 Lennart Poettering 2009-07-22 23:49:57 UTC

Bryan, you can simple use the gnome bluetooth menu to reactviate the headset. No need to kill/restart PA.

Closing this bug, since this bug seems to be gone.