Created attachment 152132 [details] short demo SUMMARY Setting any shortcut for Minimize All Windows in System Settings doesn't seem to do anything. Executing the shortcut seems to behave as if the meta key isn't pressed, other key combinations issue similar results. The only way to trigger Minimize all seems to be to place the Minimize All Windows widget on the panel and then assign a key combination to activate it, then it works. STEPS TO REPRODUCE 1. Assign a keyboard shortcut to Minimize All function in KWin in system settings 2. Try to use it OBSERVED RESULT Nothing happens, key combo ignored EXPECTED RESULT All windows are minimized Operating System: Arch Linux KDE Plasma Version: 5.25.5 KDE Frameworks Version: 5.98.0 Qt Version: 5.15.6 Kernel Version: 5.19.8-arch1-1 (64-bit) Graphics Platform: X11
You said that the meta key doesn't work for other shortcuts too... can you try to narrow this down? Like, is the Meta key broken in all shortcuts, but shortcuts using only Ctrl or Alt as modifiers work? What keyboard layout are you using? Are you doing any key re-mapping?
> You said that the meta key doesn't work for other shortcuts too... Sorry for the confusion, I meant to say no other key combination for this MinimizeAll function works. I think I've found the culprit. It turns out my MinimizeAll KWin script was turned off altogether. As soon as I turned it on it started working. I totally forgot KWin has two ways to hide all windows: via the ShowDesktop function(which is by default assigned to Meta+D and as far as i know can't be turned off) and MinimizeAll. And it turns out MinimizeAll is handled like an external script which can be turned off at will. However as soon as you turn off the script, it still lets you assign a shortcut for a given function(which was created when i first enabled the MinimizeAll script for the first time as far as i can tell) and doesn't inform the user that the script is actually disabled, so this may a UX issue. Sorry again for the confusion, i guess the bug report may be closed.
Yep, that makes sense. Letting you set shortcuts for disabled scripts/effects is not ideal though, yeah. We should probably hide these shortcuts from the KCM while the scripts/effects they control are themselves disabled.
The UX issue is even worse than described, as Shortcuts from KWin scripts are visible in Systemsettings even after the script has been uninstalled. As a workaround it is possible to delete their lines in ~/.config/kglobalshortcutsrc -- they're still visible until logout though. (Tested with Plasma 6.2)