Bug 107228 - Unable to connect Bluetooth headphones after switching audio profile.
Summary: Unable to connect Bluetooth headphones after switching audio profile.
Status: RESOLVED DUPLICATE of bug 107044
Alias: None
Product: PulseAudio
Classification: Unclassified
Component: daemon (show other bugs)
Version: unspecified
Hardware: x86-64 (AMD64) Linux (All)
: medium normal
Assignee: pulseaudio-bugs
QA Contact: pulseaudio-bugs
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2018-07-14 20:08 UTC by yousef.su.2000
Modified: 2018-08-11 10:04 UTC (History)
1 user (show)

See Also:
i915 platform:
i915 features:


Attachments

Description yousef.su.2000 2018-07-14 20:08:57 UTC
Bluetooth headphones were working since long ago. A few days ago I wanted to have a voice call so I tried to switch audio profile from 'High Fidelity Playback (A2DP sink)' to 'Headset Head Unit (HSF/HSP)', PulseAudio crashed and since then I can no longer get Bluetooth headphones to work.

Debugging stuff:
-----------------

 - Bluetooth headphones pair fine and all, but the sink is not shown in the 'Output Devices' tab in pavucontrol, and the 'Configuration' tab shows the device as 'Profile: Off'

 - If I attempt to change profile via pavucontrol or via blueman, PulseAudio stalls for a minute and then dumps core.

 - I find this in my journal: pulseaudio[26009]: Assertion '!u->thread' failed at modules/bluetooth/module-bluez5-device.c:1731, function start_thread(). Aborting.

 - It's interesting that PulseAudio since then has been saying this when running it: N: [pulseaudio] main.c: User-configured server at {2956b849822048eabdf5bd169ef03d78}unix:/run/user/1000/pulse/native, which appears to be local. Probing deeper.


Things I tried:
----------------

 - Rebooting
 - Removing device then pairing again
 - Check for any bluetooth-related or pulseaudio-related updates
 - Checked permissions on /run/user/1000/pulse/native
Comment 1 yousef.su.2000 2018-07-27 13:54:30 UTC
As an update: I tried compiling PA from source and it worked very fine. So, I tried reinstalling PulseAudio via Pacman (Arch's package manager) and that solved nothing.

I am still unsure what exactly is the problem.
Comment 2 Tanu Kaskinen 2018-07-29 16:09:04 UTC
Sorry for not responding immediately. This is a known bug in 12.0, and was fixed in the 12.1 release. Apparently Arch hasn't upgraded yet.

*** This bug has been marked as a duplicate of bug 107044 ***
Comment 3 yousef.su.2000 2018-07-29 17:02:51 UTC
(In reply to Tanu Kaskinen from comment #2)
> Sorry for not responding immediately. This is a known bug in 12.0, and was
> fixed in the 12.1 release. Apparently Arch hasn't upgraded yet.
> 
> *** This bug has been marked as a duplicate of bug 107044 ***

No not really, Arch's PulseAudio is on 12.2:

$ pulseaudio --version
pulseaudio 12.2
Comment 4 Tanu Kaskinen 2018-08-11 10:04:25 UTC
Ok, if this happens on 12.2, then this seems serious.

Bug tracking has moved to gitlab.freedesktop.org, can you file a new bug here (sorry, you'll need to register yet another account): https://gitlab.freedesktop.org/pulseaudio/pulseaudio/issues/new

Please attach a verbose log from the server that shows what happens during the crash. To get the log, first stop the running pulseaudio instance (stopping pulseaudio.socket is needed to prevent systemd from automatically restarting the service):

    systemctl --user stop pulseaudio.service pulseaudio.socket

Then start pulseaudio in a terminal:

    pulseaudio -vv

Then reproduce the crash and copy the log from the terminal (not necessarily all of it, but a good chunk from the end at least) and attach it to the bug report.


Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.