Houston, we have a problem.

[Christian Parpart]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

On Friday 06 September 2002 12:50 am, Ingo Klöcker inspired the electrons to 
say:
> On Friday 06 September 2002 00:13, Chris Howells wrote:
> > Hi,
> >
> > On Thursday 05 September 2002 11:13 pm, Ingo Klöcker wrote:
> > > > Also if gpg is trying to download a key from a keyserver and the
> > > > keyserver doesn't respond (or takes some time), kmail takes all
> > > > CPU. In the case of the server not responding, forever.
> > >
> > > Proposal: Use a more reliable keyserver.
> >
> > Do you really think that telling this to a user is an acceptable
> > answer?
>
> As a short time solution: Yes, absolutely.

You forgot that this may be also caused by having a slow bandwidth 
connection to the Internet. Ingo and Marc, I understand your problem, 
but don't be so indefinitely stubborn in your descission. 
I totally agree with Carsten Pfeiffer and Dirk. And, furthermore, a KMail 
blocking my system, just because my it is trying to download a PGP Signature, 
where either the key server is responding so slow or even my internet 
connection seems so, looks definitely to me to be a bug, too! Why? A Bug is 
not only something that lets a program crash, blocking/freezing and other 
unexpected behavior are bugs, too.

> > The program should surely deal with the problem, not expect the user
> > to work around it.
>
> I know all this. And I would very much like to fix all those problems.
> But unfortunately I only have so much time to work on the code. Maybe I
> should spend less time closing bogus bug reports and duplicate wishes
> and supporting KMail users. NOT!

Of course, you don't need to. You're not the only developer working on KMail.

Best Regards,
Christian Parpart.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.0.7 (GNU/Linux)

iD8DBQE9d+PdPpa2GmDVhK0RAn2/AKCKjvzG8pPXM+06FnEcCDy86QUBiACgijCd
C7ByGVwV4XTqE4/hVZf57sU=
=IpjI
-----END PGP SIGNATURE-----