https://bugs.kde.org/show_bug.cgi?id=384805
--- Comment #2 from Michael Zanetti <mzane...@kde.org> --- Hi Martin, I'm not 100% sure either if it's really kwin... Maybe it's the panel? But perhaps it's something in that 1 pixel push back that break it? like, if it does setCursorPosition(x, y) trying to correct one of them by 1 (depending on the edge) but there's some issue in the calculation of the new x/y values? I'm just guessing here... For all I know is that it only happens on edges where that have an autohide panel and if libinput's properties are set to translate the cursor matrix. -- You are receiving this mail because: You are watching all bug changes.
