Condition check in user based systemd unit causes problems

[BooneyNoobington]

On Debian based distros I observed the problem that the socket didn't come up. Using journalctl errors like this appear:

ssh-tpm-agent.service - ssh-tpm-agent service was skipped because of an unmet condition check

It might be because the regular ssh-agent is launched automatically on some distros.

Commenting out the respective lines in the user systemd unit solved the problem.

[Unit]
#ConditionEnvironment=!SSH_AGENT_PID
Description=ssh-tpm-agent service
Documentation=man:ssh-agent(1) man:ssh-add(1) man:ssh(1)
Requires=ssh-tpm-agent.socket

[Service]
Environment=SSH_TPM_AUTH_SOCK=%t/ssh-tpm-agent.sock
ExecStart=/home/MYNAME/.local/go/bin/ssh-tpm-agent
#PassEnvironment=SSH_AGENT_PID
SuccessExitStatus=2
Type=simple

[Install]
Also=ssh-agent.socket

[Foxboron]

I suspect I'll redo these service files and get a better thing going. Thanks for the report!

[BooneyNoobington]

If my report helped it would really make my day. Also: I think that ssh-tpm-agent is one of the coolest additions to the ssh ecosystem recently.