From mboxrd@z Thu Jan 1 00:00:00 1970 X-Msuck: nntp://news.gmane.io/gmane.emacs.gnus.user/5694 Path: news.gmane.org!not-for-mail From: "jmv" Newsgroups: gmane.emacs.gnus.user Subject: gnus crashes X on foreign characters Date: 19 Sep 2005 11:12:37 -0700 Organization: http://groups.google.com Message-ID: <1127153557.874872.86130@g49g2000cwa.googlegroups.com> NNTP-Posting-Host: main.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" X-Trace: sea.gmane.org 1138671372 28487 80.91.229.2 (31 Jan 2006 01:36:12 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Tue, 31 Jan 2006 01:36:12 +0000 (UTC) Original-X-From: nobody Tue Jan 17 17:35:41 2006 Original-Path: quimby.gnus.org!newsfeed.gazeta.pl!newsfeed.pionier.net.pl!news.glorb.com!postnews.google.com!g49g2000cwa.googlegroups.com!not-for-mail Original-Newsgroups: gnu.emacs.gnus Original-NNTP-Posting-Host: 129.252.11.88 Original-X-Trace: posting.google.com 1127153563 20154 127.0.0.1 (19 Sep 2005 18:12:43 GMT) Original-X-Complaints-To: groups-abuse@google.com Original-NNTP-Posting-Date: Mon, 19 Sep 2005 18:12:43 +0000 (UTC) User-Agent: G2/0.2 X-HTTP-UserAgent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.10) Gecko/20050909 Fedora/1.0.6-1.2.fc4 Firefox/1.0.6,gzip(gfe),gzip(gfe) Complaints-To: groups-abuse@google.com Injection-Info: g49g2000cwa.googlegroups.com; posting-host=129.252.11.88; posting-account=C1rJ_g0AAACNviXk1A8g6S0jLelww56R Original-Xref: bridgekeeper.physik.uni-ulm.de gnus-emacs-gnus:5836 Original-Lines: 21 X-Gnus-Article-Number: 5836 Tue Jan 17 17:35:41 2006 Xref: news.gmane.org gmane.emacs.gnus.user:5694 Archived-At: I am using Fedora Core 4 with Gnus 5.10.7 and XEmacs. Whenever I get a spam email that has foreign characters and try to show it in the Summary buffer then X crashes and takes everything down with it. The Xorg.0.log says Fatal server error: Caught signal 11. Server aborting and there are no more hints. Does anyone know how I can make Gnus stop trying to display foreign characters? BTW, it didn't crash on FC3. I guess it is a font issue. Thanks jmv