SUMMARY If I bind a key on my tablet to English E and switch to Ukrainian keyboard layout, the binding will do nothing. If I bind the a key on my tablet to a key with Ukrainian layout selected, for example Є, the binding won't work at all, no mater the selected keyboard layout. STEPS TO REPRODUCE 1. Bind a key on a tablet or a pen to a keyboard key, for example E, apply 2. Switch keyboard layout to Ukrainian 3. Try to use the binding on a text field 4. Switch keyboard layout back to English 5. Try to use the binding on a text field 1. Switch keyboard layout to Ukrainian 2. Bind a key on a tablet or a pen to any alphabetical keyboard key 3. Try to use the binding on a text field OBSERVED RESULT The binding only works with English keyboard layout. A binding created with a non-English keyboard layout doesn't work at all EXPECTED RESULT Bindings should be independant of the selected keyboard layout SOFTWARE/OS VERSIONS Operating System: Arch Linux KDE Plasma Version: 6.4.3 KDE Frameworks Version: 6.16.0 Qt Version: 6.9.1 Kernel Version: 6.15.7-zen1-1-zen (64-bit) Graphics Platform: Wayland Processors: 12 × AMD Ryzen 5 5600H with Radeon Graphics Memory: 16 GiB of RAM (13.5 GiB usable) Graphics Processor 1: AMD Radeon Graphics Graphics Processor 2: NVIDIA GeForce RTX 3060 Laptop GPU ADDITIONAL INFORMATION It might be related to https://bugs.kde.org/show_bug.cgi?id=453661, but there for me a keybinding created with Ukrainian keyboard layout works, here only ones created with English do.
Just to confirm, you aren't trying to trigger a shortcut but even something as simple as "E" not being printed anywhere is happening for you right?
I have two buttons on my tablet assigned to Shift+Ctrl+Z and Ctrl+Z, and one assigned to «E» (for eraser). When I switch to Ukrainian keyboard layout and try to use these buttons on my tablet, they do nothing, the button that is assigned to «E» and normally should print E, doesn't print anything, and Ctrl+Z with Shift+Ctrl+Z also do nothing. I'll make a video demonstration.
This looks like bug 501541, I'm merging this into that report. *** This bug has been marked as a duplicate of bug 501541 ***