Bug 332322 - Ctrl- key bindings stop working on some applications when non English layout is on top of the list
Summary: Ctrl- key bindings stop working on some applications when non English layout ...
Status: RESOLVED WORKSFORME
Alias: None
Product: systemsettings
Classification: Applications
Component: kcm_keyboard_layout (show other bugs)
Version: unspecified
Platform: Gentoo Packages Linux
: NOR normal
Target Milestone: ---
Assignee: Andriy Rysin
URL:
Keywords:
: 332822 (view as bug list)
Depends on:
Blocks:
 
Reported: 2014-03-19 13:52 UTC by Szef
Modified: 2018-11-12 03:13 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In:
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Szef 2014-03-19 13:52:26 UTC
When you got several layouts in layouts list and top of the list is non-English (Russian for me) layout, some applications (Netbeans, QtAssistance) stop to answer Ctrl- key bindings (Ctrl-A, for example)

Reproducible: Always

Steps to Reproduce:
1.Open keyboard layout tab in control center->keyboard
2.Make non-English layout to be top of the list
3.Apply settings
4.Try to call any Ctrl- key bind in vulnerable application.
Actual Results:  
Application make nothing

Expected Results:  
Apllication must answer Ctrl- key bindings

No special per-application key bindings setups were applied.
Comment 1 Szef 2014-03-19 13:53:30 UTC
Actual version is 4.11.2
Comment 2 PG 2014-03-31 18:55:04 UTC
*** Bug 332822 has been marked as a duplicate of this bug. ***
Comment 3 Andrew Crouthamel 2018-11-11 04:35:34 UTC
Dear Bug Submitter,

This bug has been stagnant for a long time. Could you help us out and re-test if the bug is valid in the latest version? I am setting the status to NEEDSINFO pending your response, please change the Status back to REPORTED when you respond.

Thank you for helping us make KDE software even better for everyone!
Comment 4 Szef 2018-11-11 08:42:03 UTC
Much have changed since then.
On plasma 5, similar behaviour is not reproducing this bug anymore.
Have no idea if it is still in kde4.
Comment 5 Andrew Crouthamel 2018-11-12 03:13:39 UTC
Thanks for the update!