https://bugs.kde.org/show_bug.cgi?id=524624

--- Comment #2 from Kacper Paczos <[email protected]> ---
I can confirm the same issue on an identical stack: Fedora 44, Plasma 6.7.4
(Wayland), PipeWire 1.6.8, WirePlumber 0.5.14 — but with a different trigger,
which suggests the root cause is the sink node disappearing and reappearing,
not the manual reconnect itself.

Sequence on my machine:

1. Bluetooth headphones (A2DP) are the default sink; volume keys work
correctly.
2. The A2DP transport dies on its own — the adapter firmware (Intel, Core Ultra
200V) drops completion reports; WirePlumber logs "spa.bluez5: Failure in
Bluetooth audio transport" and destroys the sink node.
3. At exactly that moment plasmashell logs:
   No object for name "bluez_output.F6_86_8E_2E_F3_7A.1"
4. The transport comes back a few seconds later, WirePlumber recreates the sink
under the same name (new object ID), audio keeps playing through Bluetooth, and
"pactl info" keeps showing Default Sink: bluez_output.F6_86_8E_2E_F3_7A.1
(state RUNNING).
5. From that point on, the volume keys change the volume of the built-in
speaker (the fallback sink) instead of the headphones — volume state confirms
it: the speaker drifted to 55% from my key presses while the headphones sit
untouched at 73%.

So the Pulse/PipeWire layer has the correct default the whole time; only
plasma-pa's model diverges — after the sink object is destroyed, it never
re-binds to the object recreated under the same name.

Regarding the question in comment 1: in my case the wrong-device volume control
issue occurred on its own — I did not click any devices in the applet, so I did
not observe the double-selection from bug 500968. This is an independent data
point showing the control mismatch does not require interacting with the
widget.

Related: I filed the BlueZ-side connection-state desync seen in the same
scenario separately: https://github.com/bluez/bluez/issues/2485 (it does not
affect plasma-pa, but it describes the same trigger).

-- 
You are receiving this mail because:
You are watching all bug changes.

Reply via email to