Your message dated Sun, 26 Sep 2004 15:56:01 +0900
with message-id <[EMAIL PROTECTED]>
and subject line [EMAIL PROTECTED]: Re: xmms/libmikmod2 bug is grave]
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)
--------------------------------------
Received: (at submit) by bugs.debian.org; 23 Jul 2004 07:20:47 +0000
>From [EMAIL PROTECTED] Fri Jul 23 00:20:47 2004
Return-path: <[EMAIL PROTECTED]>
Received: from mail020.syd.optusnet.com.au [211.29.132.131]
by spohr.debian.org with esmtp (Exim 3.35 1 (Debian))
id 1BnuMJ-00026y-00; Fri, 23 Jul 2004 00:20:47 -0700
Received: from anticd.org (c211-30-187-243.rivrw1.nsw.optusnet.com.au [211.30.187.243])
by mail020.syd.optusnet.com.au (8.11.6p2/8.11.6) with ESMTP id i6N7KY011017
for <[EMAIL PROTECTED]>; Fri, 23 Jul 2004 17:20:41 +1000
Message-ID: <[EMAIL PROTECTED]>
Date: Fri, 23 Jul 2004 17:20:35 +1000
From: Simon Males <[EMAIL PROTECTED]>
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.6) Gecko/20040413 Debian/1.6-5
X-Accept-Language: en-us, en, fr
MIME-Version: 1.0
To: [EMAIL PROTECTED]
Subject: shared object violation with libmikmod.so.2 on kernel 2.6.6
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
Delivered-To: [EMAIL PROTECTED]
X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2004_03_25
(1.212-2003-09-23-exp) on spohr.debian.org
X-Spam-Status: No, hits=-8.0 required=4.0 tests=BAYES_00,HAS_PACKAGE
autolearn=no version=2.60-bugs.debian.org_2004_03_25
X-Spam-Level:
Package: xmms
Version: 1.2.10-1
Severity: important
When I boot into kernel-image-2.6.6-1-386 and launch xmms from the
command line I get the following error:
$ xmms
libmikmod.so.2: cannot open shared object file: No such file or directory
Inconsistency detected by ld.so: ../sysdeps/generic/dl-tls.c: 72:
_dl_next_tls_modid: Assertion `result <=
_rtld_local._dl_tls_max_dtv_idx' failed!
Booting into kernel-image-2.4.25-1-386 xmms runs normally.
--
Simon Males <[EMAIL PROTECTED]>
No More AOL CDs Australia - www.anticd.org
---------------------------------------
Received: (at 261001-done) by bugs.debian.org; 26 Sep 2004 06:56:02 +0000
>From [EMAIL PROTECTED] Sat Sep 25 23:56:02 2004
Return-path: <[EMAIL PROTECTED]>
Received: from omega.webmasters.gr.jp (webmasters.gr.jp) [218.44.239.78]
by spohr.debian.org with esmtp (Exim 3.35 1 (Debian))
id 1CBSx0-0005YD-00; Sat, 25 Sep 2004 23:56:02 -0700
Received: from omega.webmasters.gr.jp (localhost [127.0.0.1])
by webmasters.gr.jp (Postfix) with ESMTP
id 28C9DDEB80; Sun, 26 Sep 2004 15:56:01 +0900 (JST)
Date: Sun, 26 Sep 2004 15:56:01 +0900
Message-ID: <[EMAIL PROTECTED]>
From: GOTO Masanori <[EMAIL PROTECTED]>
To: Pierre Machard <[EMAIL PROTECTED]>
Cc: [EMAIL PROTECTED], Eduard Bloch <[EMAIL PROTECTED]>
Subject: Re: [EMAIL PROTECTED]: Re: xmms/libmikmod2 bug is grave]
In-Reply-To: <[EMAIL PROTECTED]>
References: <[EMAIL PROTECTED]>
User-Agent: Wanderlust/2.9.9 (Unchained Melody) SEMI/1.14.3 (Ushinoya)
FLIM/1.14.3 (=?ISO-8859-4?Q?Unebigory=F2mae?=) APEL/10.3 Emacs/21.2
(i386-debian-linux-gnu) MULE/5.0 (SAKAKI)
MIME-Version: 1.0 (generated by SEMI 1.14.3 - "Ushinoya")
Content-Type: text/plain; charset=US-ASCII
Delivered-To: [EMAIL PROTECTED]
X-Spam-Checker-Version: SpamAssassin 2.60-bugs.debian.org_2004_03_25
(1.212-2003-09-23-exp) on spohr.debian.org
X-Spam-Status: No, hits=-3.0 required=4.0 tests=BAYES_00 autolearn=no
version=2.60-bugs.debian.org_2004_03_25
X-Spam-Level:
At Sat, 25 Sep 2004 18:35:42 +0200,
Pierre Machard wrote:
> > Then, for some reason, XMMS does this (not) funny thing right after
> > libGL.so.1 has been loaded.
>
> The problem is really nvidia drivers. I tryed to forward a similar bug in
> the past to the glibc maintainers but It fails. I hope it will work this
> time.
>
> Dear glibc maintainers I do not know if the severity is very well
> setted, however I would really like to know why nvidia and the behaviour
> that Eduard described break xmms.
>
> If you prefer, you can duplicate the bug repport and reassign it to
> xmms and/or nvidia.
I have no idea. nvidia drivers is non-free, so we can't look at its
source code. In addition, read #219943.
Regards,
-- gotom
--
To UNSUBSCRIBE, email to [EMAIL PROTECTED]
with a subject of "unsubscribe". Trouble? Contact [EMAIL PROTECTED]
