You are not logged in.
Pages: 1
Hello,
Returning Arch User (2016 I believe was my last visit, erk!)
Setting up a new system, up and running on latest Plasma. Everything installed and working great, except...
I cannot get
$SSH_AUTH_SOCKset correctly; is returning empty at the moment. KeepassXC shows the same in the settings page. The goal is to use KeepassXC to manage adding and removing keys.
ssh-agentshows the various values as described on the wiki when run, with the variable supposedly set as a result.
ssh-agent is running as a user service,
systemctl status --user ssh-agent.
Help and pointers welcomed to get this resolved, thanks in advance.
Last edited by joshaspinall (2025-09-07 10:15:43)
Offline
How do you start plasma?
Though apparently the environment does systematically not get imported from the user service and you'll have to export it yourself.
https://wiki.archlinux.org/title/SSH_ke … stemd_user
Offline
How do you start plasma?
Currently starting KDE as recommended; a lightly themed SDDM setup as per the Wiki.
User level services via systemd are a new beast for me. With your pointer, I made the following changes:
Enable the user service (properly) with
systemctl enable --user ssh-agentAs using KDE, set the environment variable by adding (as per this section)
export SSH_AUTH_SOCK=$XDG_RUNTIME_DIR/ssh-agent.socketto
/home/$USER/.config/plasma-workspace/env/exports.shNot forgetting to also allow execution by applying
chmod +x exports.shto the file as well. KeepassXC is happy in the settings page and console
echo $SSH_AUTH_SOCKnow shows the variable correctly set.
This solution has so far survived a reboot. Thanks for your input; always great to resolve an issue and (somewhat) understand the solution! ![]()
Last edited by joshaspinall (2025-09-18 13:01:28)
Offline
Pages: 1