Bug 453040 - screen edge desktop switch eventually always stops working
Summary: screen edge desktop switch eventually always stops working
Status: RESOLVED WORKSFORME
Alias: None
Product: kwin
Classification: Plasma
Component: general (other bugs)
Version First Reported In: unspecified
Platform: Ubuntu Linux
: NOR normal
Target Milestone: ---
Assignee: KWin default assignee
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2022-04-26 09:18 UTC by Hans Lambermont
Modified: 2024-06-12 10:28 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 Hans Lambermont 2022-04-26 09:18:27 UTC
SUMMARY
With 'Screen edges' -> 'Switch desktop on edge' set to 'always enabled' this starts working perfectly fine, for many days mostly, but it always eventually stops working.
This bug has been with KDE for many years (at least 10).

STEPS TO REPRODUCE
1. 'Screen edges' -> 'Switch desktop on edge' set to 'always enabled'
2. Just use the computer for many days, it triggers within something like 180 days (this run lasted 49 days).
3. Hitting an edge with the mouse no longer switches to another desktop. Everything else still works except for 'present windows' in the upper left corner.

OBSERVED RESULT
Hitting an edge with the mouse no longer switches to another desktop.

EXPECTED RESULT
Hitting an edge with the mouse switches to another desktop.

SOFTWARE/OS VERSIONS
Operating system: Ubuntu 20.04
KDE Plasma Version: 5.18.8
KDE Frameworks Version: 5.68.0
Qt Version: 5.12.8

ADDITIONAL INFORMATION
When this bug triggers the edges and corners still show blue-ish when the mouse gets near it (screen edge highlight).
Desktop switch via the scroll wheel on the background still works.
Desktop switch via the desktop panel in the task bar still works.
I always use 3 rows of 3 desktops each and no desktop switching animations are configured.
Comment 1 David Redondo 2024-06-12 10:28:57 UTC
Sorry this is not actionable or testable. No developer will run their PC for 180 days and their seems to be workaround - reboot.