From: "Bruno Hertz" <brrhtz@y4h00d0td3.invalid>
Subject: Re: Slashdot RSS feed.
Date: Thu, 28 Apr 2005 02:25:44 +0200 [thread overview]
Message-ID: <m3zmvjhhmf.fsf@caruso.quasi.local> (raw)
In-Reply-To: <87u0lrzwj1.fsf@robotron.ath.cx>
David Hansen <david.hansen@gmx.net> writes:
> On Tue, 26 Apr 2005 21:22:07 +0200 Bruno Hertz wrote:
>
>> Anybody else having problems with the Slashdot RSS feed
>> http://slashdot.org/rss/index.rss
>> today?
>>
>> nnrss hangs with message "Saw end of trailers" and consumes almost
>> 100% CPU here.
>>
>> Happened just this afternoon. Their feed broke at some point, even
>> Firefox reported an error, but then they somehow fixed it. At least
>> for Firefox it's OK again.
>>
>> In Emacs still no luck though (No Gnus v0.3).
>
> Do M-x toggle-debug-on-quit RET and then try to abort with C-g
> and send the backtrace to the gnus developer list (M-x gnus-bug
> RET should be fine).
Thanks David
I did some investigation myself already, posted the details to
gnus.ding without getting response and finally fixed it myself.
As it turned out, a temporarily bad Slashdot feed apparently hosed
News/rss/Slashdot.el, and nnrss (or whatever) couldn't cope with that.
Cleaning out the cruft in News/rss/nnrss.el (which has a tendency to
accumulate it btw., e.g. killing a nnrss group doesn't remove the feed
from that file) and moving Slashdot.el out of the way made Gnus happy
again.
Regards, Bruno.
prev parent reply other threads:[~2005-04-28 0:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-26 19:22 Bruno Hertz
2005-04-27 22:26 ` David Hansen
2005-04-28 0:25 ` Bruno Hertz [this message]
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=m3zmvjhhmf.fsf@caruso.quasi.local \
--to=brrhtz@y4h00d0td3.invalid \
/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).