https://bugs.kde.org/show_bug.cgi?id=500597
--- Comment #2 from incan...@gmail.com --- I am beginning to realise that this problem was more subtle that I originally thought. I have found by experiment it's not just a matter of the comand you want to run and the chosen trigger, it's also down to whether (for example) you had one command assigned, and then go back and edit the command, or change the trigger. I have tried exporting the relevant sections of the shortcuts to a file, and found things like two different command strings in the file, but only one place where (think) the trigger sequence is defined. In the case I was looking at, one of the two command definitions appeared to be an "orphan" left behind when a definition was subsequently edited. I tied it on a fresh user account and as you say, attempting to assign "ctrl+r" brings up a warning, and the command "systemctl restart --user plasma-plasmashell" can be assigned to a shortcut, as long as you pick one that's not already assigned. So, questions- 1) It seems it's quite easy to break the key assignments config. For example I would not have knowingly ignored the warning about the "ctrl+r" trigger, but somehow I did try to assign that shortcut. Is there a simple way to reset the shortcut definitions to defaultsif they get corrupted? 2) Is the import+export format the System Settings tool uses for key assignments documented anywhere? 3) Is the import behavior of the shortcuts tool defined? I am mainly interested in whether an import file that defines just a few shortcuts will be merged into the current config, only overwriting any assignments to the same trigger sequences, or whether it will wipe out the current assignments and only create the new ones defined in the import file? -- You are receiving this mail because: You are watching all bug changes.
