[kde] [Bug 441674] New: KDE custom hotkeys dropping letters used in trigger keys
Joe Dougherty
bugzilla_noreply at kde.org
Sat Aug 28 21:07:57 BST 2021
https://bugs.kde.org/show_bug.cgi?id=441674
Bug ID: 441674
Summary: KDE custom hotkeys dropping letters used in trigger
keys
Product: kde
Version: unspecified
Platform: Kubuntu Packages
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: general
Assignee: unassigned-bugs at kde.org
Reporter: joe.attaboy at gmail.com
Target Milestone: ---
SUMMARY: When creating a custom hotkey shortcut in Settings to send a text
string, if a letter is used in the trigger keys, and the string contains that
letter, the first instance of the letter is dropped when the string is sent.
STEPS TO REPRODUCE
1. Custom shortcuts -> Edit -> New -> Global Shortcut - Send Keyboard Input
2. Create a key trigger containing a letter. Example - Alt-Shift-F
3. In Action panel, build a string to send with the keystroke. Example:
Shift+f:o:o:Shift+b:a:r:Enter to send "foobar" and a return
4. Execute the trigger in any window (example, Kate)
5. The trigger sends: ooBar
6. Only the first instance of the letter is dropped. Change the build to
Shift+f:o:o:Shift+f:a:r:Enter
7. The trigger sends: ooFar
8. The use of the Shift is not consequential. This occurs on upper and lower
case letters.
OBSERVED RESULT
Alt-Shift-F (Shift+f:o:o:Shift+b:a:r:Enter) sends
ooBar
EXPECTED RESULT
FooBar
SOFTWARE/OS VERSIONS
Linux/KDE Plasma:
Operating System: Kubuntu 21.04
KDE Plasma Version: 5.21.4
KDE Frameworks Version: 5.80.0
Qt Version: 5.15.2
Kernel Version: 5.11.0-31-generic
OS Type: 64-bit
Graphics Platform: X11
ADDITIONAL INFORMATION
Just want to mention that this process has worked as expected to many past
versions. This appears to have been introduced only very recently. The previous
version of KDE I used was in Netrunner Twenty (20.01). This issue appeared in
their next version (xoxo - 21.01) and is in the current version of Kubunto,
which I'm currently using.
Keyboard layout is Generic 104-key for PC. This issue occurs on different
keyboards.
--
You are receiving this mail because:
You are the assignee for the bug.
More information about the Unassigned-bugs
mailing list