https://bugs.kde.org/show_bug.cgi?id=461173
Bug ID: 461173
Summary: SSH_AUTH_SOCK is not always set in wayland sessions
Classification: Plasma
Product: ksmserver
Version: 5.26.0
Platform: Other
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: general
Assignee: k...@davidedmundson.co.uk
Reporter: p...@ralfj.de
CC: plasma-b...@kde.org
Target Milestone: ---
SUMMARY
When using Konsole in a wayland KDE session and trying to do this with SSH, I
encounter this error:
"Could not open a connection to your authentication agent."
Turns out that the SSH_AUTH_SOCK env var is not set. This used to be always set
under X11, but under Wayland that does not always seem to work. I am pretty
sure in a previous session I did have working SSH under Wayland, so maybe this
is some non-deterministic condition related to the exact order in which
services start when the session is brought up.
I can see in "systemctl --user status ssh-agent.service" that the agent is
running. In the logs I see the following
Okt 29 21:41:20 r-thinktop agent-launch[19682]:
dbus-update-activation-environment: setting
SSH_AUTH_SOCK=/run/user/1000/openssh_agent
Okt 29 21:41:20 r-thinktop agent-launch[19682]:
dbus-update-activation-environment: setting SSH_AGENT_LAUNCHER=openssh
Okt 29 21:41:20 r-thinktop agent-launch[19678]:
SSH_AUTH_SOCK=/run/user/1000/openssh_agent; export SSH_AUTH_SOCK;
so it seems that somehow those environment variables are supposed to make their
way into the session proper, and that does not seem to (always) work.
SOFTWARE/OS VERSIONS
Operating System: Debian GNU/Linux
KDE Plasma Version: 5.26.0
KDE Frameworks Version: 5.98.0
Qt Version: 5.15.6
Kernel Version: 6.0.0-2-amd64 (64-bit)
Graphics Platform: Wayland
Processors: 8 × Intel® Xeon® CPU E3-1505M v5 @ 2.80GHz
Memory: 31,2 GiB of RAM
Graphics Processor: Mesa Intel® HD Graphics P530
Manufacturer: LENOVO
Product Name: 20ENCTO1WW
System Version: ThinkPad P50
--
You are receiving this mail because:
You are watching all bug changes.
