Lost kgpg

[Anne Wilson]

I think this is since I updated earlier today, but I can't get kgpg to 
run as user.  It was fine last night, and there was a whole lot of kde 
updates today.  Any ideas, anyone?

Anne

[Peter Gordon]

On Thu, 2006-11-02 at 21:40 +0000, Anne Wilson wrote:
>  I think this is since I updated earlier today, but I can't get
> kgpg to 
>  run as user.  It was fine last night, and there was a whole lot of kde 
>  updates today.  Any ideas, anyone? 
If you run it in a terminal window, does it spew any abnormal diagnostic
or error messages?
-- 
Peter Gordon (codergeek42)
GnuPG Public Key ID: 0xFFC19479 / Fingerprint:
  DD68 A414 56BD 6368 D957 9666 4268 CB7A FFC1 9479
My Blog: http://thecodergeek.com/blog/

[Anne Wilson]

On Friday 03 November 2006 02:31, Peter Gordon wrote:
>  On Thu, 2006-11-02 at 21:40 +0000, Anne Wilson wrote:
>  > I think this is since I updated earlier today, but I can't get kgpg to
>  > run as user.  It was fine last night, and there was a whole lot of kde
>  > updates today.  Any ideas, anyone?
>
>  If you run it in a terminal window, does it spew any abnormal diagnostic
>  or error messages? 
No, it just hangs until I use Ctrl-C.

Anne

[Anne Wilson]

On Friday 03 November 2006 02:31, Peter Gordon wrote:
>  On Thu, 2006-11-02 at 21:40 +0000, Anne Wilson wrote:
>  > I think this is since I updated earlier today, but I can't get kgpg to
>  > run as user.  It was fine last night, and there was a whole lot of kde
>  > updates today.  Any ideas, anyone?
>
>  If you run it in a terminal window, does it spew any abnormal diagnostic
>  or error messages? 
I forgot to say that I can launch it as root from a terminal - not that it 
helps me ;-)

Anne

[Anne Wilson]

On Friday 03 November 2006 02:31, Peter Gordon wrote:
>  On Thu, 2006-11-02 at 21:40 +0000, Anne Wilson wrote:
>  > I think this is since I updated earlier today, but I can't get kgpg to
>  > run as user.  It was fine last night, and there was a whole lot of kde
>  > updates today.  Any ideas, anyone?
>
>  If you run it in a terminal window, does it spew any abnormal diagnostic
>  or error messages? 
Here's clue!  I tried 'gpg --list-keys' and got

gpg: waiting for lock (held by 6678 - probably dead) ...

So far I haven't managed to find this lockfile, though.  Any ideas?

Anne

[Gene Heskett]

On Friday 03 November 2006 10:40, Anne Wilson wrote:
> On Friday 03 November 2006 02:31, Peter Gordon wrote:
> > On Thu, 2006-11-02 at 21:40 +0000, Anne Wilson wrote:
> > > I think this is since I updated earlier today, but I can't get kgpg
> > > to run as user.  It was fine last night, and there was a whole lot of
> > > kde updates today.  Any ideas, anyone?
> >
> > If you run it in a terminal window, does it spew any abnormal
> > diagnostic or error messages?
>
> Here's clue!  I tried 'gpg --list-keys' and got
>
> gpg: waiting for lock (held by 6678 - probably dead) ...
>
> So far I haven't managed to find this lockfile, though.  Any ideas?
>  
Its not in /var/lock?

> Anne 
-- 
Cheers, Gene
"There are four boxes to be used in defense of liberty:
 soap, ballot, jury, and ammo. Please use in that order."
-Ed Howdershelt (Author)
Yahoo.com and AOL/TW attorneys please note, additions to the above
message by Gene Heskett are:
Copyright 2006 by Maurice Eugene Heskett, all rights reserved.

[Anne Wilson]

On Friday 03 November 2006 16:49, Gene Heskett wrote:
>  On Friday 03 November 2006 10:40, Anne Wilson wrote:
>  >On Friday 03 November 2006 02:31, Peter Gordon wrote:
>  >> On Thu, 2006-11-02 at 21:40 +0000, Anne Wilson wrote:
>  >> > I think this is since I updated earlier today, but I can't get kgpg
>  >> > to run as user.  It was fine last night, and there was a whole lot of
>  >> > kde updates today.  Any ideas, anyone?
>  >>
>  >> If you run it in a terminal window, does it spew any abnormal
>  >> diagnostic or error messages?
>  >
>  >Here's clue!  I tried 'gpg --list-keys' and got
>  >
>  >gpg: waiting for lock (held by 6678 - probably dead) ...
>  >
>  >So far I haven't managed to find this lockfile, though.  Any ideas?
>
>  Its not in /var/lock?
>  
No, that's the first place I looked.  If this has been there since yesterday 
it's not going to time-out, either.

Anne