You are not logged in.

#1 2025-04-03 15:10:02

wwaldner
Member
Registered: 2025-04-03
Posts: 1

Connecting bluetooth headset - crash

The short is, I have a bluetooth headset that I had connected and working. This was working great, until I paired the headset with another device. After this, things went downhill.

Since pairing with another device, every time I connect to this headset with my Arch machine, it crashes. It crashes, in that hyprland goes away. I am not sure what state the machine is in, all I have is black screen.  If I hit ALT+CTL+DEL it reboots.

I have tried to unpair and re-pair, same thing. Each time it connects to this headset, down I go.

I am not familiar enough with Arch to know where to even look for problem. I tried to scan journalctl for errors, but I don't see anything particular...

help!

Offline

#2 2025-05-30 15:27:07

idaweb
Member
Registered: 2025-05-30
Posts: 1

Re: Connecting bluetooth headset - crash

Hi !

I have the same issue here. Did you fix it ?

Last edited by idaweb (2025-05-30 15:29:09)

Offline

#3 2026-01-04 16:03:14

vindolin
Member
Registered: 2026-01-04
Posts: 3

Re: Connecting bluetooth headset - crash

I now have the same problem.
My Soundcore Space Q45 headset has been working flawless since I switched to arch.
After a restart of my system, I logged in and then switched on my headphones.
I heard the bluetooth connection sound and then Gnome crashed to the login screen and my headphones played the disconnect sound.
Before I could login, the headphones connected again and the screen went black for a second before the login screen appeared again.
This would loop until I switched off the headphones.
My other Bluetooth earbuds still work without any problems.
I've unpaired/untrusted/repaired the headset but nothing works.

Did you find a solution?

Last edited by vindolin (2026-01-04 16:40:07)

Offline

#4 2026-01-05 05:03:59

tle130475c
Member
Registered: 2024-06-22
Posts: 3

Re: Connecting bluetooth headset - crash

I have problem with bluetooth headset like following:

1. Can successfully pair the device through bluetooth and play audio on that no problem
2. When try to join Microsoft Teams meeting using browser (Chrome, Firefox), at provide permission to access headset's microphone => GNOME crash, auto logout

I guess the problem is between pipewire and bluetooth as It have no problem when using an usb dongle to connect the headset to computer

Offline

#5 2026-01-05 08:57:14

vindolin
Member
Registered: 2026-01-04
Posts: 3

Re: Connecting bluetooth headset - crash

I've also posted the bug to the CachyOS forums: https://discuss.cachyos.org/t/gnome-cra … cted/20755

I posted it here first, because that was the only thread about the problem I could find.

Duckduckgo found another thread on https://forums.linuxmint.com/viewtopic.php?t=449210 but the site seems to be down ATM.

Looks like something in gsd-media-keys causes a Gvc:ERROR.


Jan 04 21:57:50 nerdonomicon kernel: input: soundcore Space Q45 (AVRCP) as /devices/virtual/input/input52
Jan 04 21:57:50 nerdonomicon systemd-logind[1266]: Watching system buttons on /dev/input/event11 (soundcore Space Q45 (AVRCP))
Jan 04 21:57:52 nerdonomicon gsd-media-keys[130916]: **
Jan 04 21:57:52 nerdonomicon gsd-media-keys[130916]: Gvc:ERROR:../gnome-settings-daemon/subprojects/gvc/gvc-mixer-stream.c:535:gvc_mixer_stream_get_port: code should not be reached
Jan 04 21:57:52 nerdonomicon gsd-media-keys[130916]: Bail out! Gvc:ERROR:../gnome-settings-daemon/subprojects/gvc/gvc-mixer-stream.c:535:gvc_mixer_stream_get_port: code should not be reached
Jan 04 21:57:52 nerdonomicon systemd-coredump[187396]: Process 130916 (gsd-media-keys) of user 1000 terminated abnormally with signal 6/ABRT, processing...
Jan 04 21:57:52 nerdonomicon systemd[1]: Started Process Core Dump (PID 187396/UID 0).
Jan 04 21:57:52 nerdonomicon gnome-shell[130378]: **
Jan 04 21:57:52 nerdonomicon gnome-shell[130378]: Gvc:ERROR:../gnome-shell/subprojects/gvc/gvc-mixer-stream.c:535:gvc_mixer_stream_get_port: code should not be reached
Jan 04 21:57:52 nerdonomicon gnome-shell[130378]: Bail out! Gvc:ERROR:../gnome-shell/subprojects/gvc/gvc-mixer-stream.c:535:gvc_mixer_stream_get_port: code should not be reached
Jan 04 21:57:52 nerdonomicon gnome-shell[130378]: == Stack trace for context 0x55a1982e3460 ==
Jan 04 21:57:52 nerdonomicon gnome-shell[130378]: #0   55a1983afaa8 i   resource:///org/gnome/shell/ui/init.js:21 (1ddd6fe8d8d0 @ 48)
Jan 04 21:57:52 nerdonomicon systemd-coredump[187398]: Process 130378 (gnome-shell) of user 1000 terminated abnormally with signal 6/ABRT, processing...
Jan 04 21:57:52 nerdonomicon systemd[1]: Started Process Core Dump (PID 187398/UID 0).
Jan 04 21:57:52 nerdonomicon systemd-coredump[187397]: [?] Process 130916 (gsd-media-keys) of user 1000 dumped core.

                                                 Stack trace of thread 130916:
                                                 #1  0x00007f3fbeabc645 g_cond_wait (libglib-2.0.so.0 + 0xa3645)
                                                 #2  0x00007f3fbea40575 g_async_queue_pop_unlocked (libglib-2.0.so.0 + 0x27575)
                                                 #3  0x00007f3fbeac62f7 n/a (libglib-2.0.so.0 + 0xad2f7)
                                                 #4  0x00007f3fbeac5d69 n/a (libglib-2.0.so.0 + 0xacd69)
                                                 #5  0x00007f3fbe4a80d6 n/a (libc.so.6 + 0xa80d6)
                                                 #6  0x00007f3fbe53b05c n/a (libc.so.6 + 0x13b05c)

                                                 Stack trace of thread 131070:
                                                 #0  0x00007f3fbe4b0892 n/a (libc.so.6 + 0xb0892)
                                                 #1  0x00007f3fbe4a42d8 n/a (libc.so.6 + 0xa42d8)
                                                 #2  0x00007f3fbe52cb33 ppoll (libc.so.6 + 0x12cb33)
                                                 #3  0x00007f3fbea828a0 n/a (libglib-2.0.so.0 + 0x698a0)
                                                 #4  0x00007f3fbea82982 g_main_context_iteration (libglib-2.0.so.0 + 0x69982)
                                                 #5  0x00007f3fbea829d2 n/a (libglib-2.0.so.0 + 0x699d2)
                                                 #6  0x00007f3fbeac5d69 n/a (libglib-2.0.so.0 + 0xacd69)
                                                 #7  0x00007f3fbe4a80d6 n/a (libc.so.6 + 0xa80d6)
                                                 #8  0x00007f3fbe53b05c n/a (libc.so.6 + 0x13b05c)

                                                 Stack trace of thread 131074:
                                                 #0  0x00007f3fbe4b0892 n/a (libc.so.6 + 0xb0892)
                                                 #1  0x00007f3fbe4a42d8 n/a (libc.so.6 + 0xa42d8)
                                                 #2  0x00007f3fbe52cb33 ppoll (libc.so.6 + 0x12cb33)
                                                 #3  0x00007f3fbea828a0 n/a (libglib-2.0.so.0 + 0x698a0)
                                                 #4  0x00007f3fbea82b2f g_main_loop_run (libglib-2.0.so.0 + 0x69b2f)
                                                 #5  0x00007f3fbed238ac n/a (libgio-2.0.so.0 + 0x1258ac)
                                                 #6  0x00007f3fbeac5d69 n/a (libglib-2.0.so.0 + 0xacd69)
                                                 #7  0x00007f3fbe4a80d6 n/a (libc.so.6 + 0xa80d6)
                                                 #8  0x00007f3fbe53b05c n/a (libc.so.6 + 0x13b05c)

                                                 Stack trace of thread 131115:
                                                 #0  0x00007f3fbe4b0892 n/a (libc.so.6 + 0xb0892)
                                                 #1  0x00007f3fbe4a42d8 n/a (libc.so.6 + 0xa42d8)
                                                 #2  0x00007f3fbe52cb33 ppoll (libc.so.6 + 0x12cb33)
                                                 #3  0x00007f3fbea828a0 n/a (libglib-2.0.so.0 + 0x698a0)
                                                 #4  0x00007f3fbea82982 g_main_context_iteration (libglib-2.0.so.0 + 0x69982)
                                                 #5  0x00007f3fbccc285e n/a (libdconfsettings.so + 0x785e)
                                                 #6  0x00007f3fbeac5d69 n/a (libglib-2.0.so.0 + 0xacd69)
                                                 #7  0x00007f3fbe4a80d6 n/a (libc.so.6 + 0xa80d6)
                                                 #8  0x00007f3fbe53b05c n/a (libc.so.6 + 0x13b05c)
                                                 ELF object binary architecture: AMD x86-64
Jan 04 21:57:52 nerdonomicon systemd[1]: systemd-coredump@5-3-187396_187397-0.service: Deactivated successfully.
Jan 04 21:57:52 nerdonomicon systemd[1]: systemd-coredump@5-3-187396_187397-0.service: Consumed 301ms CPU time over 335ms wall clock time, 138.9M memory peak.
Jan 04 21:57:52 nerdonomicon systemd[130000]: org.gnome.SettingsDaemon.MediaKeys.service: Main process exited, code=dumped, status=6/ABRT
Jan 04 21:57:52 nerdonomicon systemd[130000]: org.gnome.SettingsDaemon.MediaKeys.service: Failed with result 'core-dump'.
Jan 04 21:57:52 nerdonomicon systemd[130000]: org.gnome.SettingsDaemon.MediaKeys.service: Consumed 298ms CPU time over 2h 2min 35.910s wall clock time, 69.3M memory peak.
Jan 04 21:57:53 nerdonomicon systemd[130000]: org.gnome.SettingsDaemon.MediaKeys.service: Scheduled restart job, restart counter is at 1.
Jan 04 21:57:53 nerdonomicon systemd[130000]: Starting GNOME keyboard shortcuts service...
Jan 04 21:57:53 nerdonomicon systemd[130000]: Started GNOME keyboard shortcuts service.
Jan 04 21:57:53 nerdonomicon systemd[1]: Starting Hostname Service...
Jan 04 21:57:53 nerdonomicon systemd[1]: Started Hostname Service.
Jan 04 21:58:00 nerdonomicon systemd-coredump[187400]: [?] Process 130378 (gnome-shell) of user 1000 dumped core.

Last edited by vindolin (2026-01-05 08:59:38)

Offline

#6 2026-01-05 10:21:07

MathieuPetit
Member
Registered: 2021-04-28
Posts: 4

Re: Connecting bluetooth headset - crash

Exact same issue with a Sony 1000xm4. Gsd-media-key seems to crash when connecting the headset.

Offline

#7 2026-01-05 10:45:46

MathieuPetit
Member
Registered: 2021-04-28
Posts: 4

Re: Connecting bluetooth headset - crash

As per https://github.com/bluez/bluez/issues/1767

 wpctl settings bluetooth.autoswitch-to-headset-profile false 

mitigates the issue for me.

Offline

#8 2026-01-05 13:38:39

vmaurin
Member
Registered: 2026-01-05
Posts: 1

Re: Connecting bluetooth headset - crash

Original bug and workaround here https://gitlab.gnome.org/GNOME/libgnome … te_2643955

(downgrade wireplumber and libwireplumber to 0.5.12)

Offline

#9 2026-01-05 17:11:13

vindolin
Member
Registered: 2026-01-04
Posts: 3

Re: Connecting bluetooth headset - crash

MathieuPetit wrote:

As per https://github.com/bluez/bluez/issues/1767

 wpctl settings bluetooth.autoswitch-to-headset-profile false 

mitigates the issue for me.

Thanks that fixed it for me!

Edit: use the --save switch to make it persistent.

wpctl settings --save bluetooth.autoswitch-to-headset-profile false

Last edited by vindolin (2026-01-06 18:58:17)

Offline

Board footer

Powered by FluxBB