Bug 413264

Summary:	Can't use Alt+ in Custom Shortcuts
Product:	[Plasma] plasmashell	Reporter:	Alexander Trufanov <trufanovan>
Component:	general	Assignee:	David Edmundson <kde>
Status:	RESOLVED DUPLICATE
Severity:	normal	CC:	bugseforuns, nate, plasma-bugs
Priority:	NOR
Version:	5.17.0
Target Milestone:	1.0
Platform:	Kubuntu
OS:	Linux
Latest Commit:		Version Fixed In:
Sentry Crash Report:

Description Alexander Trufanov 2019-10-21 08:43:10 UTC

SUMMARY

Since I've upgraded to plasma 5.17 my custom shortcuts like Alt+P have stopped working. I'm able to trigger dbus event via Call button or if I use simplier key combination. But whenever I use Alt in shortcut combo - it's not working.
It was working in previous version of Plasma.
It seems Global Shortcuts with Alt+ are working but these key events are not propagated to custom shortcuts

STEPS TO REPRODUCE
1. Open Custom Shortcuts app
2. Select Screenshots/Start screenshot tool/Trigger
3. Change shortcut from Print to Alt+P. Apply.

OBSERVED RESULT

Screenshot app can't be started with Alt+P.

EXPECTED RESULT

Screenshot app can be started with Alt+P.

SOFTWARE/OS VERSIONS
Operating System: Kubuntu 19.10
KDE Plasma Version: 5.17.0
KDE Frameworks Version: 5.62.0
Qt Version: 5.12.4
Kernel Version: 5.3.0-18-generic
OS Type: 64-bit
Processors: 4 × Intel® Core™ i7-3520M CPU @ 2.90GHz
Memory: 7,6 GiB of RAM

Comment 1 Patrick Silva 2020-02-07 12:50:21 UTC

on my system "Screenshots/Start screenshot tool/Trigger" is not present in "Custom shortcuts".
But I can set alt+p to open Spectacle in "Global shorctuts" kcm and it works as expected.

Operating System: Arch Linux 
KDE Plasma Version: 5.17.90
KDE Frameworks Version: 5.66.0
Qt Version: 5.14.1

Comment 2 Alexander Trufanov 2020-02-13 13:49:22 UTC

I've just retested with 
khotkeys       4:5.18.0-0ubuntu1~ubuntu19.10~ppa1

I can set Alt+ anything and Ctrl+Alt+ anything in KHotkeys.
ALt+ numeric keys and Ctrl+Alt+ numeric keys are working.
Alt+P or Alt+S and Ctrl+Alt+ with them are still not working.

Comment 3 Nate Graham 2021-03-10 22:11:34 UTC

Same root cause as Bug 386253.

*** This bug has been marked as a duplicate of bug 386253 ***