Bug 726608

Summary:	Bluetooth headset not working if bluetooth is started from init.
Product:	Gentoo Linux	Reporter:	Francisco Lloret <fcolloret>
Component:	Current packages	Assignee:	Gentoo Linux bug wranglers <bug-wranglers>
Status:	RESOLVED NEEDINFO
Severity:	normal	CC:	jstein
Priority:	Normal
Version:	unspecified
Hardware:	All
OS:	Linux
Whiteboard:
Package list:		Runtime testing required:	---

Description Francisco Lloret 2020-06-01 07:24:06 UTC

If I add bluetooth service to default runlevel and pulseaudio is compiled with headset support, the HSP/HFP headset pairing fails with a "Host is down" error. Other headsets with only A2PD support pairing work OK.

The issue don't occurs if I delete bluetooth from default runlevel and start it manualy after boot. Also, when failed, it works if I restart bluetooth service with headset powered off.

Reproducible: Always

Steps to Reproduce:
1. Install bluez and add it to default runlevel
2. Install pulseaudio with --native-headset USE
3. reboot systema  nd try to pairing a supported HSP/HFP headset
Actual Results:  
"Host is down" error when pairing a HSP/HFP headset if bluetooth is started from init and pulseaudio is compiled with headset support.


Expected Results:  
Pairing must always works with bluetooth started from default runlevel

bluez-5.54, pulseaudio 13.0, blueman 2.1.3, gentoo-sources 5.4.38

Comment 1 Jonas Stein gentoo-dev

2020-06-01 10:17:56 UTC

It is sad to read that you have problems with the software. The situation seems to be a bit more complicate and requires some analysis.
We can not help you efficiently via bug tracker. The bug tracker aims rather on specific problems in .ebuilds and less on individual systems. 

With regard to your question collect the following information when asking for help: 
logs, software version, exact hardware version, kernel version and config.

I have had very good experience on the gentoo IRC [1] with questions like this. Of course there are also forums and mailing lists [2,3].
I hope you understand, that I will close the bug here therefore and wish you good luck on one of the mentioned channels [4].
Please reopen the ticket in order to provide an indication for an specific error in an ebuild or any gentoo related product.

[1] https://www.gentoo.org/get-involved/irc-channels/
[2] https://forums.gentoo.org/
[3] https://www.gentoo.org/get-involved/mailing-lists/all-lists.html
[4] https://www.gentoo.org/support/