SUMMARY killing an app that gets started with a defined shortcut kills the whole plasma session the actual script used called - ~/foo.sh " #!/bin/bash trap "exit" INT TERM ERR trap "{ kill 0; }" EXIT sleep 1000 & wait " STEPS TO REPRODUCE 1. define a shortcut - Add new -> "Command and Script", as command set ~/foo.sh and define a keyboard shortcut 2. activate the command by pressing the keyboard shortcut 3. open a konsole window and run - killall foo.sh OBSERVED RESULT the whole /usr/bin/startplasma-x11 session gets killed EXPECTED RESULT the script should get killed, the /usr/bin/startplasma-x11 session should be unaffected SOFTWARE/OS VERSIONS Operating System: Gentoo Linux 2.15 KDE Plasma Version: 6.0.5 KDE Frameworks Version: 6.2.0 Qt Version: 6.7.0 Kernel Version: 6.9.1 (64-bit) Graphics Platform: X11 Memory: 38.8 GiB of RAM Graphics Processor: Mesa Intel® UHD Graphics 620 ADDITIONAL INFORMATION
the whole plasma session also gets killed, when wayland is used instead of x11
ping
krunner is also effected, after starting the script and killing it from a shell, krunner is gone and some shortcuts don't work anymore until kde is restarted
Created attachment 170049 [details] script to reproduce the bug
What is this script *supposed to* do?
(In reply to Nate Graham from comment #5) > What is this script *supposed to* do? it's an example script that triggers the bugs. the "kill 0" that should kill all child processes (of the script) kills the whole kde session
was it possible to reproduce the bug?
Nope, my Plasma Wayland session failed to die after I killed that script from Konsole following launching it via a global shortcut.
did you make sure that the script is actuall running? what does "ps aux|grep foo.sh" show? could someone else please try to reproduce the bug? It kill my x11/plasma session each time i kill the script, which i started with a global shortcut, from a konsole session.
Yes, I made sure it was actually running. This is like the opposite of Bug 473702. Very strange.