GNU bug report logs - #25060
gnutls: asynchronous spurious "fatal error"

Previous Next

Package: emacs;

Reported by: Andy Wingo <wingo <at> igalia.com>

Date: Tue, 29 Nov 2016 10:11:02 UTC

Severity: normal

Tags: fixed

Merged with 25059

Found in version 24.5

Done: Lars Ingebrigtsen <larsi <at> gnus.org>

Bug is archived. No further changes may be made.

Full log


Message #10 received at 25060 <at> debbugs.gnu.org (full text, mbox):

From: Ted Zlatanov <tzz <at> lifelogs.com>
To: Andy Wingo <wingo <at> igalia.com>
Cc: 25060 <at> debbugs.gnu.org
Subject: Re: bug#25060: gnutls: asynchronous spurious "fatal error"
Date: Thu, 01 Dec 2016 13:35:08 -0500
On Tue, 29 Nov 2016 11:10:17 +0100 Andy Wingo <wingo <at> igalia.com> wrote: 

AW>     gnutls.c: [1] (Emacs) non-fatal error: Resource temporarily unavailable, try again. [3088 times]
AW>     gnutls.c: [2] received curve SECP256R1
AW>     gnutls.c: [1] (Emacs) non-fatal error: Resource temporarily unavailable, try again. [2816 times]
AW>     #<buffer  *http www.gnu.org:443*-346477>
AW>     gnutls.c: [1] (Emacs) non-fatal error: Resource temporarily unavailable, try again. [5 times]
AW>     success
...
AW> No idea what that non-fatal error appearing thousands of times is, I
AW> suspect Emacs is polling on a non-blocking file descriptor or
AW> something.  Anyway this error appears to not affect anything as it's
AW> asynchronous and it is not handleable by anything, and just makes people
AW> think they have problems :)  Can you make it go away?

I think that's reasonable for that one specific message. But could it be
in fact indicating a real problem at the C level? I don't want to
silence it then.

Ted




This bug report was last modified 8 years and 171 days ago.

Previous Next


GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.