Bluetooth connection leads to gnome crash

Hello everyone,

I am having an issue I cannot really pinpoint.

When I am connecting a bluetooth headset (tried different ones) and switch from Headset to Handsfree mode, gnome crashes. It looks like a wireplumber crash leding to a coredump. Honestly, apart from this error log, I have no idea how I may solve this or debug it further - apart from switching to pulseaudio as test - which I did not yet do (no time yet to check it further). I tried different bluetooth devices as well as the current kernels 6.17 and 6.18.

I am on the testing branch

Here is the journalctl with the problem: Coredump after audioswitch - Pastebin.com

What else can I do? What may you need to debug it further?

1 Like

I noticed the same problem today and could pin it down to wireplumber. After downgrading wireplumber and libwireplumber to version 0.5.12-1 the problem is gone, but that can only be a temporary solution. As I’m currently working I didn’t have much time for searching a solution. I would also be interested to know how to debug further when coredumping occurs.

Edit:

I found this related gnome issue
So for now it’s best to stay on wireplumber 0.5.12-1 until they solve it.

4 Likes

thank you! I downgraded wireplumber and it works again :slight_smile:

Thanks for reporting this issue and for the solution.
It would be very interesting to know how did you manage to pin down the reason to wireplumber, as a mean of learning. I was out of ideas as GNOME kept crashing, there were no ways to give a command or do anything. Thanks

I only use my wireless headset for video conferences and the last time I had one was in mid december. My system is using btrfs with automatic snapshot creation when updating with pacman. So first I tried to find out with which update the problem began. Then, knowing it had something to do with bluetooth and sound, I looked at the packages in that update (Testing Update 2026-01-01). As there were just a few, I was pretty sure, that wireplumber would be that package. So I used the downgrade command to downgrad it, made a reboot and was happy again.

2 Likes

Thank you very much for your reply, I really appreciate it!

This topic was automatically closed 3 days after the last reply. New replies are no longer allowed.