unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: nljlistbox2@gmail.com (N. Jackson)
To: Noam Postavsky <npostavs@users.sourceforge.net>
Cc: 28596@debbugs.gnu.org
Subject: bug#28596: 26.0.60; [Gnus] Checking mail is no longer reliable and C-g no longer quits
Date: Tue, 26 Sep 2017 10:13:01 -0400	[thread overview]
Message-ID: <8760c5im4y.fsf@moondust.localdomain> (raw)
In-Reply-To: <CAM-tV-9tP_QNOiWjw-mHAm-7a2fs10qiiwqUwON1XiP6p1VubA@mail.gmail.com> (Noam Postavsky's message of "Mon, 25 Sep 2017 13:14:43 -0400")

At 13:14 -0400 on Monday 2017-09-25, Noam Postavsky wrote:
>
> Does 'pkill -SIGUSR2 emacs' help? Otherwise running under gdb and
> hitting C-z at the gdb terminal should give some more info.
>
> (elisp) Error Debugging
>
> -- User Option: debug-on-event
>      If you set ‘debug-on-event’ to a special event (*note Special
>      Events::), Emacs will try to enter the debugger as soon as it
>      receives this event, bypassing ‘special-event-map’.  At present,
>      the only supported values correspond to the signals ‘SIGUSR1’ and
>      ‘SIGUSR2’ (this is the default).  This can be helpful when
>      ‘inhibit-quit’ is set and Emacs is not otherwise responding.

Hi Noam,

Thanks for these tips.

I'm now running under GDB but so far today the long hang isn't
happening so I haven't been able to get a backtrace during it.
Nevertheless, after putting Gnus into an unplugged state and then
putting it into the plugged state while my computer was still
disconnected from the Internet, Gnus is now in a broken state even
though I now am connected.

The problem can be easily seen in the *Server* buffer. All my nntp
servers are broken. (My local servers (nnfolder, nndraft, and my
nnimap server on localhost) are fine.)

- The nntp servers that are managed by the Agent are in an
  "offline" state even though Gnus is currently plugged (and I
  have a good Internet connection), and the `O', `C' and `R'
  (open, close, and reset all) commands have not effect. (Toggling
  the plugged/unplugged state a few times hasn't changed this
  brokenness.)

- The nntp servers that are not managed by the Agent are in a
  "denied" state and the `O', `C' and `R' (open, close, and reset
  all) commands have not effect.

And when I say these commands have no effect, they have no effect
at all. No messages are written to the *Messages* buffer even
though I have gnus-verbose and gnus-verbose-backends both set to
10. [The former setting doesn't seem to do anything (hasn't for a
year or two), but the latter normally prints the dialog with the
servers.]

That is, it seems that Gnus is not even trying to talk to these
servers.

It almost seems as if, because they were found once in the Emacs
session not to be accessible, Gnus will never try to talk to them
again until Emacs is restarted, and commands in the *Server*
buffer to open, close etc. these servers are just quietly ignored.

I will report more as I find it, maybe look at the code, possibly
step through it in the debugger. But as my every day workflow is
so much effected by this I might have to go back to Emacs 25 where
these problems don't happen.

N.





  reply	other threads:[~2017-09-26 14:13 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 [this message]
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
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=8760c5im4y.fsf@moondust.localdomain \
    --to=nljlistbox2@gmail.com \
    --cc=28596@debbugs.gnu.org \
    --cc=npostavs@users.sourceforge.net \
    /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).