https://bugs.kde.org/show_bug.cgi?id=525548
Bug ID: 525548
Summary: Audio Volume applet shows duplicated devices after
devices rapidly disappear/reappear
Classification: Plasma
Product: plasmashell
Version First 6.7.5
Reported In:
Platform: CachyOS
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: Audio Volume widget
Assignee: [email protected]
Reporter: [email protected]
CC: [email protected]
Target Milestone: 1.0
DESCRIPTION
The Audio Volume applet lists some input/output devices more than once. The
duplicate
entries appear in the applet popup only; System Settings -> Audio shows a clean
list, so the
server-side object set is correct and the applet's device model is at fault.
Restarting
plasmashell (systemctl --user restart plasma-plasmashell.service) clears the
duplicates.
STEPS TO REPRODUCE
1. Trigger rapid destruction and recreation of all ALSA sinks/sources, e.g. by
stopping and
starting wireplumber (all ALSA devices are torn down and re-added within ~2
s).
2. Switch away from the session and back a few times while this churn happens.
3. Open the Audio Volume applet popup.
OBSERVED RESULT
Some input/output devices are listed 1-2 extra times. The number of duplicates
grows with
the number of switch/churn cycles. The duplicates are visible in the applet
popup; the same
devices appear exactly once in System Settings -> Audio and in pavucontrol.
Volume control
from the applet can then act on a stale entry.
EXPECTED RESULT
The applet model should deduplicate when a device with the same identity is
re-added, so the
popup always matches the actual set of server-side objects.
SOFTWARE/OS VERSIONS
Operating System: CachyOS Linux
KDE Plasma Version: 6.7.5
KDE Frameworks Version: 6.30.0
Qt Version: 6.11.2
Kernel Version: 7.2.3-1-cachyos-bore-lto (64-bit)
Graphics Platform: Wayland
PipeWire 1.6.8, WirePlumber 0.5.17
ADDITIONAL INFORMATION
This may be related to bug 473093 ("Multiple duplicate entries after interface
re-connection", RESOLVED/UPSTREAM) and its upstream report
https://gitlab.freedesktop.org/pipewire/pipewire/-/issues/3414, which was fixed
in PipeWire
by commit 820ca907 (Aug 2023). That report was about duplicates after resume or
after
switching device profiles; the trigger here is different (rapid remove/add
churn of all
devices), and it still reproduces on PipeWire 1.6.8 / Plasma 6.7.5. If triagers
consider
this the same root cause, feel free to mark it as a duplicate - I could not
tell from the
earlier report whether the applet-side model accumulation was fully addressed.
No screenshot attached: I currently cannot reproduce the duplicates on demand,
they appear
after an unpredictable number of switch cycles. I will attach one in a comment
as soon as
they show up again.
--
You are receiving this mail because:
You are watching all bug changes.
