From: Eric Abrahamsen <eric@ericabrahamsen.net>
To: 28596@debbugs.gnu.org
Subject: bug#28596: 26.0.60; [Gnus] Checking mail is no longer reliable and C-g no longer quits
Date: Fri, 29 Sep 2017 13:17:58 -0700 [thread overview]
Message-ID: <87zi9d6yyx.fsf@ericabrahamsen.net> (raw)
In-Reply-To: <87k20mq0uq.fsf@moondust.localdomain>
nljlistbox2@gmail.com (N. Jackson) writes:
> At 08:20 -0700 on Friday 2017-09-29, Eric Abrahamsen wrote:
>>
>> Eli Zaretskii <eliz@gnu.org> writes:
>>>
>>> Does gnus-group-get-new-news use any of the url-* functions? If
>>> so, perhaps try setting url-asynchronous to nil when fetching
>>> news, to see if that solves the problem. Or maybe even build
>>> Emacs with HAVE_GETADDRINFO_A undefined, and see if that helps.
>>
>> FWIW, I would put money on `nntp-open-connection' being the
>> culprit, specifically the call to `open-network-stream'.
>
> Eli and Eric, than you for these suggestions. I will have a look
> in these directions the next time Gnus "breaks". (I hadn't yet
> read them when I wrote the report below.)
[...]
> Debugger entered--Lisp error: (error "something.com/443 Name or service not known")
> signal(error ("something.com/443 Name or service not known"))
> nnrss-fetch("https://something.com/boards/forums/support.246/index.rss")
My suggestion was probably a red herring after all -- nnrss-fetch
does indeed end up calling url-* functions.
[...]
> However, fetching mail/news was still broken -- no hang this time,
> just nothing seeming to happen. And the *Server* buffer was messed
> up as I previously described:
No clue here, unfortunately.
next prev parent reply other threads:[~2017-09-29 20:17 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-25 15:01 bug#28596: 26.0.60; [Gnus] Checking mail is no longer reliable and C-g no longer quits N. Jackson
2017-09-25 17:03 ` N. Jackson
2017-09-25 17:14 ` Noam Postavsky
2017-09-26 14:13 ` N. Jackson
2017-09-29 9:10 ` Eli Zaretskii
2017-09-29 15:20 ` Eric Abrahamsen
2017-09-29 17:27 ` N. Jackson
2017-09-29 20:17 ` Eric Abrahamsen [this message]
2017-12-02 17:40 ` Eli Zaretskii
2017-12-04 17:14 ` N. Jackson
2017-12-04 17:56 ` Eli Zaretskii
2017-12-22 13:43 ` Eli Zaretskii
2017-12-27 21:00 ` Lars Ingebrigtsen
[not found] ` <871sjfdaql.fsf_-_@moondust.localdomain>
2017-12-28 12:07 ` bug#28596: 26.0.60; Gnus gets into an ambiguous plugged/unplugged state that prevents retrieval of news Lars Ingebrigtsen
2017-12-28 16:27 ` Eli Zaretskii
2017-12-28 16:29 ` Lars Ingebrigtsen
2017-12-28 17:54 ` Eli Zaretskii
2017-12-28 20:15 ` Lars Ingebrigtsen
2017-12-29 0:14 ` N. Jackson
2018-07-02 17:55 ` Eli Zaretskii
2018-07-03 0:19 ` N. Jackson
2018-07-04 16:50 ` Eli Zaretskii
2018-07-04 18:03 ` N. Jackson
2018-07-04 18:13 ` N. Jackson
2018-07-04 18:30 ` Eli Zaretskii
2018-07-04 18:38 ` N. Jackson
2018-07-04 18:41 ` Eli Zaretskii
2018-07-12 15:33 ` N. Jackson
2018-07-12 15:45 ` Eli Zaretskii
2019-09-27 15:25 ` Lars Ingebrigtsen
2020-07-19 15:44 ` Lars Ingebrigtsen
2018-07-04 18:30 ` Eli Zaretskii
2017-12-11 17:58 ` bug#28596: " N. Jackson
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87zi9d6yyx.fsf@ericabrahamsen.net \
--to=eric@ericabrahamsen.net \
--cc=28596@debbugs.gnu.org \
/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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).