>
> egreshko 1595 1483 0 00:21 ?00:00:00 /usr/bin/ssh-agent /bin/sh -c
> exec -l
> /bin/bash -c "/usr/bin/startlxde"
>
> and the environment variables are set accordingly.
>
> SSH_AGENT_PID=1595
> SSH_AUTH_SOCK=/tmp/ssh-CQUbfzKj1483/agent.1483
> SSH_ASKPASS=/usr/libexec/openssh/gnom
On 04/08/2012 12:12 AM, Ranjan Maitra wrote:
> On Sun, 8 Apr 2012 00:05:50 +0800 Ed Greshko
> wrote:
>
>> On 04/07/2012 11:53 PM, Ed Greshko wrote:
>>> So, it had started previously under lxde?
>> FWIW, I just group installed LXDE on a VM and ssh-agent started OK when I
>> logged in.
>>
> OK, the
On Sun, 8 Apr 2012 00:05:50 +0800 Ed Greshko
wrote:
> On 04/07/2012 11:53 PM, Ed Greshko wrote:
> > So, it had started previously under lxde?
>
> FWIW, I just group installed LXDE on a VM and ssh-agent started OK when I
> logged in.
>
OK, then it is me perhaps. But I did nothing out of the or
On Sat, 7 Apr 2012 23:53:12 +0800 Ed Greshko
wrote:
> On 04/07/2012 11:33 PM, Ranjan Maitra wrote:
> > This has always been the case from when I used fvwm, xfce and (now) lxde.
>
> So, it had started previously under lxde?
Yes, until last night's updates (which may not have been relevant).
>
On 04/07/2012 11:53 PM, Ed Greshko wrote:
> So, it had started previously under lxde?
FWIW, I just group installed LXDE on a VM and ssh-agent started OK when I
logged in.
--
Never be afraid to laugh at yourself, after all, you could be missing out on
the joke
of the century. -- Dame Edna Evera
On 04/07/2012 11:33 PM, Ranjan Maitra wrote:
> This has always been the case from when I used fvwm, xfce and (now) lxde.
So, it had started previously under lxde?
>> So Does it get started again when you logout/login?
> No. Do I use systemd on this? But again, I have never had to do this,
>
On Sat, 7 Apr 2012 23:28:05 +0800 Ed Greshko
wrote:
> On 04/07/2012 11:10 PM, Ranjan Maitra wrote:
> >> It means /usr/bin/ssh-agent isn't running.
> > But why did it suddenly stop?
>
> Are you sure it even started? (See below)
In the past, it has always started.
> >> >
> >> > How are y
On 04/07/2012 11:10 PM, Ranjan Maitra wrote:
>> It means /usr/bin/ssh-agent isn't running.
> But why did it suddenly stop?
Are you sure it even started? (See below)
>
>> >
>> > How are you logging in?
> The usual way: type password in lxdm. Is this what you were asking?
I asked because it
On Sat, 7 Apr 2012 15:24:22 +0800 Ed Greshko
wrote:
> On 04/07/2012 03:01 PM, Ranjan Maitra wrote:
> > Dear friends,
> >
> > Just updated to the latest kernel 3.3.1 and rebooted and tried to get
> > everything going but I get:
> >
> > $ ssh-add
> > Could not open a connection to your authenticati
On 04/07/2012 03:01 PM, Ranjan Maitra wrote:
> Dear friends,
>
> Just updated to the latest kernel 3.3.1 and rebooted and tried to get
> everything going but I get:
>
> $ ssh-add
> Could not open a connection to your authentication agent.
> $
>
> What is this supposed to mean? This is perhaps the f
Dear friends,
Just updated to the latest kernel 3.3.1 and rebooted and tried to get
everything going but I get:
$ ssh-add
Could not open a connection to your authentication agent.
$
What is this supposed to mean? This is perhaps the first time I have
seen this error in almost 15 years on linux.
11 matches
Mail list logo
