SUMMARY When releasing spacebar to end pan/zoom, the cursor gets "locked", it won't revert from zoom/pan mode to brush mode. Sometimes the it reverts itself to brush mode after a few seconds, other times the only cure is to lift the pen high so the pad cannot detect it. After returning the pen within detection range of the pad, the pen act as if press against the pad (it's hovering). The pen must be lifted several times from detection range of the pad for it to return to normal. The issue occurs only when using combination of spacebar and Wacom tablet, if I use the button on the pen, this issue doesn't appear. I have tried Krita 4.1.7, current Krita Next and current master (I can't get it to run, maybe my Qt libs are too old?) same results. Current AppImage of MyPaint and Gimp 2.10.6 work OK. Wacom model is CTL-6100WL. Haven't tried it on Windows. STEPS TO REPRODUCE 1. Open any image. 2. Pan the image with spacebar and pen. 3. Release the spacebar. OBSERVED RESULT The pen is stuck in pressed mode after spacebar has been released. EXPECTED RESULT The pen is reverted to normal mode after releasing the spacebar. SOFTWARE/OS VERSIONS Windows: - macOS: - Linux/KDE Plasma: Xubuntu 18.10 kernel 4.18.0-16-generic (available in About System) KDE Plasma Version: - KDE Frameworks Version: - Qt Version: 4.8.7 ADDITIONAL INFORMATION
Does this also happen with the nighties(Krita Next)? We're trying to resolve a whole puzzle of tablet bugs and maybe these are resolved in 4.2...
I have used krita-4.1.8-0218025-x86_64.appimage (Mar 29, 2019 6:48:40 PM) from https://binary-factory.kde.org/job/Krita_Stable_Appimage_Build/lastSuccessfulBuild/artifact/ And krita-4.2.0-pre-alpha-01fe31d-x86_64.appimage (Mar 30, 2019 4:23:33 PM) from https://binary-factory.kde.org/job/Krita_Nightly_Appimage_Build/lastSuccessfulBuild/artifact/ Same problem unfortunately... I also attempted to purge kritarc from .config but it didn't help. Is there any other config file to delete/rename or something I can try? I forgot to mention, I have found these bug reports which might be of some interest even if they are for different project: https://bugs.launchpad.net/inkscape/+bug/1458200 https://bugs.launchpad.net/inkscape/+bug/1400234 Some people have resolved a similar problem by using another keyboard. I tried it, but the problem persists.
Thanks for your comment! Automatically switching the status of this bug to REPORTED so that the KDE team knows that the bug is ready to get confirmed. In the future you may also do this yourself when providing needed information.
Removing the nib and spraying the pen with compressed air has solved this issue. It seems some kind of translucent thread got stuck in the pen, triggering this issue. My apologies for wasting your time.