Bug 507517 - volume jumps to maximum when mixer popup opens
Summary: volume jumps to maximum when mixer popup opens
Status: RESOLVED UPSTREAM
Alias: None
Product: plasmashell
Classification: Plasma
Component: Audio Volume widget (other bugs)
Version First Reported In: 6.4.3
Platform: Fedora RPMs Linux
: NOR major
Target Milestone: 1.0
Assignee: Plasma Bugs List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2025-07-26 17:35 UTC by Luan Vitor Simião Oliveira
Modified: 2025-08-08 17:25 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed/Implemented In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Luan Vitor Simião Oliveira 2025-07-26 17:35:30 UTC
SUMMARY
opening the volume popup makes the volume on the usb ALC4082 from my motherboard jump to 100% when using hw mixing, but both wireplumber and alsa report that the volume is at the same level.

changing the volume using the ui or the shortcut will make the volume go back to the original level

this happens every time

STEPS TO REPRODUCE
1. play audio with any app (with no audio playing it doesn't happen)
2. open audio widget

OBSERVED RESULT
volume jumps to maximum on headphones 

EXPECTED RESULT
volume stays at same level

SOFTWARE/OS VERSIONS
Operating System: Fedora Linux 42
KDE Plasma Version: 6.4.3
KDE Frameworks Version: 6.16.0
Qt Version: 6.9.1
Kernel Version: 6.15.7-200.fc42.x86_64 (64-bit)
Graphics Platform: Wayland
Processors: 16 × AMD Ryzen 7 9800X3D 8-Core Processor
Memory: 32 GiB of RAM (30.9 GiB usable)
Graphics Processor 1: NVIDIA GeForce RTX 4070 Ti SUPER (main)
Graphics Processor 2: AMD Radeon Graphics
Manufacturer: ASUS

ADDITIONAL INFORMATION
motherboard: rog crosshair x670e hero
Comment 1 Luan Vitor Simião Oliveira 2025-07-26 20:00:35 UTC
small correction, it still happens with software mixer, but when using it i just leave the hardware mixer volume at max so the change in volume is not perceivable
Comment 2 Luan Vitor Simião Oliveira 2025-08-04 18:40:42 UTC
could be a bug with the alsa-ucm-config for my board:
https://github.com/alsa-project/alsa-ucm-conf/issues/598
Comment 3 Nate Graham 2025-08-08 17:25:38 UTC
That sounds very, very likely.