https://bugs.kde.org/show_bug.cgi?id=410181
Bug ID: 410181
Summary: when using an xmodmap, some key-combinations never
reach the active application
Product: kwin
Version: 5.12.8
Platform: Ubuntu Packages
OS: Android 9.x
Status: REPORTED
Severity: normal
Priority: NOR
Component: libinput
Assignee: kwin-bugs-n...@kde.org
Reporter: arne_...@web.de
Target Milestone: ---
Created attachment 121712
--> https://bugs.kde.org/attachment.cgi?id=121712&action=edit
crie.xmodmap
SUMMARY
When I switch to a different keyboard layout with xmodmap, the CTRL-x key
combination does not reach the applications.
Curiously the blinking cursor reacts to the keystroke by restarting the
blinking.
STEPS TO REPRODUCE
1. switch to alternate keyboard layout with `setxkbmap de -option ctrl:nocaps;
xmodmap path/to/crie.xmodmap` — take the xmodmap from the attachment.
2. Select some text.
3. On a German keyboard type CTRL-y, on a US keyboard type CTRL-z (this is
mapped to CTRL-x in the xmodmap)
4. Observe that the text is not cut.
5. Switch back to your regular keyboard layout with `setxkbmap de -option
ctrl:nocaps` (replace de by your locale)
OBSERVED RESULT
CTRL-x does not reach the text field, the text is not cut, but the cursor
restarts blinking.
EXPECTED RESULT
CTRL-x reaches the text field and cuts the text.
SOFTWARE/OS VERSIONS
Windows:
macOS:
Linux/KDE Plasma: Kubuntu 18.04, Kernel: 4.15.0-52-generic
(available in About System)
KDE Plasma Version: 5.12.8
KDE Frameworks Version: 5.44.0
Qt Version: 5.9.5
ADDITIONAL INFORMATION
This is a long-standing bug and I’ve been using a workaround for years in Emacs
(use CTRL-SHIFT-x — this does not work in the browser, though). I also observed
this in Gentoo GNU/Linux with a customized setup, so this is not from the
distribution.
It might be connected to the switch to XCB with Qt5 (yes, the bug already
exists for that long).
--
You are receiving this mail because:
You are watching all bug changes.
