Type of device* : Graphics tablet
Brand and version of the device: XP-Pen Artist pro 16 gen 2
System** : Arch Linux with KDE Plasma version 6.4.3
* graphics tablet/display tablet/2-in-1 laptop/Android tablet
** Windows/Linux/Mac/Android, + version (you’ll find it in Help -> Show system information for bug reports)
Description of the issue (you can include screenshots): Hiya. On Krita for Linux (this doesn’t happen on windows) Every time I press a hotkey on my macropad that came with my tablet, it has a chance of getting “stuck,” and looping until it decides to stop. The most infuriating case of this is when it loops Ctrl+Z and I either have to redo all of it or I draw something after it’s done undoing and I can’t redo it. I’d love if anybody with a bit more insight could help with this. It only happens on Linux and I don’t think the desktop environment I use matters, as it was happening while I used other WMs like Qtile. Thanks.
Here you should make use of Krita’s Undo History Docker, there you can scroll to the point you want to go back to and with a click Krita will jump to the chosen point. BUT here it is the same true what you already mentioned, if you directly make any action after this unwanted CTRL + Z, it will sadly delete the part of the undo history from your last edit to the point where this unwanted hung CTRL + Z brought you !
Currently, I have no idea what the reason for this could be on your system, at least if you don’t use chat apps from Tencent, so WeChat or QQ (if these exist for Linux too), because these are known to notorious interfere with other keys, lead to stuck keys, etc., so if you use Krita and these apps too, you should decide what is more important to you, chatting or painting …
Hiya, thanks for the reply. I’m not aware of any apps on my system that could be interfering with my shortcuts beyond my Window Manager but, the issue was still present previously. It also happens across multiple tablets. Previously it was an issue with a pen button, now it is some keys on the macropad.
Okay, there is one thing I overlooked, for whatever reason. Something that has been noticeable in recent years are error messages from Arch installations, don’t ask me for the reasons. Arch-based distributions, i.e., offshoots of Arch, seem to be less prone to the problems reported here in the forum, only the main branch Arch itself has been the distribution with the most reported problems here on KA in the last ~3 years. As if the maintainers of the offshoots would maintain their Arch based distros better.
I also forgot to ask which version of Krita you are using and from which installation source. In the latter case, AppImage is always preferable, and in the event of errors with non-AppImage Krita installations, it is always advisable to test with AppImage to see if the error also occurs with it.
The background to this is that many maintainers of repositories and other versions, RPM, snap, Flatpak, etc., are known for regularly introducing errors because they disregard the build instructions and who knows what else. In any case, it is interesting that most Linux problems do not occur with the AppImage, the only official version from Krita’s creators, and that the often-complained-about “big bug in Krita” could be fixed this way – but this is not always the case, only most of the time!
I used the Arch Linux Repository version of Krita for a long time, but recently switched to the Steam version of Krita. The issue has happened across both versions.
Interesting to hear that Arch is the most problem-prone though.
And no one knows why. The only thing I can think of is that Arch is a cutting-edge distribution that always includes the latest developments—whether it’s worth it to always have the latest developments at the price of a potentially unstable operating system is something everyone has to decide for themselves.
I have similar issues with things getting stuck mostly pan and select tool often activating seemingly out of nowhere (mostly when I seem to press two pen buttons at once). This happened when I started using Wayland, not happening on X11, so my guess is it’s because Krita is still running in compatibility mode. Unfortunately I can’t switch back to x11 because it’s basically broken and unusable in my display setup, so I have no choice.
!