Runit with KDE Plasma: krunner current working directory /

Martin Steigerwald martin at
Fri Feb 10 13:39:58 GMT 2023


This puzzled me for a long time and I have no idea where to report this:

…proc# ls -ld $(pidof krunner)/cwd
lrwxrwxrwx 1 USER USER 0 10. Feb 14:26 15116/cwd -> /
…proc# ls -ld $(pidof plasmashell)/cwd
lrwxrwxrwx 1 USER USER 0 10. Feb 14:27 9191/cwd -> /home/USER

This is with /bin/sh pointing to Dash, the user shell is Z-Shell, but I 
have also seen this on systems where the user shell is Bash. No 
usrmerge. (I hope to avoid it as long as possible.)

According to pstree krunner's parent process is runit which of course 
has current working directory pointing to /.

Plasmashell instead is going like this



I bet through SDDM its working directory is set to the actual home 
directory of the user.

Is this a bug with runit? Is this an upstream bug?

Any idea how to find the root cause for this and determine what needs to 
be fixed?

I tried to work around this by doing "cd $HOME" in my zshrc. However 
this makes open new tabs in Konsole always start at $HOME even when I 
open them with a tab active which has a different cwd. Yeah, I got only 
do "cd $HOME" if current working directory is /, but I'd rather see this 
fixed. However, I do not even know where to report this issue.

Any insight greatly appreciated.


More information about the Debian-init-diversity mailing list