https://bugs.kde.org/show_bug.cgi?id=524804
Zamundaaa <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- Status|ASSIGNED |RESOLVED Latest Commit| |https://invent.kde.org/plas | |ma/kwin/-/commit/52626988ae | |5ba5a072970e8b9c863e49ca07c | |d55 Resolution|--- |FIXED --- Comment #2 from Zamundaaa <[email protected]> --- Git commit 52626988ae5ba5a072970e8b9c863e49ca07cd55 by Xaver Hugl. Committed on 07/10/2026 at 19:50. Pushed by zamundaaa into branch 'master'. wayland/pointerwarp: also set the locked pointer position to the warp request When we made pointer locking double buffered, interactions between pointer locking and warping changed. While before, the client could do something like - unlock the pointer - warp it - commit and the pointer would be warped, since unlocking the pointer was immediate, now the same sequence of requests ignores the pointer warp entirely. To fix this, on each pointer warp, set the locked pointer hint to match the warped position. Once the pointer is actually unlocked, the pointer is warped as expected. M +1 -0 autotests/integration/CMakeLists.txt M +11 -0 autotests/integration/kwin_wayland_test.h M +31 -1 autotests/integration/pointer_constraints_test.cpp M +19 -0 autotests/integration/test_helpers.cpp M +10 -2 src/wayland/pointerwarp_v1.cpp https://invent.kde.org/plasma/kwin/-/commit/52626988ae5ba5a072970e8b9c863e49ca07cd55 -- You are receiving this mail because: You are watching all bug changes.
