Type of device: Desktop
Kernel/Krita version: Arch Linux (6.17.1-arch1-1), Krita version 5.2.13
Description of the issue (you can include screenshots):
Hello! Just yesterday I updated my entire system and for some reason Krita doesn’t detect certain shortcuts at all. I first noticed this when the undo shortcut just didn’t work, but going to the menu option itself works just fine, redo also has the same behavior and even panning the canvas with spacebar + left click doesn’t work unless I do the zoom shortcut (ctrl + spacebar) and let go of control. I noticed that even the icons for the pipette/zoom/pan have a delay after I hold down their respective keys. Last thing to note is that even the shortcut to make a new image (ctrl + n) don’t work and when choosing a template I can’t tab nor press enter to use the selected template.
I’ve had this shortcut issue appear before, but it wasn’t this grave, as all I had to do was select the undo menu option and the shortcut would work again. Any help would be a big help!
For more context about my system, here are a few more specs:
Hyprland/Wayland
qt version 5.15.17
As mentioned above, my system was fully updated just yesterday.
A bit unrelated, I also tried the git version on the AUR, but the package failed to build, the error was related to the CMake generation step when making the krita-git-exit package.
Have you checked the assignments of the shortcuts in Krita under ‘‘Settings’’ >> ‘‘Configure Krita’’ >> ‘‘Keyboard Shortcuts’’, there were some changes recently for a reason I can’t remember?
Did you try to rule your issue out by checking against the AppImage if the issue will also occur with it? The AppImage is Krita’s only official version, so the one and only build by the makers of Krita, if you shouldn’t know. And Arch is the distro which for a few years now leads the number of issues with Krita reported under Linux.
This mainly happens because, unfortunately, many repository and other builds of Krita are faulty because the maintainers of these alternative versions don’t follow Krita’s build instructions.
I downloaded and ran the appimage, but to no avail. The issue still persists.
As for the shortcuts I haven’t touched them at all, so everything there is still on their defaults, I do remember checking yesterday and confirming that the shortcuts are actually assigned.
I should add that when I invoke Krita via terminal, I notice that I get this output when it’s booting.
qt.qpa.xkeyboard: failed to compile a keymap
qt.qpa.xkeyboard: failed to compile a keymap
qt.qpa.xkeyboard: failed to compile a keymap
qt.qpa.xkeyboard: failed to compile a keymap
Loading plugin "/usr/lib/kritaplugins/kritaseexprgenerator.so" failed, "Cannot load library /usr/lib/kritaplugins/kritaseexprgenerator.so: (libKSeExprUI.so.4: cannot open shared object file: No such file or directory)"
Loading plugin "/usr/lib/kritaplugins/kritamypaintop.so" failed, "Cannot load library /usr/lib/kritaplugins/kritamypaintop.so: (libmypaint.so.0: cannot open shared object file: No such file or directory)"
QObject::startTimer: Timers cannot have negative intervals
krita.scripting: "Traceback (most recent call last):"
krita.scripting: " File \"/usr/lib/krita-python-libs/krita/__init__.py\", line 11, in <module>"
krita.scripting: " from .api import *"
krita.scripting: " File \"/usr/lib/krita-python-libs/krita/api.py\", line 15, in <module>"
krita.scripting: " from PyKrita.krita import *"
krita.scripting: "ModuleNotFoundError: No module named 'PyQt5'"
krita.scripting: "Could not import krita"
Warning: requested data for unknown action "path-break-at-selection"
I assume my issue is coming from the very beginning where xkeyboard is failing which is why my keyboard inputs don’t work half the time?
The same initial failure is present in both the Arch package from the extra repo and the appimage as well
Maybe I did not express it the right way, I did not say you changed something, but I believe to remember that there were a few shortcuts disabled for a reason I don’t recall, (but) not the actions they call. That is the background why I asked you to check the ones that no longer work like you expect them to work, in addition, you should check for disabled or incorrectly assigned keyboard shortcuts under Settings → Configure Krita → Canvas Input Settings.
I checked both settings and clicked the restore defaults on both and the shortcuts I mentioned remain the same, I looked at a few shortcuts and nothing seems to be disabled or anything of the sort in both menus. Still have no idea as to why this is even happening, my only hunch is that maybe qt changed something in the latest update, especially based on the output from the terminal saying qt.qpa.xkeyboard: failed to compile a keymap. Only a guess though, I don’t have the sufficient knowledge to say anything concrete.
Well, I don’t have any other ideas at the moment, so if all the shortcuts are assigned and mapped correctly.
If you don’t have any other ideas, and no more come up here in the forum, you should report this to the bug trackers at Krita, https://bugs.kde.org/, and Arch.
For Krita, I’m attaching my info template:
To report a bug, you must register at https://bugs.kde.org/ to gain access to the “KDE bug tracking system”, i.e. “KDE’s bug tracker”. Keep in mind that the e-mail address you use there must firstly be existing / valid and secondly that it can be viewed by any visitor to the site. But the likelihood of your address falling into the hands of spammers there seems to be very low, because the address I used to register with them, I’m using exclusively for access to the KDE bug tracking system and have not had a single spam mail in my mailbox in the years I have been registered there.
You can read what a bug report should look like under Reporting Bugs in the Krita manual (the input mask looks slightly different today), or the User Guide on KDE.ORG, which I like less. Please use the drop-down menus to select the software, i.e. Krita, the version number, the operating system and try to narrow everything down as much as possible using the drop-down menus available there.
Here you’ll find the mask to report bugs in Krita, you can open it when you are logged in into your account (if not logged in it will detour you to the start page):
So far the only solution I was able to find was found in this issue created on the libxkbcommon package’s gitlab. I would still prefer a solution that doesn’t require downgrading so any other solution would be great.
The solution provided was to downgrade the packages with the following command, but I recommend reading the linked issue first before executing this:
The bug has been fixed now so you can update without worry now, it really was just the libxkbcommon causing an issue on the experimental versions. A simple update should fix it!
Hello 
