From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.io/gmane.emacs.gnus.user/4983 Path: news.gmane.org!not-for-mail From: "Bruno Hertz" Newsgroups: gmane.emacs.gnus.user Subject: Re: Slashdot RSS feed. Date: Thu, 28 Apr 2005 02:25:44 +0200 Organization: Cablecom Newsserver Message-ID: References: <87u0lrzwj1.fsf@robotron.ath.cx> NNTP-Posting-Host: main.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: sea.gmane.org 1138670815 25646 80.91.229.2 (31 Jan 2006 01:26:55 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Tue, 31 Jan 2006 01:26:55 +0000 (UTC) Original-X-From: nobody Tue Jan 17 17:34:36 2006 Original-Path: quimby.gnus.org!newsfeed1.e.nsc.no!news.powertech.no!news.banetele.no!tsicnews.teliasonera.com!newsfeed00.sul.t-online.de!newsfeed01.sul.t-online.de!t-online.de!newsfeed.inode.at!news.hispeed.ch!not-for-mail Original-Newsgroups: gnu.emacs.gnus Original-NNTP-Posting-Host: 80-218-17-54.dclient.hispeed.ch Original-X-Trace: news.hispeed.ch 1114647944 1889 80.218.17.54 (28 Apr 2005 00:25:44 GMT) Original-X-Complaints-To: news@hispeed.ch Original-NNTP-Posting-Date: Thu, 28 Apr 2005 00:25:44 +0000 (UTC) User-Agent: Gnus/5.110003 (No Gnus v0.3) Emacs/22.0.50 (gnu/linux) Cancel-Lock: sha1:JZeeqYiv4/bzIwus1P59gxM5cec= Original-Xref: bridgekeeper.physik.uni-ulm.de gnus-emacs-gnus:5124 Original-Lines: 35 X-Gnus-Article-Number: 5124 Tue Jan 17 17:34:36 2006 Xref: news.gmane.org gmane.emacs.gnus.user:4983 Archived-At: David Hansen 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.