I’m a mathematician too. They’re probably speaking from an intuitive grasp of utility.

Yeah, but still - the elephant.

The Tarot of the Bohemians.

I think it’s fairly parochial, and sounds quite infantile to me. Growing up (uk) we just used clockwise to tighten.

“I love life on Earth… but I love capitalism more.”

Bobby Fingers has the best definition of “woke,” one that I feel all can agree with, even if they are dismayed by the quality of his dashboards.

That was my, admittedly bitter, point, yes. You do have to wonder what the hell weretcollectively playing at.

We live in a world of plenty where we still produce enough food that nobody need go hungry.

It does make me wonder about quantum suicide.

The Sixth Sense.

Thank-you.

And 51 feels prime. Someone sgould write a letter.

It’s “revelation,” singular. Like trivial pursuit.

Ed Balls

FWIW I was trying to do something like this and ended up with pretty much what you describe - some custom shading to get everything working.

Netware was rock solid.

Minimise your windows one at a time and check that the gnome keyring hasn’t popped up a dialog box sonewhere behind everything else that’s asking you if it’s okay to proceed.

It’s the gnome key ring ssh agent.

It’s possible that this has popped up a window asking gor permission / a passphrase / something and you’re not seeing that.

That’s only part of the handshake. It’d require agent input around that point.

Is this problem a recurring one after a reboot?

If it is it warrants more effort.

If not and you’re happy with rhe lack of closure, you can potentially fix this: kill the old agent (watch out to see if it respawns; if it does and that works, fine). If it doesn’t, you can (a) remove the socket file (b) launch ssh-agent with the righr flag (-a $SSH_AGENT_SOCK iirc) to listen at the same place, then future terminal sessions that inherit the env var will still look in the right place. Unsatisfactory but it’ll get you going again.