Maybe half that time.

Do the top 1% have more or less than 30% of the total wealth?

It’s around one in two million.

Believe it. Of the eligible electorate, 20% cast a vote for Labour, who wound up with two thirds of the House.

Netware was rock solid.

Led By Donkeys is about five years old. I don’t think that in that period there was a non-Tory government for them to mock, was there?

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.

Okay, that agent process is running but it looks wedged: multiple connections to the socket seem to be opened, probably your other attempts to use ssh.

The ssh-add output looks like it’s responding a bit, however.

I’d use your package manager to work out what owns it and go looking for open bugs in the tool.

(Getting a trace of that process itself would be handy, while you’re trying again. There may be a clue in its behaviour.)

The server reaponse seems like the handshake process is close to completing. It’s not immediately clear what’s up there I’m afraid.

Please don’t ignore the advice about SSH_AGENT_SOCK. It’ll tell yoy what’s going on (but not why).

Without the ssh-agent invocation:

• what does ssh-add -L show?
• what is the original SSH_AUTH_SOCK value?
• what is listening to that? (Use lsof)

This kind of stuff often happens because there’s a ton of terrible advice online about managing ssh-agent - make sure there’s none if that baked into your shellrc.

It’s a real pity they’ve ruled out the major course that could help rectify this.

I don’t doubt that the parliamentary committee on ethics is looking at it.

The killer application for Twitter is leaving a forwarding address to mastodon.

“The” catalyst is massively oversimplifying. I approve of the policy she’s attaching to this, but it seems something like a disingenuous rhetorical trick.

There are no excuses for racist violence.

On “they wpuld have voted reform anyway”: that’s not necessarily true. There’s a floating protest vote slice of “none of these fuckers” - a chunk of whom latched onto the LibDems back in 2010.

What happened in this election is that Reform split the racist vote that’s been stoked up because of the continual messaging conflating asylum-seeking and human trafficking.

That [Reform’s poor seat count] isn’t because of a politically-savvy voting public. It’s because we’ve got a shit voting system.

It’s a pity the recall provision requires censure rather than just not turning up for 14 days.