https://bugs.kde.org/show_bug.cgi?id=424319
--- Comment #13 from Dmitry Kazakov <dimul...@gmail.com> --- Hi, Stephen and Dummsaccs! >From the symptoms you describe it looks like Krita gets a KeyPress event for some key and never gets a KeyRelease for it. It makes Krita think that the key is pressed forever, which blocks all actions other than painting. If my guess is right then switching to another app and then back to Krita should exit this locked state (Krita resets its internal key-tracking state on every FocusIn event). I have found a small bug in the key processing code, but I'm not sure it is related to this bug. Could you do some tests for me? 1) Download 'dk1-failing' package from here: https://yadi.sk/d/wO9UmqtHIs-nIw 2) Remove existing 'krita.log' file (it is placed in %LOCALAPPDATA% folder) 3) Work with the package for some time until the problem appears 4) As soon as the problem appear go to Help->Show Krita Log For Bugreports 5) Save the log into some file, e.g. 'dk1-failing.log', and attach to this bug 6) Download 'dk2-fixed' package: https://yadi.sk/d/h5F3FJ6pbBTcuA 7) Remove existing 'krita.log' file (it is placed in %LOCALAPPDATA% folder) 8) Work with the package for some time trying to reproduce the problem 9) If the problem appears, go to Help->Show Krita Log For Bugreports 10) Save the log into some file, e.g. 'dk2-fixed.log', and attach to this bug These packages are basically Krita 4.4 Beta1, which is not yet released, but with extra logging added. I don't think this logging will affect performance in any way. -- You are receiving this mail because: You are watching all bug changes.
