Package: gnome-shell Version: 50.2-3 Severity: important X-Debbugs-Cc: [email protected]
Dear Maintainer, gnome-shell (Wayland session) aborts when a Bluetooth headset's card profile changes rapidly, killing the whole session: Jun 10 16:36:36 gnix gnome-shell[4249]: Gvc:ERROR:../subprojects/gvc/gvc-mixer-card.c:211:_pa_context_set_card_profile_by_index_cb: assertion failed: (card->priv->target_profile) Jun 10 16:36:36 gnix gnome-shell[4249]: Bail out! Gvc:ERROR:../subprojects/gvc/gvc-mixer-card.c:211:_pa_context_set_card_profile_by_index_cb: assertion failed: (card->priv->target_profile) This looks related to, but distinct from, #1126514: that bug covered the "code should not be reached" assertion in gvc-mixer-stream.c:535 and was fixed in 49.3-2 by updating the bundled libgvc. The target_profile assertion in gvc-mixer-card.c:211 is still present in the libgvc snapshot shipped with 50.2-3, and is reachable when the set-card-profile callback fires after target_profile has already been cleared by a subsequent profile change (same class of race; previously seen in Ubuntu as LP: #1990952 in gnome-control-center's copy). Trigger in my case: the headset (EPOS H3PRO) had failing Bluetooth audio transports, causing WirePlumber to flip the card profile repeatedly: Jun 10 16:35:58 gnix wireplumber[2360]: spa.bluez5: Acquire /org/bluez/hci0/dev_00_16_94_7F_1E_A5/sep1/fd0 returned error: org.bluez.Error.Failed Jun 10 16:35:58 gnix wireplumber[2360]: spa.bluez5: Failure in Bluetooth audio transport /org/bluez/hci0/dev_00_16_94_7F_1E_A5/sep1/fd0 Jun 10 16:36:03 gnix wireplumber[2360]: spa.bluez5: Failure in Bluetooth audio transport /org/bluez/hci0/dev_00_16_94_7F_1E_A5/fd52 Jun 10 16:36:10 gnix wireplumber[2360]: spa.bluez5: Failure in Bluetooth audio transport /org/bluez/hci0/dev_00_16_94_7F_1E_A5/fd52 Jun 10 16:36:36 gnix gnome-shell[4249]: Gvc:ERROR:../subprojects/gvc/gvc-mixer-card.c:211:_pa_context_set_card_profile_by_index_cb: assertion failed: (card->priv->target_profile) A core dump was captured (coredumpctl, SIGABRT, PID 4249, 2026-06-10 16:36:37 CEST); I can provide a backtrace on request. Workaround that avoids the trigger: wpctl settings --save bluetooth.autoswitch-to-headset-profile false Relevant versions: gnome-shell 50.2-3 wireplumber 0.5.14-1 pipewire 1.6.6-1 libspa-0.2-bluetooth 1.6.6-1 Kernel 7.0.12+deb14-amd64 Bluetooth Intel BE201 (btintel_pcie, PCI 8086:A876) Session GNOME on Wayland Thanks Glenn
