https://bugs.kde.org/show_bug.cgi?id=522064
Alex Ball <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- CC| |[email protected] --- Comment #2 from Alex Ball <[email protected]> --- I experienced the same issue, and I think I've worked out the cause. The file /etc/profile.d/org.kde.neon.ksshaskpass_auth_sock.sh from neon-settings-2 contains this: >if [ "$XDG_SESSION_TYPE" = "wayland" ]; then > export SSH_AUTH_SOCK="$XDG_RUNTIME_DIR/ssh-agent.socket" >fi This is loaded before /usr/lib/systemd/user/ssh-agent.service starts up. That service unit runs "/usr/lib/openssh/agent-launch start", the relevant stanza of which is this: >if [ -z "$SSH_AUTH_SOCK" ] && grep -s -q '^use-ssh-agent$' >/etc/X11/Xsession.options; then > S="$XDG_RUNTIME_DIR/openssh_agent" > dbus-update-activation-environment --verbose --systemd SSH_AUTH_SOCK="$S" > SSH_AGENT_LAUNCHER=openssh > exec ssh-agent -D -a "$S" "$@" >fi That is, ssh-agent only starts (and hence the systemd service only stays active) if the $SSH_AUTH_SOCK environment variable is blank at that point. But on a Wayland session, it is set to "$XDG_RUNTIME_DIR/ssh-agent.socket", so ssh-agent is never called and the ssh-agent.service immediately stops again when started. In my case, I commented out the lines in org.kde.neon.ksshaskpass_auth_sock.sh and ssh-agent started working again. -- You are receiving this mail because: You are watching all bug changes.
