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

            Bug ID: 507212
           Summary: Pulseaudio Volume Control (pa-applet) wakes up all
                    audio devices when opening
    Classification: Plasma
           Product: plasmashell
      Version First 6.4.3
       Reported In:
          Platform: Arch Linux
                OS: Linux
            Status: REPORTED
          Severity: minor
          Priority: NOR
         Component: Audio Volume widget
          Assignee: plasma-b...@kde.org
          Reporter: z...@omaera.org
                CC: isma...@gmail.com
  Target Milestone: 1.0

SUMMARY
Plasma's audio volume widget wakes up all audio devices when opening.

I have 4 audio devices, and 2 of them are USB DACs that power off (or enter a
stand-by mode) after a few minutes of inactivity. When I open the volume
control applet, it wakes them all up even though I haven't selected any yet.

STEPS TO REPRODUCE
1. Click the audio volume widget on the Plasma panel

OBSERVED RESULT
The widget should just open and list the devices, nothing else. But it wakes up
all audio devices as well.

EXPECTED RESULT
The widget should just open without talking to the audio devices at all unless
I select one and/or pressed the volume slider so it makes a sound.

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Arch Linux x86_64 updated to 20250718
KDE Plasma Version: 6.4.3
KDE Frameworks Version: 6.16.0
Qt Version: 6.9.1
Audio backend: pipewire + pipewire-pulse

ADDITIONAL INFORMATION
It can be seen using qpwgraph that opening the volume applet a connection is
opened to all audio devices in the system. I assume this is done so a sound can
be played when moving the volume sliders. The problem is that this wakes up all
audio devices that are in a standby state. It should only open a connection to
them when necessary (after pressing the volume slider of the interface, or
actually switching to the interface) and only with the interface in question,
not all of them.

So far to me this only happens in KDE Plasma. I haven't observed this behavior
in other DEs or operating systems yet. The behavior I've seen is that an
interface is woken up only when switching to it (or actual sound needs to be
played through it).

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

Reply via email to