https://bugs.kde.org/show_bug.cgi?id=516157
stephen <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|WAITINGFORINFO |--- Status|NEEDSINFO |REPORTED --- Comment #3 from stephen <[email protected]> --- (In reply to Dmitry Kazakov from comment #2) > Hi, Stephen! > > Could you please try this bug with the latest version of Krita 6.x? And it > would be really nice to see a video of the issue. I don't fully understand, > what needs to be done to trigger the issue and what kind of device you use > to get it (tablet or touch or both). Hi Dmitry. Myself I do not know exactly how to trigger the issue manually. All I know is that when you keep Krita out of focus for a while, and then return to the app, or when you press on WIN key, the issue can occur. But it is a bit random. Now when the issue occurs, the current workaround is to press WIN + L to unregister and re-register input APIs. My speculation is that, this buggy behavior of Krita is caused by a "conflict between Windows ink and Wintab APIs". I can not confirm unfortunately. If you could not reproduce the issue itself with the instruction from the "STEPS TO REPRODUCE" section, I honestly have no idea how to trigger it again besides moving out of focus from Krita's window, for a browser, or another app, and then hovering over the canvas in Krita. I have absolutely no idea about how to track the API conflict itself, and the log viewer in Krita also shows nothing when the issue occurs. So it is complicated. -- You are receiving this mail because: You are watching all bug changes.
