Bug 448568

Summary: Overview effect can be selected in the screen edges menu even if the effect is disabled
Product: [Applications] systemsettings Reporter: indecisiveautomator
Component: kcm_kwinscreenedgesAssignee: KWin default assignee <kwin-bugs-null>
Status: CONFIRMED ---    
Severity: normal CC: aleixpol, herzenschein, lucia.mrenica, nate, plasma-bugs-null, vlad.zahorodnii
Priority: NOR    
Version First Reported In: 5.23.90   
Target Milestone: ---   
Platform: Other   
OS: Linux   
Latest Commit: Version Fixed/Implemented In:
Sentry Crash Report:

Description indecisiveautomator 2022-01-15 23:25:01 UTC
SUMMARY
A user is able to bind the Overview effect to one of their desktop corners in the "Screen Edges" menu, even if the Overview effect is disabled. When attempting to activate the effect after setting this, it will not work. The effect needs to be activated in the Desktop Effects menu, where it is disabled by default. 


STEPS TO REPRODUCE
1. Disable Overview effect in Desktop Effects menu
2. Open Screen Edges settings and you will still be able to set the Overview effect to one of the edges
3. Trying to activate the effect will not work, as it is disabled in the Desktop Effects, but the user is still able to set this as an action in the Screen Edges menu


OBSERVED RESULT
User is able to bind Overview effect to a Screen Edge even if the effect is disabled in the Desktop Effects settings.


EXPECTED RESULT
User should not see the Overview effect listed in the Screen Edges menu if it is disabled.
If the Overview effect is disabled after the user has set it as a Screen Edge action, the edge should be set to "No Action". 


SOFTWARE/OS VERSIONS
Linux/KDE Plasma: 5.16.0-arch1-1
KDE Plasma Version: 5.23.90
KDE Frameworks Version: 5.90.0
Qt Version: 5.15.2

ADDITIONAL INFORMATION
Tested on Wayland but potentially a bug across X11 and Wayland.
Comment 1 Patrick Silva 2022-01-16 03:21:20 UTC
*** Bug 448548 has been marked as a duplicate of this bug. ***
Comment 2 Nate Graham 2022-02-22 18:18:58 UTC
*** Bug 450681 has been marked as a duplicate of this bug. ***