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

--- Comment #17 from Mariusz Libera <[email protected]> ---
(In reply to Niklāvs Koļesņikovs from comment #16)
> Oh, that's neat. Mariusz, if you happen to encounter this again, can you
> maybe check the output of `wpctl status`? It would be interesting to see, if
> that tool is reporting the correct state (the default sink and source have *
> prefix to their listings) and whether it's possible to use `wpctl
> set-default <id>` or `wpctl clear-default <id>` to return to a sane state or
> not. The id should be the same as what wpctl showed for its list command.
> 
> Also I think when I last encountered this, it was possible to recover by
> restarting the audio stack instead of Plasma, which on Arch is done with
> `systemctl --user restart pipewire{,-pulse}.socket`, assuming you're using
> the PipeWire audio stack.

`wpctl status` displays the correct status matching System Settings Sound kcm.
`wpctl set-default` functions correctly, but neither it nor `wpctl
clear-default` fixes the applet. using `systemctl --user restart
wireplumber.service` fixed the applet, but maybe it also restarts pipewire as a
dependency? So far I don't even know what triggers this bug.

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

Reply via email to