https://bugs.kde.org/show_bug.cgi?id=424000
Bug ID: 424000
Summary: Plasma(?) eats my "c" key
Product: plasmashell
Version: 5.19.2
Platform: Other
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: general
Assignee: k...@davidedmundson.co.uk
Reporter: ci3...@gmail.com
CC: plasma-b...@kde.org
Target Milestone: 1.0
SUMMARY
When starting Plasma my "c" key (German qwertz layout) does not trigger any
action anymore. Typing `setxkbmap de nodeadkeys` in the console reenable it.
STEPS TO REPRODUCE
1. Start Plasma or switching the keyboard layout to "Deutsch (Nur
Acute(´)-Akzentzeichen)".
2. Press the "c" key (e.g. in an editor).
OBSERVED RESULT
Nothing happens.
EXPECTED RESULT
A "c" is printed.
SOFTWARE/OS VERSIONS
Linux/KDE Plasma: Gentoo Linux 5.4.28
KDE Plasma Version: 5.19.2
KDE Frameworks Version: 5.71.0
Qt Version: 5.15.0
X-Server version: 1.20.8
ADDITIONAL INFORMATION
- I have the problem a very long time (1-2 years). Since the workaround is
pretty easy, I have not investigated in reporting or fixing it before.
- I'm not sure what system component is responsible. Please reassign, if you
have a better idea. I have tried `xev`. Here is the output with a working "c"
key:
```
KeyPress event, serial 40, synthetic NO, window 0xa400001,
root 0x1a2, subw 0x0, time 200291144, (1263,927), root:(1263,947),
state 0x0, keycode 54 (keysym 0x63, c), same_screen YES,
XLookupString gives 1 bytes: (63) "c"
XmbLookupString gives 1 bytes: (63) "c"
XFilterEvent returns: False
KeyRelease event, serial 40, synthetic NO, window 0xa400001,
root 0x1a2, subw 0x0, time 200291232, (1263,927), root:(1263,947),
state 0x0, keycode 54 (keysym 0x63, c), same_screen YES,
XLookupString gives 1 bytes: (63) "c"
XFilterEvent returns: False
```
Here is the output with a not working "c" key:
```
FocusOut event, serial 40, synthetic NO, window 0xa400001,
mode NotifyGrab, detail NotifyAncestor
FocusOut event, serial 40, synthetic NO, window 0xa400001,
mode NotifyUngrab, detail NotifyPointer
FocusIn event, serial 40, synthetic NO, window 0xa400001,
mode NotifyUngrab, detail NotifyAncestor
KeymapNotify event, serial 40, synthetic NO, window 0x0,
keys: 2 0 0 0 0 0 64 0 0 0 0 0 0 0 0 0
0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
KeyRelease event, serial 40, synthetic NO, window 0xa400001,
root 0x1a2, subw 0x0, time 200396769, (1265,1085), root:(1265,1105),
state 0x0, keycode 54 (keysym 0x63, c), same_screen YES,
XLookupString gives 1 bytes: (63) "c"
XFilterEvent returns: False
```
- Typing `setxkbmap de nodeadkeys` always fixes the problem. Switching the
layout with Plasma (per GUI) always triggers the problem.
- I recently experimented with the Neo layout. On the Neo layout the "c"
keyboard key is mapped to the letter "ä". When switching to Neo, my "ä" is not
working (and "c" is working). That means that the same keyboard key triggers
the false behaviour (at least within the same Plasma session). I also
discovered that, when I switch to Neo and type multiple times "ä" immediately
after the switch, the first "ä"s arrives in my terminal. Then some mechanism
triggers and all following "ä"s are eaten by some component.
- Typing `setxkbmap de neo` does _not_ fix the Neo layout.
- I have controlled my hotkeys. I have not found a global hotkey that begins
with "c".
If you have any suggestions how to debug or fix this, please say so. I will see
to collect the data.
--
You are receiving this mail because:
You are watching all bug changes.
