https://bugs.kde.org/show_bug.cgi?id=461280
--- Comment #9 from pditc...@gmail.com --- Precisely, the binary is in ~/.local/bin , which is in PATH. As commented here: https://stackoverflow.com/questions/60977834/systemd-user-service-exec-command-not-in-path , systemd does not reslove PATH by default (if the info in the thread is correct). And as per the Arch Wiki: https://wiki.archlinux.org/title/systemd/User#PATH PATH can be substituted for systemd in .bash_profile via `systemctl --user import-environment PATH` (which will affect units started after that point. IDK about the autostart ones). So I might file a bug upstream, but initially it seems to be expected behavior. -- You are receiving this mail because: You are watching all bug changes.
