Runit with KDE Plasma: krunner current working directory /

[Martin Steigerwald]

Lorenzo - 14.02.23, 17:59:15 CET:
> On Tue, 14 Feb 2023 16:22:50 +0100
> Martin Steigerwald <martin at lichtvoll.de> wrote:
> > > My guess is that the keyboard is somehow not linked to the graphic
> > > session (plasma session) so by starting program with keyboard
> > > combo
> > > it's parented directly to init.
> > 
> > The keyboard? Well krunner has runit as parent process. But does
> > that
> > have to do with a keyboard? You mean it could be an issue with
> > elogind?
> 
> Forget about that, was just guessing (wrong); looking at the KDE bug,
> you can try to manually change the krunner.desktop file, logout &
> restart the desktop and see if it fixes the issue
> 
> the file should be
> /usr/share/kglobalaccel/org.kde.krunner.desktop
> 
> and the offending commit[1] seems to change from direct exec to dbus
> activation
> [1]
> https://invent.kde.org/plasma/plasma-workspace/-/commit/0e575a20ef3653
> 2b5b40a40ea30f915976942477
> ---------------------------------------------------
> [Desktop Entry]
> - Exec=@CMAKE_INSTALL_PREFIX@/bin/krunner
> + Exec=dbus-send --type=method_call --dest=org.kde.krunner /App
>  org.kde.krunner.App.display
> Name=KRunner
> Name[ar]=مشغّل.ك
> Name[ast]=KRunner
> X-KDE-Wayland-Interfaces=org_kde_plasma_window_management
> 
> [Desktop Action RunClipboard]
> - Exec=krunner -c
> + Exec=dbus-send --type=method_call --dest=org.kde.krunner /App
> org.kde.krunner.App.displayWithClipboardContents
> Name=Run command on clipboard contents
> Name[az]=Əmri, mübadilə b
> ----------------------------------------
> 
> basically respectively use
> Exec=/usr/bin/krunner
> and
> Exec=krunner -c
> 
> if it works you can install a diversion on that file

Now I am seriously confused, cause I do have:

% grep -B 1 Exec= /usr/share/kglobalaccel/org.kde.krunner.desktop
[Desktop Entry]
Exec=/usr/bin/krunner
--
[Desktop Action RunClipboard]
Exec=krunner -c

The file is in package plasma-workspace 4:5.26.90-1.

Maybe it works the other way around, i.e. with DBUS activation? Actually 
if I read above commit diff, then it is exactly that. -krunner +DBUS 
activitation if I read the patch correctly.

Will try.

> > > Not sure if this is a bug in KDE, elogind or we are missing some
> > > systemd features (user-session, cgroups?).
> > 
> > What would you suggest to find out?
> 
> By looking at the above commit, the dbus activation is behaving
> different because (another guess) under systemd the
> 'dbus-user-session' pkg is used, while other inits are using
> 'dbus-X11' package. Dbus maintainers probably know better, but if
> that is true, what is missing is a 'runit-user' or 'sysv-user'
> integration ..
> But first please confirm if changing the .desktop files works for you

I will reply to this after I changed to DBUS activation. Maybe it helps.

Best,
-- 
Martin