https://bugs.kde.org/show_bug.cgi?id=401921
Martin Flöser <mgraess...@kde.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Status|REPORTED |RESOLVED
Resolution|--- |NOT A BUG
--- Comment #5 from Martin Flöser <mgraess...@kde.org> ---
After analyzing the debug output it looks like kodi is doing some things wrong.
It creates two wl_pointer objects as described in the github issue. On one of
them it sets a null cursor. On the other one it doesn't set a cursor at all.
Given that we should have no cursor - neither from Kodi nor from KWin. This
means that Kodi is also drawing it's own cursor. But Kodi is not using the
Wayland protocols for such an interaction. It should use the pointer
constraints interface and lock the cursor and use the relative pointer
interface for motion when the cursor is locked.
I'm setting this bug report to not a bug on our side.
--
You are receiving this mail because:
You are watching all bug changes.
