SUMMARY The change of the shortcut for zoom (in desktop effects) is not saved. STEPS TO REPRODUCE 1. Go to settings -> Desktop behavior -> Zoom (not sure about exact name, set up different language) 2. change enlarge to meta+x, reduce to meta+y and original size to meta+c 3. save OBSERVED RESULT It is not saved. EXPECTED RESULT Saved! SOFTWARE/OS VERSIONS Operating System: openSUSE Tumbleweed 20210715 KDE Plasma Version: 5.22.3 KDE Frameworks Version: 5.84.0 Qt Version: 5.15.2 Kernel Version: 5.13.1-1-default (64-bit) Graphics Platform: X11 Processors: 4 × Intel® Core™ i5-6500T CPU @ 2.50GHz Memory: 15.5 GiB of RAM Graphics Processor: Mesa DRI Intel® HD Graphics 530 ADDITIONAL INFORMATION
...running wayland but also happens on X11
Works for me.
What can I do? It's a newly created profile, I switched from X11 to wayland. Any log which might help?
What do you meant on OBSERVED RESULT when said "It is not saved" ? Are you saying that after setting new shorcuts and pressing OK button to confirm you reopen the setting and the shortcuts are not there anymore? I tested on X11 to set Meta+y as reduce zoom and it works for me. There are some open bugs related to shortcuts not working when there is set multiple keyboard layouts. Does it is your case? Do you have more than one keyboard layout configured? Does it reproduces to any layout?
Created attachment 141438 [details] Screenshot setting Yes, I changed the default shortcuts and clicked "OK". When I go back to the settings it's back to default.
Currently I use wayland exclusively.
Try to set those shortcuts as Global Alternative, that is how I do. I don't even know what the shortcut on first column does. For a shortcut to work from anywhere it have to be of the Global type. In case of a desktop effect I think that it should be always as Global shortcuts, at least the way I understand it. With the current UI that is not obvious to the user and can lead to confusion.
Capital idea, this works. Thank you!
This bug was reported against an outdated version of KWin. We have made many changes since the. If the issue persists in newer versions can you reopen the bug report updating the version number.