Bug 21758 - "Send Keyboard Input" shortcuts do not work in KDE in Mga6
Summary: "Send Keyboard Input" shortcuts do not work in KDE in Mga6
Status: RESOLVED FIXED
Alias: None
Product: Mageia
Classification: Unclassified
Component: RPM Packages (show other bugs)
Version: 6
Hardware: All Linux
Priority: Normal normal
Target Milestone: ---
Assignee: KDE maintainers
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2017-09-22 19:32 CEST by Dennis Griffin
Modified: 2018-06-04 01:25 CEST (History)
0 users

See Also:
Source RPM: ? KDE 5.8.7
CVE:
Status comment:


Attachments

Description Dennis Griffin 2017-09-22 19:32:12 CEST
Description of problem: KDE allows you to create custom keyboard shortcuts that type in text strings.  These do not work in Mga6 (KDE 5.8.7) but work fine in Mga5 (KDE 4.14.35) and cauldron (KDE 5.10.4)


Version-Release number of selected component (if applicable):
KDE 5.8.7

How reproducible: Always.  Tested with desktop, laptop & vbox running Mga6.


Steps to Reproduce:
1.In Mga6 KDE go to System settings/shortcuts/custom shortcuts.
2.Right click on the list of shortcuts, New/Global shortcut/Send Keyboard Input
3.Give your new shortcut a name, for example "test"
4.On the right side of the screen select the "trigger" tab
5.Press the button that says "None" and press CTRL+ALT+T
6.Select the "Action" tab.  Type in t:e:s:t (characters need to be separated by colon)
7.Select "Active Window" at the lower part of the screen and press "Apply".
8.Open konsole (or kwrite) and press CTRL+ALT+T.  You should see the word "test" just as if you typed it in on the keyboard. This works in Mga5 and cauldron but not Mga6. If you open the "Examples" section of the shortcuts list there is "Type "Hello"" which is a "Send Keyboard Input" type.  It also does not work in Mga6.  Oddly, if one of the characters you specify is a period that will show up, but not other characters. Try ".:.:." as the "Action" and your shortcut will type 3 periods.
David Walser 2017-09-23 15:48:11 CEST

Assignee: bugsquad => kde

Comment 1 Dennis Griffin 2018-06-04 01:25:23 CEST
After the big update this problem is resolved and works as it should with KDE 5.12.2

Status: NEW => RESOLVED
Resolution: (none) => FIXED


Note You need to log in before you can comment on or make changes to this bug.