https://bugs.kde.org/show_bug.cgi?id=451171
Niklāvs Koļesņikovs <89q1r1...@relay.firefox.com> changed:
What |Removed |Added
----------------------------------------------------------------------------
CC| |89q1r1...@relay.firefox.com
--- Comment #3 from Niklāvs Koļesņikovs <89q1r1...@relay.firefox.com> ---
Unlike the legacy PulseAudio, PIpeWire initializes as quickly as possible and
then does asynchronous device discovery. This itself is, I'd guess, invisible
in terms of popups. What, I expect, is most likely generating the popups is the
default sink change as higher priority sinks are discovered and become the new
default until either the initial device discovery is done or PW finds the user
chosen default sinks (what pavucontrol oddly denotes as fallback) at which
point it will stay with that device until the user changes the default sink or
the device disappears and the PW session manager picks the next default in the
order of the configured priority.
If my suspicious are correct, then the popups will keep happening unless the
discovered device is also the user preferred default sink (or there's no more
non-default sinks to discover). And because it could be set in some other way
than via plasma-pa (meaning one should not rely on prior knowledge of previous
plasma-pa default sink state), I'm not sure if there's an easy and quick to
check way to know if the default sink change flurry is over (but I'm not expert
on the PulseAudio API, so maybe there is one?). A less reliable method would be
to just suppress all such events for a set time after login, resume and
possibly session and/or tty switch.
--
You are receiving this mail because:
You are watching all bug changes.
