https://bugs.kde.org/show_bug.cgi?id=453506
Bug ID: 453506 Summary: Need to kick hotkeys on release, not press Product: kwin Version: 5.24.4 Platform: Manjaro OS: Linux Status: REPORTED Severity: normal Priority: NOR Component: wayland-generic Assignee: kwin-bugs-n...@kde.org Reporter: chibiry...@gmail.com Target Milestone: --- SUMMARY *** Key combinations are consumed on press, not on release which leads to inability to activate some combinations at all. Let's say that I have 2 languages/layouts installed and I want my hotkey be CTRL+SHIFT to switch them. I will be unable to do any combination that has CTRL+SHIFT in it, like CTRL+SHIFT+S (Save as... in Kate) or CTRL+SHIFT+CURSOR_ARROW to select words one by one in a text, for example. Basically, it's a copy of this ancient xorg bug which will never be fixed upstream: https://gitlab.freedesktop.org/xorg/xserver/-/issues/258 *** STEPS TO REPRODUCE 1. Have 2 languages/layouts installed 2. Make them switch using hotkey CTRL+SHIFT 3. Open Kate and type "The quick brown dog" 4. CTRL+SHIFT+<- (LEFT ARROW) to select the last word 5. Type "fox" OBSERVED RESULT The layout had been switched on the 4 step (before you pressed an arrow, because the hotkey was consumed on press) and there was no word selection, instead of "fox" you typed some other symbols in another language/layout, resulting in a sentence "The quick brown ащчdog" (Cyrillic symbols for example) EXPECTED RESULT Layout switching didn't occur, you selected the word "dog" and it was replaced with newly typed "fox", resulting in a sentence "The quick brown fox" SOFTWARE/OS VERSIONS Linux/KDE Plasma: 5.15.32-1-MANJARO (64-bit) (available in About System) KDE Plasma Version: 5.24.4 KDE Frameworks Version: 5.92.0 Qt Version: 5.15.3 ADDITIONAL INFORMATION I was very disappointed in finding out that this behaviour is present in wayland, because I was convinced that this would be fixed there from the start (there are a couple of posts about it dating 10 or so years ago), since it's basic and core functionality that was present on windows forever (and in many linux distros for a long time when maintainers just silently patched xorg by default). I'm not sure if it's a KWin issue or just Wayland, but there's was a similar Weston bug reported in the git some time ago, so I assumed it had to do with a compositor. -- You are receiving this mail because: You are watching all bug changes.