Fri, 14 Feb 2014 12:13:57 +0200 Freek de Kruijf
:
> Op vrijdag 14 februari 2014 11:47:15 schreef Yuri Chornoivan:
>> Fri, 14 Feb 2014 10:58:39 +0200 Freek de Kruijf
>>
>> :
>> > Message # 116 reads:
>> > In such cases, the only way to restore order is to kill &scdaemo
Fri, 14 Feb 2014 10:58:39 +0200 Freek de Kruijf
:
> Message # 116 reads:
> In such cases, the only way to restore order is to kill &scdaemon;,
> &dirmngr;, &gpgsm; and &gpg; processes, in that order, via the operating
> system tools (top, &Windows; Task-Manager, &etc;),
> until
>
Op vrijdag 14 februari 2014 11:47:15 schreef Yuri Chornoivan:
> Fri, 14 Feb 2014 10:58:39 +0200 Freek de Kruijf
>
> :
> > Message # 116 reads:
> > In such cases, the only way to restore order is to kill &scdaemon;,
> > &dirmngr;, &gpgsm; and &gpg; processes, in that order, via the op
Am Freitag, 14. Februar 2014, 11:47:15 schrieb Yuri Chornoivan:
> Fri, 14 Feb 2014 10:58:39 +0200 Freek de Kruijf
>
> :
> > Message # 116 reads:
> > In such cases, the only way to restore order is to kill &scdaemon;,
> > &dirmngr;, &gpgsm; and &gpg; processes, in that order, via the
Message # 116 reads:
In such cases, the only way to restore order is to kill &scdaemon;,
&dirmngr;, &gpgsm; and &gpg; processes, in that order, via the operating
system tools (top, &Windows; Task-Manager, &etc;), until
the operation get unblocked.
In my view this is something which happens in a
