https://bugs.kde.org/show_bug.cgi?id=424319
--- Comment #50 from stephen <[email protected]> --- (In reply to Caeh Lyn from comment #49) > Hi, just to say I've getting this bug for something like 2 weeks. > I used to get this bug a while ago, but I guess it had been fixed until now. > > I can reliably trigger it by hitting the Windows key. > Alt tabbing doesn't seem trigger it as much. > Hitting the Windows key while Krita isn't focused triggers the bug too. > > I have a wacom BT S CTL 4100WL, Azerty keyboard. Windows 10. > > Thank you! Greetings Lyn! On Windows, it seems this issue is caused by a conflict between Wintab and Windows Ink APIs. A solution which has worked at a rate of 100% for me lately, was to simply tap "WIN + L". What it seems to do is reset all inputs including the ones from the Krita app. So far it has never failed me, so I recommend you do the same. When that issue occurs again, tap "WIN + L". Quickly log back into windows, and see if the issue persists. In principle it shouldn't. -- You are receiving this mail because: You are watching all bug changes.
