Bug 373956

Created attachment 102894 [details]
Screen shot of shortcuts app in KDE

First discovered this bug in Mint 18 KDE ("Sarah", Plasma 5.6) and verified it in Kubuntu 16.10 (Plasma 5.7.5), both based on Ubuntu and in the current Bluestar Linux (Live version, based on Arch). This issue was not present in Linux Mint KDE 17.2, based on Plasma 4.

The issue is in the creation of custom keyboard shortcuts to send keyboard input. After creating the shortcut in the settings tool, when the shortcut is executed, the input it sends is all upper case (both letters and characters), as though the user were holding or locking the CAPS LOCK key in place while typing. 

However, this only appears to occur when sending input to KDE apps (i.e. Konsole).

Sending the keystroke in non-KDE apps (such at LibreOffice or in a text area in a web page in Chrome), the key combination appears to work correctly

I use shortcuts to create passphrases for use on the system. Since the wrong keys are being sent, I can't use the shortcut to, for example, log into Synaptic or some other app that requires a "sudo" password input.

To duplicate:

System Settings -> Shortcuts -> Custom Shortcuts
Click the Edit button, Click New -> Global Shortcut -> Send Keyboard Input

Click Trigger Tab, Click Shortcut button, type the desired key combination. In my testing, I used Alt+Shift+X (all my customer shortcuts use Alt+Shift+{some alphanumeric}.

Click the Action tab, enter the keys desired in the top text area. To send upper case or shifted characters, the key string must use Shift+(key).

To send the input MyTesting!123*, use the following string:
Shift+M:Y:Shift+T:E:S:T:I:N:G:Shift+1:1:2:3

Click Apply to save the shortcut. To test, keep the cursor in the input box, hit enter one or twice and execute the shortcut.

The results will be:

MYTESTING!!@#

However, in Google Plus's search box, the input was pasted correctly:

MyTesting!123

It doesn't appear to matter if I use upper or lower case characters in the string entered in the Action box. Past documentation has suggested using upper case, but it breaks either way.

I've attached a screen shot to show the error.