Bug 422801 - Screen Edges for Virtual Desktop Switching are not working
Summary: Screen Edges for Virtual Desktop Switching are not working
Status: RESOLVED DUPLICATE of bug 422816
Alias: None
Product: kwin
Classification: Plasma
Component: general (show other bugs)
Version: 5.19.0
Platform: Other Linux
: HI normal
Target Milestone: ---
Assignee: KWin default assignee
URL:
Keywords: regression
Depends on:
Blocks:
 
Reported: 2020-06-11 08:14 UTC by Matthias Dahl
Modified: 2020-06-18 08:42 UTC (History)
1 user (show)

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


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Matthias Dahl 2020-06-11 08:14:12 UTC
SUMMARY
Since upgrading to 5.19.0, virtual desktops cannot be switched via screen edges, at least not reliably.

I have a setup with 8 virtual desktops (2 rows, 4 each). When I move the mouse cursor to a corner, the desktop is switched to its neighbour. But not when I move to an edge. If a window is present and I move the mouse cursor to the top edge, the desktop is switched, but this does not work on the other edges (a panel is on the bottom edge).

STEPS TO REPRODUCE
1. Configure a 4x2 virtual desktop layout.
2. Set "Switch desktop on edge" to "Always Enabled"
3. Set a "Activation delay" and "Reactivation delay" of 300ms
4. Move your mouse cursor to any desktop edge while the desktop is empty with just your panel showing

OBSERVED RESULT
Nothing happens.

EXPECTED RESULT
The virtual desktop should be switched according to the triggered edge.

SOFTWARE/OS VERSIONS
Windows: no
macOS: no
Linux/KDE Plasma: Gentoo ~amd64 w/ official kde and qt overlay
(available in About System)
KDE Plasma Version: 5.19.0
KDE Frameworks Version: 5.70.0
Qt Version: 5.15.0

ADDITIONAL INFORMATION
Comment 1 Matthias Dahl 2020-06-18 07:15:44 UTC
Commit bc2df9f84be7ff12ab7e67ee7931eae1f5aeacce (which references bug #422816), also fixes this bug. Thanks! :-)
Comment 2 Vlad Zahorodnii 2020-06-18 08:42:21 UTC
Yeah, bug 422816 and this one are caused by the same thing.

*** This bug has been marked as a duplicate of bug 422816 ***