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

--- Comment #11 from nyanpasu64 <nyanpas...@tuta.io> ---
> If I install pipewire-alsa and uninstall pulseaudio-alsa (with either
> pulseaudio or pipewire-pulse installed/running), now ALSA apps are using
> pipewire-alsa to talk directly(?) to pipewire. I no longer get volume keys
> in the task manager.

Update: I'm using pipewire-alsa, and I'm again seeing speaker mute icons in the
task manager when playing audio in Audacity (flatpak) in ALSA mode.

Additionally, this bug isn't as simple as ALSA being broken. The Audacious
music player triggers this bug (mute icon on pinned apps) in *PulseAudio* mode,
but *not* in ALSA mode (mute icon on Audacious). mpv (not sure if Pulse or
ALSA) triggers this bug, but Firefox (pulse-rust) does not.

Restarting plasmashell (I'm using systemd Plasma startup, so `systemctl --user
restart plasma-plasmashell`) while Audacious is playing in PulseAudio makes the
mute icon appear correctly, and it continues to appear correctly after
pausing/stopping and resuming playback. Switching to ALSA and back to Pulse, or
restarting Audacious, makes the bug return.

In other news, many apps are misbehaving when running under PipeWire. While
Audacious is playing, changing system volume or beginning Audacity playback has
an unusually long audio delay (slight delay in Audacious ALSA, longer delay in
Audacious PulseAudio, both delays increase with longer Audacious buffer sizes,
as if Audacious is causing PipeWire's latency to increase up to pipewire.conf's
default.clock.max-quantum).

Audacious (forgot if PulseAudio or ALSA) *sometimes* makes Audacity hang while
starting up.

Sublime Text is hanging for ~30 seconds in (pa_threaded_mainloop_wait ->
pthread_cond_wait@@GLIBC_2.3.2) when trying to close a tab and play a ding.

In the pipewire-alsa bug, the process is hanging on (snd_pcm_mmap_writei -> ...
-> poll), but this only happens in BambooTracker after I load a different file
and *then* try playback (before loading a file, playback works fine).

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

Reply via email to