From: Steinar Bang <sb@dod.no>
To: gmane-discuss@hawk.netfonds.no
Cc: ding@gnus.org
Subject: Re: Problems entering gmane groups with git gnus
Date: Fri, 14 Feb 2014 16:09:09 +0100 [thread overview]
Message-ID: <871tz5n33e.fsf@dod.no> (raw)
In-Reply-To: <87txe8om7s.fsf@flea.lifelogs.com>
>>>>> Ted Zlatanov <tzz@lifelogs.com>:
> I don't run on W32 so I can't confirm this, but please check that the
> installed GnuTLS version is the latest before anything else.
Now I've seen this on a Win8 Asus X301A laptop, that so far have eluded
being linux-ified (it starts booting the PXE install, then just stops
and skips out and continues with Win8 boot, but that's another
story...).
GNU Emacs 24.3.1 (i386-mingw-nt6.2.9200) of 2013-03-17 on MARVIN
gnutls-3.0.9-w32-bin.zip (from http://sourceforge.net/projects/ezwinports/files/)
What happened here was quite strange. When I tried entering
gmane.discuss on news.gmane.org, It failed, and I got the following
messages in the minibuffer:
Opening nntp server on news.gmane.org...done
gnutls.c: [0] (Emacs) fatal error: The TLS connection was non-properly terminated. [2 times]
apply: Server closed connection
Then I did
(setq gnutls-log-level 1)
in the scratch buffer, and tried entering gmane.discuss, and this time
it worked.
So I don't know how reproducible this is. Here are the Messages buffer
content resulting from entering gmane.discuss:
Opening nntp server on news.gmane.org...
gnutls.c: [1] (Emacs) allocating credentials
gnutls.c: [1] (Emacs) gnutls callbacks
gnutls.c: [1] (Emacs) gnutls_init
gnutls.c: [1] (Emacs) got non-default priority string: NORMAL
gnutls.c: [1] (Emacs) setting the priority string
news.gmane.org certificate could not be verified.
gnutls.c: [1] (Emacs) certificate signer was not found: news.gmane.org
gnutls.c: [1] (Emacs) certificate validation failed: news.gmane.org
Opening nntp server on news.gmane.org...done
Seems like this wasn't the culprit at all? Just a warning?
> If it still fails, open an Emacs bug or hop onto an existing one.
> There were some gnutls.c changes recently by Paul Eggert that could
> have caused this. My changes for certificate validation are less
> likely to affect only Windows, but still possible. Ideally you could
> do some kind of test bisection and tell us which commit broke your
> setup.
If I can get something really reproducible, I will try a bisect.
next prev parent reply other threads:[~2014-02-14 15:09 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-22 14:02 Steinar Bang
2013-12-14 17:04 ` Lars Magne Ingebrigtsen
2013-12-14 22:25 ` Steinar Bang
2013-12-15 3:13 ` Lars Magne Ingebrigtsen
2013-12-15 9:27 ` Steinar Bang
2013-12-16 15:21 ` Ted Zlatanov
2014-02-14 15:09 ` Steinar Bang [this message]
2014-02-16 15:36 ` Steinar Bang
2014-02-17 14:47 ` Ted Zlatanov
2014-02-17 17:55 ` Steinar Bang
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=871tz5n33e.fsf@dod.no \
--to=sb@dod.no \
--cc=ding@gnus.org \
--cc=gmane-discuss@hawk.netfonds.no \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).