bluetooth headset pairs but not available for audio

Bug #417863 reported by RagnarokAngel
32
This bug affects 5 people
Affects Status Importance Assigned to Milestone
gnome-bluetooth (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

Binary package hint: bluez-gnome

Description: Ubuntu karmic (development branch)
Release: 9.10
bluez:
  Installed: 4.48-0ubuntu1
  Candidate: 4.48-0ubuntu1
  Version table:
 *** 4.48-0ubuntu1 0
        500 http://us.archive.ubuntu.com karmic/main Packages
        100 /var/lib/dpkg/status

The mac address of my device is 00:1A:0E:A9:B1:C6 Motorola H350

It pairs and gets a headset profile just fine. I expected to be able to then use this as a headset via pavucontrol but it was unavailable as either an input or an output file.

Sorry if any of this info is posted twice.

ProblemType: Bug
Architecture: i386
Date: Sun Aug 23 17:25:20 2009
DistroRelease: Ubuntu 9.10
Package: bluez-gnome 1.8-1ubuntu1
ProcEnviron:
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SourcePackage: bluez-gnome
Uname: Linux 2.6.31-020631rc6-generic i686

Revision history for this message
RagnarokAngel (ragnarokangel-s) wrote :
Revision history for this message
komputes (komputes) wrote :

This seems to be a regression. This hardware was reported as working (somewhat) in Feisty:
https://bugs.launchpad.net/ubuntu/+source/bluez-btsco/+bug/50600/comments/7

This may also be related to the following bug which describes the ability to pair, but non working audio:
https://bugs.launchpad.net/ubuntu/+source/bluez/+bug/327284

Revision history for this message
komputes (komputes) wrote :

We tried to get this working using the following instructions:
https://help.ubuntu.com/community/BluetoothHeadset

It failed at step 11 when the modules could not be loaded.

We then tried to go through the workaround explained here, but it still did not work:
https://bugs.edge.launchpad.net/ubuntu/+source/bluez/+bug/327284/comments/20

Revision history for this message
hanzomon4 (hanzomon4) wrote :

I can confirm this... I paired my jawbone 2 but when setting my input and output to jawbone in sound preferences I get no audio... in or out

Changed in bluez-gnome (Ubuntu):
status: New → Confirmed
Revision history for this message
thefluxster (buy-ikentech) wrote :

Someone want to give these instructions a try in Koala? Sad that this hasn't been better integrated yet for Kharmic. i would consider this a high priority bug for laptop or netbook users...

The content of the text in the link is really for my sanity and may or may not render correctly in your browser. The links at the top of the linked blog post are more accurate but contain too much info. I've done my best to capture what I needed to get it working, not really meant for public consumption, but here it is:

http://linuxforkeysers.blogspot.com/2009/04/more-bluetooth-woes-in-jaunty-jackalope.html

As a piece of background, the trouble isn't so much the bluetooth as the use of pulseaudio with bluetooth. PulseAudio just isn't ready for this kind of "new" technology.

Revision history for this message
thefluxster (buy-ikentech) wrote :

Has anyone tested this again on the RC? If it's still present, what's the plan for Lucid? File new bug and watch it get ignored again? :(

affects: bluez-gnome (Ubuntu) → gnome-bluetooth (Ubuntu)
papukaija (papukaija)
tags: added: karmic
Revision history for this message
Marc MAURICE (dooblem) wrote :

Tested today with the H350 headset and my thinkpad T42p.
Works perfectly under Lucid.

Revision history for this message
Chris Stratford (chris-gondolin) wrote :

I'm seeing virtually the same behaviour under trusty on a headset that worked fine on raring (it was a bit iffy on saucy, but I think it eventually worked there too)

This is a Plantronics ML10 headset. It pairs ok, gets listed in sound settings, but selecting it there has no effect and no sound gets directed to the headset.

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.