Grabbing a window for resizing operations leads the cursor to be only in one depiction regardless of actual resize direction: Arrows from left down to right up. Reproducible: Always
I never noticed and I thought that worked correctly. Might be a recent regression.
See https://phabricator.kde.org/D3202
*** Bug 383838 has been marked as a duplicate of this bug. ***
Git commit 1ca2aec77fee3ba0d82fa8ef71efe1290028f7d7 by Vlad Zagorodniy. Committed on 31/12/2018 at 10:35. Pushed by vladz into branch 'master'. [wayland] Don't use hardcoded move-resize cursor Summary: Currently, when resizing a window the cursor doesn't match the resize direction. The reason for that is the move-resize cursor is hardcoded. To fix that, CursorImage::updateMoveResize has to use AbstractClient::cursor. Also, because the move-resize cursor is updated after calling startMoveResize, we have to connect to AbstractClient::moveResizeCursorChanged. FIXED-IN: 5.15 Reviewers: #kwin, davidedmundson, broulik, romangg, graesslin Reviewed By: #kwin, graesslin Subscribers: davidedmundson, romangg, graesslin, kwin Tags: #kwin Maniphest Tasks: T5714 Differential Revision: https://phabricator.kde.org/D3202 M +186 -0 autotests/integration/pointer_input.cpp M +3 -0 cursor.h M +2 -1 pointer_input.cpp https://commits.kde.org/kwin/1ca2aec77fee3ba0d82fa8ef71efe1290028f7d7