Gnus development mailing list
 help / color / mirror / Atom feed
From: Xavier Maillard <zedek@gnu-rox.org>
Subject: [BUG]: Gnus randomly refuse to fetch and display articles
Date: Mon, 11 Oct 2004 13:25:19 +0200	[thread overview]
Message-ID: <plop87d5zpxzs0.fsf@gnu-rox.org> (raw)

Hello,

New problem I have since 2 or 3 days now.

Sometimes for an unknown reason, I get this backtrace when trying
to display an article:

,----
| Debugger entered--Lisp error: (error "Server closed connection")
|   signal(error ("Server closed connection"))
|   error("Server closed connection")
|   apply(error "Server closed connection")
|   nntp-report("Server closed connection")
|   nntp-accept-process-output(nil)
|   byte-code("\b	=ƒ%
|   gnus-async-wait-for-article(15716)
|   gnus-async-request-fetched-article("nntp+gnu-rox.org:gnus.ding" 15716 #<buffer *Article*>)
|   gnus-request-article-this-buffer(15716 "nntp+gnu-rox.org:gnus.ding")
|   gnus-article-prepare(15716 nil)
|   gnus-summary-display-article(15716 nil)
|   gnus-summary-select-article(nil nil pseudo)
|   gnus-summary-scroll-up(1)
|   call-interactively(gnus-summary-scroll-up)
`----

It doesn't happen every time but in a random fashion. I can for
example read 10 articles in a row and then, Gnus refuse to
display one. Dunno what can cause this to happen since I have
this behavior when plugged or not.

Regards
-- 
Xavier MAILLARD (GnuPG: 1024D/1E028EA5)
EmacsOS user (http://emacsfr.org)
APRIL (http://www.april.org)




             reply	other threads:[~2004-10-11 11:25 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-10-11 11:25 Xavier Maillard [this message]
2004-10-11 22:35 ` Xavier Maillard
2004-10-13  2:54   ` Kevin Greiner
2004-10-13  7:08     ` Xavier Maillard
2004-10-13 12:00       ` Kevin Greiner
2004-10-13 14:52         ` Xavier Maillard
2004-10-17 21:47           ` Xavier Maillard
2004-10-19 23:10             ` [SOLVED] (was: [BUG]: Gnus randomly refuse to fetch and display articles) Xavier Maillard

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=plop87d5zpxzs0.fsf@gnu-rox.org \
    --to=zedek@gnu-rox.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.
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).