Your message dated Mon, 6 Feb 2006 12:19:23 -0500 with message-id <[EMAIL PROTECTED]> and subject line found the problem; not xchm's fault has caused the attached Bug report to be marked as done.
This means that you claim that the problem has been dealt with. If this is not the case it is now your responsibility to reopen the Bug report if necessary, and/or fix the problem forthwith. (NB: If you are a system administrator and have no idea what I am talking about this indicates a serious mail system misconfiguration somewhere. Please contact me immediately.) Debian bug tracking system administrator (administrator, Debian Bugs database)
--- Begin Message --->From [EMAIL PROTECTED] Wed Dec 28 04:05:51 2005 Received: (at submit) by bugs.debian.org; 28 Dec 2005 12:05:51 +0000 Return-path: <[EMAIL PROTECTED]> Received: from rwcrmhc12.comcast.net ([216.148.227.152]) by spohr.debian.org with esmtp (Exim 4.50) id 1Era3z-0004WB-2X for [EMAIL PROTECTED]; Wed, 28 Dec 2005 04:05:51 -0800 Received: from helium (pcp04399275pcs.nrockv01.md.comcast.net[69.140.163.93]) by comcast.net (rwcrmhc12) with ESMTP id <20051228120520014008hiroe>; Wed, 28 Dec 2005 12:05:20 +0000 Received: from andrex by helium with local (Exim 4.60) (envelope-from <[EMAIL PROTECTED]>) id 1Era3S-0001o3-6w; Wed, 28 Dec 2005 07:05:18 -0500 Content-Type: text/plain; charset="us-ascii" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit From: Andrew Schulman <[EMAIL PROTECTED]> To: Debian Bug Tracking System <[EMAIL PROTECTED]> Subject: xchm: segfault at start Message-ID: <[EMAIL PROTECTED]> X-Mailer: reportbug 3.18 Date: Wed, 28 Dec 2005 07:05:17 -0500 Delivered-To: [EMAIL PROTECTED] X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2005_01_02 (1.212-2003-09-23-exp) on spohr.debian.org X-Spam-Level: X-Spam-Status: No, hits=-7.5 required=4.0 tests=BAYES_00,HAS_PACKAGE, RCVD_IN_SORBS autolearn=no version=2.60-bugs.debian.org_2005_01_02 Package: xchm Version: 2:1.2.0-5 Severity: important $ xchm Segmentation fault -- System Information: Debian Release: testing/unstable APT prefers testing APT policy: (990, 'testing'), (400, 'stable'), (200, 'unstable'), (1, 'experimental') Architecture: i386 (i686) Shell: /bin/sh linked to /bin/bash Kernel: Linux 2.6.14 Locale: LANG=C, LC_CTYPE=C (charmap=ANSI_X3.4-1968) Versions of packages xchm depends on: ii libc6 2.3.5-9 GNU C Library: Shared libraries an ii libchm1 0.37-2 library for dealing with Microsoft ii libgcc1 1:4.0.2-5 GCC support library ii libstdc++6 4.0.2-5 The GNU Standard C++ Library v3 ii libwxgtk2.6-0 2.6.1.2 wxWidgets Cross-platform C++ GUI t xchm recommends no packages. -- no debconf information
--- End Message ---
--- Begin Message --->From [EMAIL PROTECTED] Mon Feb 06 09:19:56 2006 Received: (at 345006-done) by bugs.debian.org; 6 Feb 2006 17:19:56 +0000 Return-path: <[EMAIL PROTECTED]> Received: from sccrmhc11.comcast.net ([63.240.77.81]) by spohr.debian.org with esmtp (Exim 4.50) id 1F6A1s-0001Uw-JA for [EMAIL PROTECTED]; Mon, 06 Feb 2006 09:19:56 -0800 Received: from c-69-140-163-93.hsd1.md.comcast.net ([69.140.163.93]) by comcast.net (sccrmhc11) with ESMTP id <200602061719250110039912e>; Mon, 6 Feb 2006 17:19:25 +0000 From: Andrew Schulman <[EMAIL PROTECTED]> To: [EMAIL PROTECTED] Subject: found the problem; not xchm's fault Date: Mon, 6 Feb 2006 12:19:23 -0500 User-Agent: KMail/1.9.1 MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Content-Disposition: inline Message-Id: <[EMAIL PROTECTED]> X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2005_01_02 (1.212-2003-09-23-exp) on spohr.debian.org X-Spam-Level: X-Spam-Status: No, hits=-2.0 required=4.0 tests=BAYES_00,RCVD_IN_SORBS autolearn=no version=2.60-bugs.debian.org_2005_01_02 I had locally installed libgdkxft, and had set LD_PRELOAD=/usr/local/lib/libgdkxft.so in my environment. With this set, xchm segfaults. When I unset it, xchm runs just fine. This also turns out (at least in my case) to be the cause of bug #328788 against kaffeine. This wasn't a bug in xchm, so I'm closing it now. Sorry for your trouble. (Note to self and maintainers: output of the 'env' command would have made this bug easy to find, and should be required in bug reports.) Andrew.
--- End Message ---
