From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.bugs Subject: bug#28596: 26.0.60; [Gnus] Checking mail is no longer reliable and C-g no longer quits Date: Fri, 22 Dec 2017 15:43:15 +0200 Message-ID: <834loinaj0.fsf@gnu.org> References: <87k20mq0uq.fsf@moondust.localdomain> <83tvzl98fe.fsf@gnu.org> <87efqppm4p.fsf@ericabrahamsen.net> <87bmlt76uw.fsf@moondust.localdomain> <831skd110u.fsf@gnu.org> <87wp22xvn8.fsf@moondust.localdomain> <83bmjextpg.fsf@gnu.org> Reply-To: Eli Zaretskii NNTP-Posting-Host: blaine.gmane.org X-Trace: blaine.gmane.org 1513950138 5015 195.159.176.226 (22 Dec 2017 13:42:18 GMT) X-Complaints-To: usenet@blaine.gmane.org NNTP-Posting-Date: Fri, 22 Dec 2017 13:42:18 +0000 (UTC) Cc: eric@ericabrahamsen.net, nljlistbox2@gmail.com, 28596@debbugs.gnu.org To: larsi@gnus.org Original-X-From: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Fri Dec 22 14:42:13 2017 Return-path: Envelope-to: geb-bug-gnu-emacs@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by blaine.gmane.org with esmtp (Exim 4.84_2) (envelope-from ) id 1eSNaW-0000qD-NS for geb-bug-gnu-emacs@m.gmane.org; Fri, 22 Dec 2017 14:42:12 +0100 Original-Received: from localhost ([::1]:51081 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1eSNcV-00059j-1b for geb-bug-gnu-emacs@m.gmane.org; Fri, 22 Dec 2017 08:44:15 -0500 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:45868) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1eSNcL-000585-4b for bug-gnu-emacs@gnu.org; Fri, 22 Dec 2017 08:44:06 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1eSNcI-0001V7-0D for bug-gnu-emacs@gnu.org; Fri, 22 Dec 2017 08:44:05 -0500 Original-Received: from debbugs.gnu.org ([208.118.235.43]:38361) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1eSNcH-0001V2-TD for bug-gnu-emacs@gnu.org; Fri, 22 Dec 2017 08:44:01 -0500 Original-Received: from Debian-debbugs by debbugs.gnu.org with local (Exim 4.84_2) (envelope-from ) id 1eSNcH-0003tk-NA for bug-gnu-emacs@gnu.org; Fri, 22 Dec 2017 08:44:01 -0500 X-Loop: help-debbugs@gnu.org Resent-From: Eli Zaretskii Original-Sender: "Debbugs-submit" Resent-CC: bug-gnu-emacs@gnu.org Resent-Date: Fri, 22 Dec 2017 13:44:01 +0000 Resent-Message-ID: Resent-Sender: help-debbugs@gnu.org X-GNU-PR-Message: followup 28596 X-GNU-PR-Package: emacs X-GNU-PR-Keywords: Original-Received: via spool by 28596-submit@debbugs.gnu.org id=B28596.151395020614935 (code B ref 28596); Fri, 22 Dec 2017 13:44:01 +0000 Original-Received: (at 28596) by debbugs.gnu.org; 22 Dec 2017 13:43:26 +0000 Original-Received: from localhost ([127.0.0.1]:47042 helo=debbugs.gnu.org) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1eSNbi-0003sp-HG for submit@debbugs.gnu.org; Fri, 22 Dec 2017 08:43:26 -0500 Original-Received: from eggs.gnu.org ([208.118.235.92]:54223) by debbugs.gnu.org with esmtp (Exim 4.84_2) (envelope-from ) id 1eSNbh-0003sc-1b for 28596@debbugs.gnu.org; Fri, 22 Dec 2017 08:43:25 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1eSNbY-0000s4-QP for 28596@debbugs.gnu.org; Fri, 22 Dec 2017 08:43:20 -0500 Original-Received: from fencepost.gnu.org ([2001:4830:134:3::e]:54014) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1eSNbY-0000rw-MS; Fri, 22 Dec 2017 08:43:16 -0500 Original-Received: from [176.228.60.248] (port=2077 helo=home-c4e4a596f7) by fencepost.gnu.org with esmtpsa (TLS1.2:RSA_AES_256_CBC_SHA1:256) (Exim 4.82) (envelope-from ) id 1eSNbY-0001jL-4H; Fri, 22 Dec 2017 08:43:16 -0500 In-reply-to: <83bmjextpg.fsf@gnu.org> (message from Eli Zaretskii on Mon, 04 Dec 2017 19:56:43 +0200) X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] X-BeenThere: debbugs-submit@debbugs.gnu.org X-Mailman-Version: 2.1.18 Precedence: list X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] X-Received-From: 208.118.235.43 X-BeenThere: bug-gnu-emacs@gnu.org List-Id: "Bug reports for GNU Emacs, the Swiss army knife of text editors" List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: bug-gnu-emacs-bounces+geb-bug-gnu-emacs=m.gmane.org@gnu.org Original-Sender: "bug-gnu-emacs" Xref: news.gmane.org gmane.emacs.bugs:141375 Archived-At: Ping! > Date: Mon, 04 Dec 2017 19:56:43 +0200 > From: Eli Zaretskii > Cc: eric@ericabrahamsen.net, 28596@debbugs.gnu.org > > > From: nljlistbox2@gmail.com (N. Jackson) > > Cc: eric@ericabrahamsen.net, 28596@debbugs.gnu.org > > Date: Mon, 04 Dec 2017 12:14:51 -0500 > > > > Hello Eli, > > > > At 19:40 +0200 on Saturday 2017-12-02, Eli Zaretskii wrote: > > > > > > Any news on this? Is this problem still present in the Emacs > > > 26.0.90 pretest? > > > > Yes, the problem is still present with the 26.0.90 pretest. I ran > > that for three weeks and the problem happened almost every day. > > > > Then I went back to using Emacs 25 out of frustration. > > > > No, sorry, no news. I wasn't able to get any traction on debugging > > it; that would be so much easier if the code were in C! (I am > > perennially unsuccessful when I try to get the Elisp debugger to > > function the way I think it ought to, probably because I don't > > understand the way it is supposed to work.) > > > > However, I had forgotten (or never saw) your suggestions to > > > > "try setting url-asynchronous to nil when fetching news... [o]r > > maybe even build Emacs with HAVE_GETADDRINFO_A undefined" > > > > and I will try that with 26.0.90 these next days. > > > > Additionally, I am almost convinced that the problem is that Gnus > > gets into an ambiguous state where part of it thinks it is > > "unplugged" and part of it thinks it's "plugged", and that it > > never even tries to retrieve the news in the cases where it seems > > to be "broken". > > > > Furthermore, I now believe that the hang that I had been observing > > was just Bug 16026 / Bug 16906 and that I failed to recognise it > > because I was too confused by the strange behaviour resulting from > > this current bug. > > Lars, can you help us here? I'd hate to release Emacs 26.1 with this > annoying problem. Can we do something to have a solution or at least > a reasonably convenient band-aid? > > Thanks.