ssh-agent broken in Jaunty?

[Smoot Carl-Mitchell]

On Tue, 2009-06-30 at 08:56 -0500, Sean Carolan wrote:
> >> Perhaps try seahorse as a workaround?
> 
> A reboot seems to have cured this issue.  Hopefully it doesn't crop up
> again, but if it does I'll try to figure out how to reproduce it.

I noticed an earlier error message said SSH could not talk to the agent.
The agent listens on a local Unix socket in a subdirectory of /tmp.  If
you run this:

printenv | grep SSH

you will see the agent socket and the pid of the agent.  If the agent
socket got deleted or has the wrong permissions, then you will see the
cannot contact agent error.  You do not happen to have a cron job which
cleans up /tmp periodically of old and supposedly unused files or you
accidentally cleaned out /tmp of files you owned?
-- 
Smoot Carl-Mitchell
Computer Systems and
Network Consultant
smoot at tic.com
+1 480 922 7313
cell: +1 602 421 9005