Bug 1311238 - Refused to switch profile to headset_head_unit
Refused to switch profile to headset_head_unit
Status: NEW
Product: Fedora
Classification: Fedora
Component: pulseaudio (Show other bugs)
26
x86_64 Linux
unspecified Severity high
: ---
: ---
Assigned To: Lennart Poettering
Fedora Extras Quality Assurance
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2016-02-23 12:01 EST by pavel.nedr
Modified: 2017-07-31 07:28 EDT (History)
14 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed:
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)


External Trackers
Tracker ID Priority Status Summary Last Updated
Red Hat Bugzilla 1305453 None None None 2016-02-23 12:01 EST

  None (edit)
Description pavel.nedr 2016-02-23 12:01:17 EST
Description of problem:
HSP/HFP profiles doesn't work with pulseaudio on my Fedora 22 and Fedora 23 installations.
I've tried to use it with both default settings and with ofono (enabling ofono with systemctl and using "load-module module-bluetooth-discover headset=ofono" in /etc/pulse/default.pa and system.pa), but it doesn't solve problem.

I have that problems with 3 different devices from Sony, Jabra and Logitech.

This bug may be related with #1305453 which is with High severity

Version-Release number of selected component (if applicable):
pulseaudio-7.1-1.fc23.x86_64
bluez-5.36-1.fc23.x86_64

How reproducible:
Always


Steps to Reproduce:
1. Connect and pair Bluetooth headset
2. Go to System Settings -> Multimedia -> Audio and Video -> Audio Hardware Setup
3. Select your device in Sound Card field,
4. Select profile "Head Set Unit (HSP/HFP)", click "Apply"

Actual results:
- If you reload this settings page, you'll see A2DP Sink profile again
- In log you can see "pulseaudio[11942]: [pulseaudio] module-bluez5-device.c: Refused to switch profile to headset_head_unit: Not connected" message
- You can't see any bluetooth input devices in pavucontrol Input Devices section (excepting monitor)


Expected results:
Voice recording should work with HSP/HFP profile as, say, in Android
Comment 1 Brian J. Murrell 2016-04-15 10:45:19 EDT
Sigh.  Bluetooth headset problems on Fedora again (still?).

I am also seeing this.

What needs to happen to have this fixed?  It's been probably a year or more since I have been able to use my B/T headset on Fedora.
Comment 2 Erwan Legrand 2016-07-13 09:14:18 EDT
This is possibly related to Bug 1356136, although in my case HSP/HFP is always activated and I can't switch to A2DP. I wonder whether the workaround I described in Bug 1356136 works for this bug.
Comment 3 Fedora End Of Life 2016-11-24 10:43:35 EST
This message is a reminder that Fedora 23 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 23. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '23'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 23 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.
Comment 4 Brian J. Murrell 2016-11-24 11:21:10 EST
This needs to have it's Version: updated to 24 as this still issue still exists in F24.  Can somebody with permission please make the change?
Comment 5 Brian J. Murrell 2016-11-24 12:28:04 EST
New information!  With some help from https://bugzilla.freedesktop.org/show_bug.cgi?id=97064 I added "headset=auto" to the "load-module module-bluetooth-discover" line in /etc/pulse/default.pa (and restart pulseaudio of course) and it now works!
Comment 6 Gabriel 2017-04-12 20:20:40 EDT
I'm facing the same issue under on a Lenovo T460 and RHEL 7.3.

$ rpm -qa | grep bluetooth
gnome-bluetooth-3.14.1-1.el7.x86_64
pulseaudio-module-bluetooth-6.0-8.el7.x86_64
gnome-bluetooth-libs-3.14.1-1.el7.x86_64

$ dmesg | grep Bluetooth
[   15.319094] Bluetooth: Core ver 2.21
[   15.319110] Bluetooth: HCI device and connection manager initialized
[   15.319114] Bluetooth: HCI socket layer initialized
[   15.319116] Bluetooth: L2CAP socket layer initialized
[   15.319121] Bluetooth: SCO socket layer initialized
[   15.337397] Bluetooth: hci0: Firmware revision 0.0 build 30 week 18 2016
[   16.887770] Bluetooth: BNEP (Ethernet Emulation) ver 1.3
[   16.887773] Bluetooth: BNEP filters: protocol multicast
[   16.887778] Bluetooth: BNEP socket layer initialized
[   36.300269] Bluetooth: RFCOMM TTY layer initialized
[   36.300278] Bluetooth: RFCOMM socket layer initialized
[   36.300372] Bluetooth: RFCOMM ver 1.11


Headset is a Logitech H800 and the pairing works smoothly. I can also see the HSP/HFP profile. However, the mic is not recognized.

gpborges@gpborges:~$ bluetoothctl
[NEW] Controller A4:34:D9:83:10:9D gpborges.br.ibm.com [default]
[NEW] Device 00:0D:44:DE:83:86 H800 Logitech Headset
[H800 Logitech Headset]# info 
Device 00:0D:44:DE:83:86
	Name: H800 Logitech Headset
	Alias: H800 Logitech Headset
	Class: 0x240404
	Icon: audio-card
	Paired: yes
	Trusted: yes
	Blocked: no
	Connected: yes
	LegacyPairing: no
	UUID: Audio Sink                (0000110b-0000-1000-8000-00805f9b34fb)
	UUID: A/V Remote Control Target (0000110c-0000-1000-8000-00805f9b34fb)
	UUID: Advanced Audio Distribu.. (0000110d-0000-1000-8000-00805f9b34fb)
	UUID: A/V Remote Control        (0000110e-0000-1000-8000-00805f9b34fb)
	UUID: Handsfree                 (0000111e-0000-1000-8000-00805f9b34fb)
[H800 Logitech Headset]# 

It would be great if we see this bug fixed.

Thanks in advance!
Comment 7 Gabriel 2017-05-26 17:42:27 EDT
I just installed kernel 4.11.3 (4.11.3-1.el7.elrepo.x86_64) in my RHEL 7.3 and the mic is still not working for my Logitech H800. :-( I am using Cinnamon and I used bluebuerry (GUI) to pair it. Same thing as with kernel 3.10. It lists the HFP but no mic is displayed to be selected. Tried from default sound settings and also pauvcontrol.
Comment 8 Fedora End Of Life 2017-07-25 16:15:09 EDT
This message is a reminder that Fedora 24 is nearing its end of life.
Approximately 2 (two) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 24. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '24'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not
able to fix it before Fedora 24 is end of life. If you would still like
to see this bug fixed and are able to reproduce it against a later version
of Fedora, you are encouraged  change the 'version' to a later Fedora
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.
Comment 9 Richard Allen 2017-07-30 12:21:43 EDT
Still present in Fedora 26
Comment 10 Brian J. Murrell 2017-07-31 07:25:30 EDT
Given comment #9, can somebody who has permission please update the Version: field of this ticket?

Note You need to log in before you can comment on or make changes to this bug.