ssh_agent vs. The New Hotness

A recent Manjaro update killed whatever magic held the passwords used for public-key ssh access from my desktop box, requiring me to remember the passords and type them correctly.

After considerable thrashing around doing what I thought I knew about ssh_agent (which, yes, was being autostarted to no avail), it seems that thread applies and the fix now requires creating /etc/profile.d/gcr-keyring.sh with this burst of line noise:

export SSH_AUTH_SOCK=$XDG_RUNTIME_DIR/gcr/ssh

Then tell systemd about it:

systemctl --user enable gcr-ssh-agent.socket
systemctl --user enable gcr-ssh-agent.service

Whereupon, after a reboot presumably causing systemd to make the right thing perform the right act at the right time, It Just Worked™.

I used to have some mild sysadmin mojo, but obviously if you don’t do it all the time, everything you think you know becomes wrong.

The WordPress AI did generate an image based on the above text and the prompt linux overlapping windows on monitor:

Which looks a lot like those stock photos filling otherwise empty space in spammy web pages, doesn’t it? In point of fact, the AI Feedback on Post had this to say:

While the AI-generated image may align with the content, consider using original or more contextually relevant visuals to maintain the professional look of the website.

Couldn’t have put it better myself. Thank you, AI image & text generators, for your help.