Bug 516076

Summary: Triggering widget configuration by long pressing on widget changes widget values
Product: [Plasma] plasmashell Reporter: Schlaefer <openmail+kde>
Component: ContainmentAssignee: Plasma Bugs List <plasma-bugs-null>
Status: REPORTED ---    
Severity: normal CC: cwo.kde, isma.af, notmart
Priority: NOR    
Version First Reported In: 6.5.5   
Target Milestone: 1.0   
Platform: CachyOS   
OS: Linux   
Latest Commit: Version Fixed/Implemented In:
Sentry Crash Report:
Attachments: Minimal reproducible case with a single slider

Description Schlaefer 2026-02-16 10:30:59 UTC
Created attachment 189641 [details]
Minimal reproducible case with a single slider

SUMMARY

Triggering the widget configuration by long pressing on the widget changes the values of the widget itself: changes sliders, buttons etc.

STEPS TO REPRODUCE
1. Place the build-in volume widget onto the desktop
2. Long press the widget with the mouse to go into configuration mode

OBSERVED RESULT

Volume sliders, mute button, etc change their values when entering configuration mode.

EXPECTED RESULT

The widget should not change internal state when going into configuration mode.

SOFTWARE/OS VERSIONS

Operating System: CachyOS Linux 
KDE Plasma Version: 6.5.5
KDE Frameworks Version: 6.23.0
Qt Version: 6.10.2
Kernel Version: 6.19.0-2-cachyos (64-bit)
Graphics Platform: Wayland

Operating System: KDE Linux 2026-02-14
KDE Plasma Version: 6.6.80
KDE Frameworks Version: 6.24.0
Qt Version: 6.10.2
Kernel Version: 6.18.9-zen1-2-zen (64-bit)
Graphics Platform: Wayland

ADDITIONAL INFORMATION

This behavior doesn't seem to be exclusive to the volume widget but all widgets. I attached a minimal example plasmoid with just one slider.
Comment 1 cwo 2026-02-16 14:54:59 UTC
The problem is in ItemContainer:

https://invent.kde.org/plasma/plasma-workspace/-/blob/master/components/containmentlayoutmanager/itemcontainer.cpp?ref_type=heads#L459

Since 1560be8ab509c2a3a30c8381d382d8f9eeee5eb9, we send MouseButtonRelease events recursively to every child, so that e.g. the FolderView rubber band finishes instead of continuing in edit mode.

The problem seems to be that some components trigger on release; in particular checkable AbstractButtons toggle on mouse release. This means that for the volume (desktop) widget the switch, the mute buttons, and the tab buttons activate when entering edit mode.

Not sure how to best solve this - we could not send it to AbstractButtons, but there may be other components that trigger on release.