Yakuake shortcuts work with QWERTY keyboard layout without problem but won't work with Devorak layout. I guess Yakuake also won't work with other keyboard layouts. When I switch from QWERTY to Devorak, Yakuake shortcuts still recognize the old position of the shortcuts. For instance, the position for "K" under QWERTY is "T" under Devorak. If I set a shortcut for "Ctrl + K" under QWERTY for Action A, then hitting "Ctrl + T" under Devorak would have the same result. It can be nice to keep the same shortcut position under different layouts, in some cases. But this can cause shortcut conflicts when using the new layout. My "Ctrl + K" is switch to next session for Yakuake. Under Devorak, that would be "Ctrl + T". But "Ctrl + T" is also the back button for vim's cscope plug-in.
Sorry, but Yakuake isn't involved with shortcuts handling on that low level. Reassigning.
(In reply to comment #1) > Sorry, but Yakuake isn't involved with shortcuts handling on that low level. > Reassigning. I thought Yakuake shortcut would not do the low level keyboard mapping and only get characters not key position. But it looks like Yakuake still remember the key position even after a keyboard layout change. On the other hand, the keyboard input for the terminal would change accordingly when keyboard layout changes. Other applications like Firefox would work normally. Its shortcut would change accordingly after layout change. So open a new tab is still "Ctrl + T".
May be the same as https://bugs.kde.org/show_bug.cgi?id=306374 which is assigned to plasma I have this problem, using a UK Colemak layout. All KDE apps (most annoyingly Kate) seem to have shortcuts bound to keystrokes, not characters, so they do not respect keyboard layouts. This means that all documentation for keyboard is incorrect (e.g. Kate tells me Ctrl-S is save: with Colemak it is Ctrl-R), and mnemonics fail (r for save, k for new, ; for print). This undocumented layout is also different from layouts in non KDE apps (Chrome, Firefox) which will generally respect my layout. For me personally this is particularly annoying as I use both pair programming workstations set to QWERTY with a keyboard hardware switched to Colemak, and a laptop set to Colemak. The shortcut layouts are different in each environment. KDE 4.13.1
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!
Dear Bug Submitter, This is a reminder that 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? This bug will be moved back to REPORTED Status for manual review later, which may take a while. If you are able to, please lend us a hand. Thank you for helping us make KDE software even better for everyone!
Thank you for reporting this issue in KDE software. As it has been a while since this issue was reported, can we please ask you to see if you can reproduce the issue with a recent software version? If you can reproduce the issue, please change the status to "REPORTED" when replying. Thank you!
(In reply to Justin Zobel from comment #6) > Thank you for reporting this issue in KDE software. As it has been a while > since this issue was reported, can we please ask you to see if you can > reproduce the issue with a recent software version? > > If you can reproduce the issue, please change the status to "REPORTED" when > replying. Thank you! Thanks for checking back on this old issue. Unfortunately I don't have the setup (OS + Yakuake) to test/reproduce this issue now. But for those with Yakuake installed, it should be relatively easy to test. Just (temporarily) switch to a non-QWERT keyboard layout and try the shortcuts.
Dear Bug Submitter, This bug has been in NEEDSINFO status with no change for at least 15 days. Please provide the requested information as soon as possible and set the bug status as REPORTED. Due to regular bug tracker maintenance, if the bug is still in NEEDSINFO status with no change in 30 days the bug will be closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging If you have already provided the requested information, please mark the bug as REPORTED so that the KDE team knows that the bug is ready to be confirmed. Thank you for helping us make KDE software even better for everyone!
This bug has been in NEEDSINFO status with no change for at least 30 days. The bug is now closed as RESOLVED > WORKSFORME due to lack of needed information. For more information about our bug triaging procedures please read the wiki located here: https://community.kde.org/Guidelines_and_HOWTOs/Bug_triaging Thank you for helping us make KDE software even better for everyone!