Bug 505816 - Overview screen edge does not work with reactivation delay of 0; migrate old settings to have the current minimum re-activation delay
Summary: Overview screen edge does not work with reactivation delay of 0; migrate old ...
Status: CONFIRMED
Alias: None
Product: kwin
Classification: Plasma
Component: Hotcorners and edges (other bugs)
Version First Reported In: 6.4.0
Platform: Fedora RPMs Linux
: NOR normal
Target Milestone: ---
Assignee: KWin default assignee
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2025-06-20 03:10 UTC by warren
Modified: 2025-06-25 20:43 UTC (History)
1 user (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 warren 2025-06-20 03:10:00 UTC
SUMMARY
When the reactivation delay setting for screen edges is too low, the overview effect fails to trigger most of the time. (in the previous version of plasma I had it set all the way to 0, the setting carried over and now no longer works the same way.)

STEPS TO REPRODUCE
1. In screen edge settings, set "activation delay" to 0 ms and "reactivation delay" to 50 ms
2. try to use the hot corner

OBSERVED RESULT
Windows jitter and the overview effect isn't fully triggered, unless you're extra fast with the mouse.

EXPECTED RESULT
the overview effect is triggered instantly with no delay

SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Fedora 42
KDE Plasma Version: 6.4.0
KDE Frameworks Version: 6.15.0
Qt Version: 6.9.1
Comment 1 Nate Graham 2025-06-20 14:53:51 UTC
I see the spinbox no longer lets you set it to below 125ms right now. Do you recall setting it to 0 using the GUI in the past? Or did you set it to 0 manually by editing the config file?
Comment 2 warren 2025-06-21 01:01:43 UTC
(In reply to Nate Graham from comment #1)
> I see the spinbox no longer lets you set it to below 125ms right now. Do you
> recall setting it to 0 using the GUI in the past? Or did you set it to 0
> manually by editing the config file?

I used the GUI.
In the current version you can set the reactivation delay lower than 125ms by turning down the activation delay setting to 0 first. The minimum now is 50 ms.
Comment 3 Nate Graham 2025-06-25 20:43:14 UTC
It looks like we increased the minimum value (perhaps because 0 produced weird effects) but didn't migrate old settings.