https://bugs.kde.org/show_bug.cgi?id=386954
--- Comment #9 from Martin Flöser <mgraess...@kde.org> --- It might be that XWayland assumes a bug in the Wayland compositor. I read the documentation of pointer locking again and looked at the source code of XWayland and that doesn't fit. We have in the protocol: "If the client is drawing its own cursor, it should update the position hint to the position of its own cursor. A compositor *may* use this information to warp the pointer *upon unlock* in order to avoid pointer jumps." So KWin can ignore this hint (and does so) and it should only use it on unlock. But XWayland has a xwl_pointer_warp_emulator_set_fake_pos which uses the hint described above. I'll further investigate, but I think XWayland is built against the behavior of Weston and not against the spec. -- You are receiving this mail because: You are watching all bug changes.
