https://bugs.kde.org/show_bug.cgi?id=470113
Bug ID: 470113
Summary: Main keyboard layout switching shortcuts fire on press
instead of on release
Classification: Plasma
Product: kwin
Version: 5.27.5
Platform: Other
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: input
Assignee: kwin-bugs-n...@kde.org
Reporter: o...@geek.co.il
Target Milestone: ---
SUMMARY
With multiple keyboard layouts configure, the shortcuts for switching layout
trigger on press instead of on release, making them unusable as a prelude for
other shortcuts - for example: CTRL+SHIFT is a common prefix for complex
shortcuts (Kate, for example, has a ton of default CTRL+SHIFT shortcuts, but
just consider "Save As"), but when setting Input Devices -> Keyboard ->
Advances -> switching to another layout -> Ctrl+Shift, all these shortcuts
become inaccessible.
The more common Alt+Shift (for people who grew up on multi-lingual MS-Windows)
is less common in KDE software but still breaks a lot of useful functionality
in other apps.
STEPS TO REPRODUCE
1. In System Settings -> Input Devices -> Keyboard -> Layouts, set two or more
layouts.
2. Click the "Main shortcuts" setting and choose, well, anything in the list
that opens - but lets try "Left Ctrl" for the most damage.
3. Go to any app and try to save the document with CTRL + S.
OBSERVED RESULT
The layout switches.
EXPECTED RESULT
The expected action for the combined shortcut should trigger.
SOFTWARE/OS VERSIONS
Operating System: KDE neon Testing Edition
KDE Plasma Version: 5.27.5
KDE Frameworks Version: 5.107.0
Qt Version: 5.15.9
Kernel Version: 6.2.0-20-generic (64-bit)
Graphics Platform: offscreen
Processors: 8 × Intel® Core™ i7-7820HQ CPU @ 2.90GHz
Memory: 31.2 GiB of RAM
Graphics Processor: Mesa Intel® HD Graphics 630
ADDITIONAL INFORMATION
- See the 20 years old Xorg bug
https://gitlab.freedesktop.org/xorg/xserver/-/issues/258 that describes the
problem with the original XKB specification that is probably the cause of this
kwin_wayland issue (and its 20 years worth of "me too"). Andrey Butirsky
(@butirsky) had commented there about opening a ticket here, so - 2 years late
- here we are.
- See bug #464805 and bug #420493 (X11-specific) for slightly different
behaviors about 'fire on press' that are also problematic and were (apparently)
fixed.
--
You are receiving this mail because:
You are watching all bug changes.
