Since I'm using AppArmor, I can't use the default environment provided by my Plasma desktop. I found out that the KDE_FORK_SLAVES variable can be set[1] to help with confining GUI user apps in AA profiles by changing how the processes are executed. They say[2] this should be done via the `$HOME/.config/plasma-workspace/env/` dir by placing in it some file like `env.sh` with the following content:

Code: Select all

[ -z "$KDE_FORK_SLAVES" ] && KDE_FORK_SLAVES=1 && export KDE_FORK_SLAVES

I did so, and then I restarted the GUI session (Xserver), and after logging in it looks like nothing has changed compared to previous setup.

I can see that the variable is set when I start `konsole` and type the `env` command:

Code: Select all

$ env | grep KDE
KDE_FORK_SLAVES=1
KDE_FULL_SESSION=true
KDE_SESSION_UID=1000
KDE_SESSION_VERSION=5
XDG_CURRENT_DESKTOP=KDE
XDG_SESSION_DESKTOP=KDE

When the app is started via terminal, it behaves as it should. Also it doesn't matter whether the `KDE_FORK_SLAVES` is set to 0 or 1. But when I want to start the same app from the menu/launcher or from a panel shortcut, then no matter what is in the `KDE_FORK_SLAVES` variable, it doesn't work.

I also tried to set the `KDE_DEBUG` variable to 1 in the same way, but this also didn't affect anything, at least I don't know what to look for.

Does this `KDE_FORK_SLAVES` variable even work, if yes, how to set it properly?


[1]: https://userbase.kde.org/KDE_System_Adm ... _Variables
[2]: https://userbase.kde.org/Session_Enviro ... riables/en