#1124791 wireplumber: Upgrade to 0.5.13 crashes gnome-shell when connecting bluetooth headphones #1124791
- Package:
- wireplumber
- Source:
- wireplumber
- Description:
- modular session / policy manager for PipeWire
- Submitter:
- T S
- Date:
- 2026-05-13 02:43:02 UTC
- Severity:
- normal
- Tags:
Dear Maintainer, *** Reporter, please consider answering these questions, where appropriate *** * What led up to the situation? Ever since the upgrade to 0.5.13 when trying to connect bluetooth headphones the gnome-shell crashes. Journactl yields: X Y gsd-media-keys[6466]: Gvc:ERROR:../subprojects/gvc/gvc-mixer-stream.c:535:gvc_mixer_stream_get_port: code should not be reached X Y gsd-media-keys[6466]: Bail out! Gvc:ERROR:../subprojects/gvc/gvc-mixer-stream.c:535:gvc_mixer_stream_get_port: code should not be reached Seems to be same/related to: https://gitlab.gnome.org/GNOME/libgnome-volume-control/-/issues/34 https://www.mail-archive.com/debian-bugs-dist@lists.debian.org/msg2077712.html * What exactly did you do (or not do) that was effective (or ineffective)? * What was the outcome of this action? * What outcome did you expect instead? *** End of the template - remove these template lines ***
Workaround is: wpctl settings bluetooth.autoswitch-to-headset-profile false from https://gitlab.gnome.org/GNOME/libgnome-volume-control/-/issues/34
Hi, What's the reason for this bug being downgraded from critical to important? I think it qualifies as critical, as it leads to gnome crashing immediately, possibly leading to data loss as any open documents, sessions, etc. are not saved properly. Cheers, Bastian
Dear Maintainer, * What led up to the situation? I performed a daily upgrade of my system (Debian Forky), when after rebooting and logging in, gnome-shell crashed. Turning off my headphones (Sony WH-1000XM4) fixed the issue, but subsequently when trying to reconnect it, it would crash gnome-shell. * What exactly did you do (or not do) that was effective (or ineffective)? Ran `wpctl settings --save bluetooth.autoswitch-to-headset-profile false` * What was the outcome of this action? It stoped gnome-shell from crashing, even when reconnecting and between boots.
According to upstream this should be fixed with gnome-control-center 49.4: zmore /usr/share/doc/gnome-control-center/NEWS.gz ============ Version 49.4 ============ - Various translation updates Sound/Bluetooth - Update libgvc to fix crashes with new pipewire See also: https://gitlab.gnome.org/GNOME/gnome-control-center/-/commit/2da4105d1a2c54e47939fbd1c8363560dee8c836
Control: clone 1124791 -1 -2 Control: reassign -1 gnome-shell Control: fixed -1 49.3-2 Control: reassign -2 gnome-control-center Control: fixed -2 49.4-1 https://gitlab.gnome.org/GNOME/gnome-control-center/-/commit/2da4105d1a2c54e47939fbd1c8363560dee8c836 this only fixes gnome control center, not gnome-shell which ships its own copy of libgvc or one of its library does). libgvc is copied into project source directory, it is not a dynamically loaded library. Every project including libgvc has to upgraded its copy. I believe upstream (both GNOME and wireplumber) concluded this is a libgvc bug. Thus this bug about gnome-shell should be reassigned to gnome-shell (I could do that on my side if need be) and cloned to every project in Debian including libgvc (that list I don't know so I cannot do this clone). These bugs should be kept opened until a fixed copy is including in Debian. For gnome control center we can already conclude that forky and sid are fixed as they ship 49.4-1. It seems gnome-shell is fixed in forky (49.3-2) and sid (49.3-3) as: gnome-shell (49.3-2) unstable; urgency=medium * Team upload * d/patches/libgvc: Update libgvc to prevent crashes with newer Pipewire. This updates it to 47c47a42 (2026-01-23) which is the latest version, and the version currently used in gnome-shell's main branch. (Closes: #1126514) * d/watch: Convert to v5 format * Update Lintian overrides