Bug 332222

Summary:	executes 2 key combo when firing 3 key combo (keyboard layout related?!)
Product:	[Frameworks and Libraries] frameworks-kglobalaccel	Reporter:	Ryszard <rustedwolf>
Component:	general	Assignee:	Martin Flöser <mgraesslin>
Status:	REPORTED ---
Severity:	normal	CC:	alex.danila.web, kdelibs-bugs-null
Priority:	NOR
Version First Reported In:	unspecified
Target Milestone:	---
Platform:	openSUSE
OS:	Linux
Latest Commit:		Version Fixed/Implemented In:
Sentry Crash Report:

Description Ryszard 2014-03-16 17:43:24 UTC

I'm used to Alt+Shift key binding to change keyboard layout. And I work in Netbeans IDE it has a a neat combo (Alt+Shift+F) for source formatting. I've noticed that when I press that combo it fires the Alt+F combo thus opening the "File" context menu (which is weird) and fires up the Alt+Shift which changes the keyboard layout.
I assume this problem is caused as soon as the keys are pressed (but not released). 
I think that key combo should be fired only at the moment as soon as one of the keys (n the combo) are released. So when I press Alt+Shift and do not release the keys, the service waits for possible third key. 

Reproducible: Always

Steps to Reproduce:
1. Set the switch layout to Alt+Shit
2. Try any Alt+Shift+<any key> combo like Alt+Shift+Tab
Actual Results:  
Switched between windows
Changed the keyboard layout

Expected Results:  
Switched between windows

Comment 1 Thomas Lübking 2015-10-15 14:11:16 UTC

Afaik, the keyboard layout switch operates aside, ie. is not controlled by the kglobalaccel system (which however does operate on keypresses - the problem though is, that the kdb switch acts on pure modifier state changes)

No idea who to blame because of the kbd switch, I don't even know where that's implemented.

Comment 2 Thomas Lübking 2015-10-15 22:01:52 UTC

*** Bug 348528 has been marked as a duplicate of this bug. ***

Comment 3 Justin Zobel 2021-03-09 05:54:04 UTC

Thank you for the bug report.

As this report hasn't seen any changes in 5 years or more, we ask if you can please confirm that the issue still persists.

If this bug is no longer persisting or relevant please change the status to resolved.

Comment 4 Alex Dănilă 2021-03-09 06:52:32 UTC

I'm not the original reporter, but reporter of 348528: that issue has been fixed many releases ago.