We live in a world of plenty where we still produce enough food that nobody need go hungry.
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.
And 51 feels prime. Someone sgould write a letter.
It’s “revelation,” singular. Like trivial pursuit.
The beeb. Interviewees were both pro-Israeli and representatives of different Palastinian groups; what could not be distinguished between them was the playground line of blaming the other for their own behaviour.
In the days following the October attacks, the media was filled with spokespeople repeatedly delivering the line, “look what they made us do”.
It comes to the same conclusion regarding the illegality of the weapons, even if it’s pretty lenient in its interpretation of how thousands of devices can be “reasonably expected” to all end up in the hands of combatants.
Are you saying that you’re in the tribe of people who are sick of identity politics?
That’s not how legal jurisdiction works in the EU. Member states are still sovereign; if you’re liable for something in France and you get off a plane in Germany then France still needs to ask Germany nicely, and sans an extraditable conviction nothing is likely to come of it.
He’s not smart enough. More like the Grand Negus.
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).
That was my, admittedly bitter, point, yes. You do have to wonder what the hell weretcollectively playing at.