On Freitag, 15. März 2024 23:31:22 CET Patrick Shanahan wrote:
* Patrick Shanahan
[03-15-24 18:19]: * mh@mike.franken.de
[03-15-24 17:58]: On Freitag, 15. März 2024 22:34:14 CET Patrick Shanahan wrote:
* Patrick Shanahan
[03-14-24 16:14]: * phanisvara das
[03-14-24 15:56]: On Thursday 14 March 2024 08:51:03 PM (+01:00), mh@mike.franken.de
wrote: [...]
> > 4. custom shortcuts were gone > > Correction: They exist, but do not work.
my custom shortcuts were also saved but not active. after creating new shortcuts they do work.>
I deleted and recreated several but they do not work :(
I restarted plasma but did not help
fwiw: after the fourth reboot, my *recreated* snapshots work. and those subsequently created also.
Did you try with plasma 6.0.1 or 6.0.2?
both
With 6.0.1 newly created snapshots worked for me. With 6.0.2 nothing at all works - neither existing nor newly created ones. Especially for bash or perl scripts really crazy named desktop files are created. If you use something like $HOME, the complete directory tree to the script is copied to ~/.local/share/applications.
I use xset for screen blanker
#! /bin/bash sleep .3 ; xset dpms force off
and it works fine. note: sleep necessary to delay action until keyboard is clear.
but I have not tried using variables for command address, only full path.
guess I very poorly explained. I have a script in ~/bin which I have set as a "script" to use Ctrl+Shift+X
and it works with plasma 6.0.2
Ok, so I spent an afternoon to test each and everything regarding shortcuts. Thats what I found out (not sure, though, if it completely correct): - The interface for custom shortcuts is ugly for both handling and optics. - Not only *some* shortcuts didn't work, but also *some* desktop "links to application". - .desktop files (belonging to both desktop icons and shortcuts) with links to shell scripts or binaries worked as expected, if they didn't need parameters; that's not true for all, but most parameters. I didn't find out, which parameters worked and which one didn't. - .desktop files linking to script files for other interpreters like perl never worked. So I wrote a starter shell script for all of my shortcuts and desktop icons. You can create links for the appropriate script or program with all the necessary parameters. These script links can be used for shortcuts or desktop icons as "application". ---------------------< snip >------------------ #!/bin/bash my_base=$( dirname $0 ) my_name=$( basename $0 ) ACTION="$1" declare -A APPSTART # some examples APPSTART["appstart-kcminit.sh"]="/usr/bin/kcminit /usr/lib64/qt5/plugins/ plasma/kcminit/kcm_mouse_init.so" APPSTART["appstart-pbpswitchusb.sh"]="monitor_pbp_switch -m U4924DW -a switchusb" APPSTART["appstart-pbpswitchboth.sh"]="monitor_pbp_switch -m U4924DW -a switchboth" APPSTART["appstart-pbpreset.sh"]="monitor_pbp_switch -m U4924DW -a reset" APPSTART["appstart-firefox.sh"]="firefox" APPSTART["appstart-calc.sh"]="kcalc" APPSTART["appstart-gvim.sh"]="gvim" APPSTART["appstart-plasmashell_restart.sh"]="plasmashell_restart" if test "$my_name" = "appstart"; then case "$ACTION" in mklink) for _appstart in "${!APPSTART[@]}" do _t="${my_base}/${_appstart}" test -L "${_t}.sh" \ || ln -s "${my_base}/${my_name}" "$_t" done ;; rmlink) for _appstart in "${!APPSTART[@]}" do _t="${my_base}/${_appstart}" test -L "$_t" && rm -f "$_t" done ;; esac else _run="${APPSTART[$my_name]}" if test -n "$_run"; then echo "running ${_run}" $_run & fi fi ---------------------< snip >------------------ Bye. Michael.