Version: 3.3.91 (using KDE KDE 3.3.91) Installed from: Unlisted Binary Package OS: Linux Assigning a keyboard shortcut combination in Control Center > Regional > Keyboard Shortcuts with a non-latin layout causes that shortcut not to work. Example: In order to be able to use the customary CTRL+C and CTRL+V shortcuts while in Russian keyboard layout, I set up alternate shortcuts to these functions in Keyboard Shortcuts control panel. I along-side CTRL+C and CTRL+V i set up CTRL+"Russian Letter S" (located on "C" key") and CTRL+"Russian Letter M" (located on "V" key). The Keyboard SHortcuts gialogue accepted my shortcut combinations, however, DID NOT display the corresponding russian letter but a rectangular box. Upon switching to KWrite (or any other text-edit application), Pressing the chosen custom shortcuts results in either: no reaction at all, or the russian letter corresponding to the letter key pressed would show up. The action prescribed to this keyboard shortcut is not performed. This is particularly damaging while copying text. I would type a sentence in Russian, select it with the mouse, push the CTRL+C combination and watch the whole selection disappear and be replaced by russian letter S. Issue is persistent on KDE from v.3.2.3 onward (including 3.4b1). System Info: Pentium-based system. ps\2, 101 keys keyboard. (No Windows\Menu keys) Slackware 10 KDE 3.4b1 (also tested on 3.2.3, 3.3, 3.3.1, 3.3.2) Downloaded from the download.kde.org contrib/Slackware10
Just for information: there's an easier way of doing what you want. Set up your keyboard layout in X as "ru,us", so that a Latin representation is overlayed. This will get you your Ctrl+C shortcut working even when "C" is not "C", but "ะก". As for the bug itself, could it be just a font problem? Can you change your font and see if the dialog box shows the letter correctly?
I am marking this (earlier) bug a dupe of the later bug as the later bug specifies a KDE-based (as opposed to user-based) solution to the problem. Also, the later bug is confirmed and has votes. *** This bug has been marked as a duplicate of bug 176113 ***