On Wednesday June 05 2019 13:11:24 Gong, Zaiwen wrote:
> I also tried to modify this setting in file directly (this user's
> ~/.kde/share/config/kglobalshortcutsrc
That looks like your user is still using a KDE4/Plasma4 desktop. If so, you
could try to relaunch the plasma session. I do this periodically to reduce the
amount of virtual memory in use (swap space) without having to quit all
applications I have open:
```
#!/bin/sh
# first try nicely:
kquitapp plasma-desktop
# a bit more force
killall -1 plasma-desktop
killall -1 plasma
# even more
killall plasma-desktop 2>&1 > /dev/null
killall plasma 2>&1 > /dev/null
# radical:
killall -9 plasma-desktop 2>&1 > /dev/null
killall -9 plasma 2>&1 > /dev/null
. ${HOME}/.kde/env/kdewm.sh
kstart plasma-desktop &
exec ${KDEWM} --replace
```
In your case you can skip the killall lines. With a bit of luck this will
restart the kglobalshortcut daemon, thus forcing it to re-read the
configuration file. There must be a simpler and more targeted method of
restarting just that daemon (or getting it to re-read its configuration; the
KCM does just that after all). The script above has the advantage that it will
achieve the intended effect for any other change, as long as it restarts the
corresponding agent/daemon/whatever.
Of course this assumes that your user has his $HOME (or at least ~/.kde/) on a
networked disk that's accessible from all 30 machines.
R
