shared object violation with libmikmod.so.2 on kernel 2.6.6

Message-ID: <email address hidden>
Date: Fri, 23 Jul 2004 17:20:35 +1000
From: Simon Males <email address hidden>
To: <email address hidden>
Subject: shared object violation with libmikmod.so.2 on kernel 2.6.6

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 address hidden>
No More AOL CDs Australia - www.anticd.org

Message-ID: <email address hidden>
Date: Mon, 26 Jul 2004 11:32:05 +1000
From: Simon Males <email address hidden>
To: <email address hidden>
Subject: Re: Bug#261001: Acknowledgement (shared object violation with libmikmod.so.2
 on kernel 2.6.6)

The following is the work around, but libmikmod2 is only a recommended
package to download when use apt.

# apt-get install libmikmod2

--
Simon Males <email address hidden>
No More AOL CDs Australia - www.anticd.org

Message-ID: <email address hidden>
Date: Tue, 3 Aug 2004 20:57:26 +0200
From: Eduard Bloch <email address hidden>
To: <email address hidden>
Subject: really fucked up

severity 261001 grave
thanks

Having a such thing without real dependency should be considered RC, it
leads directly to a broken installation.

Regards,
Eduard.
--
The past tempts us, the present confuses us, the future frightens us.
And our lives slip away, moment by moment, lost in the terrible
in-between. -- Centauri Emperor, "Babylon 5 - The Coming Of Shadows"

Works fine on Warty; I tested by removing libmikmod2 and xmms still loads OK.
Looks like maybe a glibc problem

Message-ID: <20040805175059.GA10001@andromeda>
Date: Thu, 5 Aug 2004 13:50:59 -0400
From: Justin Pryzby <email address hidden>
To: <email address hidden>
Subject: xmms crash

--YiEDa0DAkWCtVeE4
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

I just purged libmikmod, and I get the "cannot open .so" message, but no
assertion failed.

Linux andromeda 2.6.7 #20 Wed Jul 7 15:31:10 EDT 2004 i686 GNU/Linux
Comments?

--=20
Justin
aptitude install iraf saods9 eclipse xpa sextractor x11iraf wcstools pyraf
http://www.justinpryzby.com/debian/

References

[1] http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=3D261001

--YiEDa0DAkWCtVeE4
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: Digital signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)

iD8DBQFBEnOCh7yD3l4ITTYRAvHSAJ9qUDEvRESVUTpQbj/5ISEQzVYCsQCgqSF3
K4KUBCOOeLgNcrK6ctlft44=
=MjHV
-----END PGP SIGNATURE-----

--YiEDa0DAkWCtVeE4--

Message-ID: <email address hidden>
Date: Fri, 20 Aug 2004 20:46:38 +0000
From: <email address hidden> (Brian M. Carlson)
To: <email address hidden>
Subject: NVidia Drivers?

-----BEGIN PGP SIGNED MESSAGE-----

Are you using NVidia drivers? If you are, then this looks like the
culprit.
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.5 (GNU/Linux)

iQEVAwUBQSZjPeWR/8lWBVPnAQFLFwf/ffie22Lhk/oJudiWW9pjQVVsvYyW1mqs
ZAYb8pS0VvKwLbJpfihJtOOQHlghVTWE3aQIu2uGs9oJXVq6lUkaOO+WVZ9xThOi
sprJSbEVztouYqYu6dX04ojZSUxK7dl248O72ZImoA6q7d/rgYnToYQG5iadwEMU
feX+QLHAANLJJqzY6gBZtaCa4areaeLSzh9fU2bjv53OkjBqj6wepkeTRNyPyCo0
BhUmTYV3/zCVAs2yRIerZsFXXheMphI+j7oeg0gVbIuaG+9wPkrswQ4ub7ueehDt
S3gNiAZxcyFyxeX8g4jaZtKsjgtDG/7LSzfYrgETJwblat4PibR3ow==
=W77S
-----END PGP SIGNATURE-----

Message-ID: <45065.157.92.49.2.1093050621.squirrel@157.92.49.2>
Date: Fri, 20 Aug 2004 22:10:21 -0300 (ART)
From: "Ricardo F. Markiewicz" <email address hidden>
To: <email address hidden>
Subject: fix libmikmod dependence

------=_20040820221021_33389
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: 8bit

tags: patch
thanks

The attached patch fix the dependence with libmikmod2 when the plugin is
compiled.

Ricardo Markiewicz
--
Linux Inside!
------=_20040820221021_33389
Content-Type: text/x-patch; name="control.patch"
Content-Transfer-Encoding: 8bit
Content-Disposition: attachment; filename="control.patch"

11c11
< Recommends: ${shlibs:Recommends}
---
> Recommends:
------=_20040820221021_33389
Content-Type: text/x-patch; name="rules.patch"
Content-Transfer-Encoding: 8bit
Content-Disposition: attachment; filename="rules.patch"

82c82,83
< -dRecommends `find $(tmp)/usr/lib/xmms -type f -name "*.so"` \
---
> `find $(tmp)/usr/lib/xmms -type f -name "*.so"` \
> # -dRecommends ""
------=_20040820221021_33389--

Message-ID: <45900.157.92.49.2.1093051432.squirrel@157.92.49.2>
Date: Fri, 20 Aug 2004 22:23:52 -0300 (ART)
From: "Ricardo F. Markiewicz" <email address hidden>
To: <email address hidden>
Subject: patch

package xmms
tags 261001 patch
thanks

i sent the patch in a previous email

Ricardo Markiewicz
--
Linux Inside!

Message-ID: <46636.157.92.49.2.1093052694.squirrel@157.92.49.2>
Date: Fri, 20 Aug 2004 22:44:54 -0300 (ART)
From: "Ricardo F. Markiewicz" <email address hidden>
To: <email address hidden>
Cc: <email address hidden>
Subject: resend :-P

tags 261001 + patch
thanks

sorry for the resend :-/

Ricardo Markiewicz
--
Linux Inside!

Message-ID: <email address hidden>
Date: Sat, 21 Aug 2004 18:11:30 +0200
From: Pierre Machard <email address hidden>
To: <email address hidden>
Cc: <email address hidden>
Subject: This bug is not grave

--/04w6evG8XlLl3ft
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

severity 261001 important
tags 261001 -patch
thanks,

Hello,

quoting xmms/README.Debian=20

[....]
The package's dependencies are somewhat complex compared to an average
package -- the dependencies of xmms proper and libxmms are in Depends:, the
dependencies of the plugins are in Recommends:. If the package management
tool of your choice doesn't support some of these dependencies, please do
not cast blame for that on the xmms package. Direct thy wrath properly ;o)

When filing bug reports against the xmms package, please pay attention to
the fact that there are several plugins that are _not_ shipped in this
package.

The fact that libmikmod2 is not installed does not prevent xmms to work.

Cheers,
--=20
                                Pierre Machard
<email address hidden> http://debian.org
GPG: 1024D/23706F87 : B906 A53F 84E0 49B6 6CF7 82C2 B3A0 2D66 2370 6F87

--/04w6evG8XlLl3ft
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: Digital signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)

iD8DBQFBJ3Qys6AtZiNwb4cRAmndAKCqHRgXlD2x0kJIb1af9E3vc2z5CwCdGRru
xCcpaOZwD++s/TSpE9oQxWA=
=RWCr
-----END PGP SIGNATURE-----

--/04w6evG8XlLl3ft--

Message-ID: <email address hidden>
Date: Sat, 18 Sep 2004 12:34:46 +0200
From: Eduard Bloch <email address hidden>
To: <email address hidden>
Cc: <email address hidden>
Subject: xmms/libmikmod2 bug is grave

--mP3DRpeJDSE+ciuQ
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline

severity 261001 grave
tags 261001 + patch
thanks

Why did you set the severity back if you did not understand the issue?
The problem here is not a plugin that breaks because of some missing
extra library (which would be okay).

> The fact that libmikmod2 is not installed does not prevent xmms to work.

Wrong. That is the core of the problem. xmms application does not start
at all. I tried to get a backtrace now, but gdb does not produce any
data, maybe it is confused with its thread model. No idea.
However, xmms starts with LD_ASSUME_KERNEL=2.4.1 and this problem may be
somehow related to TLS.

Personally, I would remove that mikmod plugin completely and replace the
Recommends: entry with xmms-modplug. Why? The plugin is crap. No control
options, no information box, not even the progress bar is working.
xmms-modplug and its library need only few kilobytes more, but provide
all those features, and better sound quality and are not crashing in
that way.

Patch to do this attached.

Regards,
Eduard.
--
"The quiet ones are the ones who change the universe.
 The loud ones only take the credit."
                                                               L.M. ItB

--mP3DRpeJDSE+ciuQ
Content-Type: text/plain; charset=us-ascii
Content-Disposition: attachment; filename="xmms.diff"

diff -u xmms-1.2.10/debian/changelog xmms-1.2.10/debian/changelog
--- xmms-1.2.10/debian/changelog
+++ xmms-1.2.10/debian/changelog
@@ -1,3 +1,11 @@
+xmms (1.2.10-1.1) unstable; urgency=low
+
+ * NMU if necessary
+ * Dropped the mikmod plugin and recommending xmms-modplug instead
+ (closes: #246601, #248008, #261931, #267306, #270623, #270984, #271811)
+
+ -- Eduard Bloch <email address hidden> Sat, 18 Sep 2004 12:12:11 +0200
+
 xmms (1.2.10-1) unstable; urgency=low

   * New upstream version,
diff -u xmms-1.2.10/debian/control xmms-1.2.10/debian/control
--- xmms-1.2.10/debian/control
+++ xmms-1.2.10/debian/control
@@ -2,7 +2,8 @@
 Section: sound
 Priority: optional
 Maintainer: Josip Rodin <email address hidden>
-Build-Depends: debhelper (>= 2), xlibs-dev, libdb3-dev, libglib1.2-dev, libgtk1.2-dev, libaudiofile-dev, libesd0-dev, libmikmod2-dev, xlibmesa-gl-dev | libgl-dev, libxml-dev, libogg-dev, libvorbis-dev (>= 1.0.0-2), gettext, libasound2-dev
+Build-Depends: debhelper (>= 2), xlibs-dev, libdb3-dev, libglib1.2-dev, libgtk1.2-dev, libaudiofile-dev, libesd0-dev, xlibmesa-gl-dev | libgl-dev, libxml-dev, libogg-dev, libvorbis-dev (>= 1.0.0-2), gettext, libasound2-dev
+Build-Conflicts: libmikmod2-dev
 Standards-Version: 3.6.1

 Package: xmms
@@ -21,9 +22,9 @@
   * Audio MPEG layer 1, 2, and 3 (with mpg123 plug-in),
   * Ogg Vorbis files (with the Ogg Vorbis plug-in),
   * CD Audio (with CDAudio plug-in), with CDDB support,
- * WAV, RAW, AU (with internal wav plug-in and MikMod plug-in),
- * MOD, XM, S3M, and other module formats (with MikMod plug-in),
- * .cin fi...

*** Bug 8313 has been marked as a duplicate of this bug. ***

Message-ID: <email address hidden>
Date: Sat, 25 Sep 2004 11:02:41 +0200
From: Pierre Machard <email address hidden>
To: Eduard Bloch <email address hidden>
Cc: <email address hidden>
Subject: Re: xmms/libmikmod2 bug is grave

--17pEHd4RhPHOinZp
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

Hello,

On Sat, Sep 18, 2004 at 12:34:46PM +0200, Eduard Bloch wrote:
> severity 261001 grave
> tags 261001 + patch
> thanks
>=20
> Why did you set the severity back if you did not understand the issue?
> The problem here is not a plugin that breaks because of some missing
> extra library (which would be okay).=20
>=20
> > The fact that libmikmod2 is not installed does not prevent xmms to work.
>=20
> Wrong. That is the core of the problem. xmms application does not start
> at all. I tried to get a backtrace now, but gdb does not produce any
> data, maybe it is confused with its thread model. No idea.
> However, xmms starts with LD_ASSUME_KERNEL=3D2.4.1 and this problem may be
> somehow related to TLS.

On my environment (sarge) I have not this problem. I am running a
2.6.7-1-k7 kernel, but when I was running a 2.4.x I had not this
problem. Are you running a Debian kernel or are you running a home made
kernel ?

That's why I downgraded the bug repport. Moreover Josip Rodin seems
pretty away currently.

> Personally, I would remove that mikmod plugin completely and replace the
> Recommends: entry with xmms-modplug. Why? The plugin is crap. No control
> options, no information box, not even the progress bar is working.
> xmms-modplug and its library need only few kilobytes more, but provide
> all those features, and better sound quality and are not crashing in
> that way.

According to xmms-modplug, xmms is not required. I am not sure that
putting a such Recommands is really obvious.

Cheers,
--=20
                                Pierre Machard
<email address hidden> http://debian.org
GPG: 1024D/23706F87 : B906 A53F 84E0 49B6 6CF7 82C2 B3A0 2D66 2370 6F87

--17pEHd4RhPHOinZp
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: Digital signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)

iD8DBQFBVTQws6AtZiNwb4cRArqyAJ0Zpvv4cSK55YcO0rFV8aL7yX9fpgCgt3xS
xIrprq2nE35zdnXKekNpFGM=
=J/lC
-----END PGP SIGNATURE-----

--17pEHd4RhPHOinZp--

Message-ID: <email address hidden>
Date: Sat, 25 Sep 2004 13:55:07 +0200
From: Eduard Bloch <email address hidden>
To: Pierre Machard <email address hidden>
Cc: <email address hidden>
Subject: Re: xmms/libmikmod2 bug is grave

#include <hallo.h>
* Pierre Machard [Sat, Sep 25 2004, 11:02:41AM]:

> > Why did you set the severity back if you did not understand the issue?
> > The problem here is not a plugin that breaks because of some missing
> > extra library (which would be okay).=20
> >=20
> > > The fact that libmikmod2 is not installed does not prevent xmms to wo=
rk.
> >=20
> > Wrong. That is the core of the problem. xmms application does not start
> > at all. I tried to get a backtrace now, but gdb does not produce any
> > data, maybe it is confused with its thread model. No idea.
> > However, xmms starts with LD_ASSUME_KERNEL=3D2.4.1 and this problem may=
 be
> > somehow related to TLS.
>=20
> On my environment (sarge) I have not this problem. I am running a
> 2.6.7-1-k7 kernel, but when I was running a 2.4.x I had not this
> problem. Are you running a Debian kernel or are you running a home made
> kernel ?

A-Ha. I think, something reported by several people cannot be just
random irreproducible problem. In fact, you need following conditions to
reproduce this bug:

 - run a 2.6.x kernel (as stated in other bug reports!)
 - have a libc with NTPL/TLS support
 - install the binary nvidia drivers (and make sure it setups its TLS
   libraries)

Then, for some reason, XMMS does this (not) funny thing right after
libGL.so.1 has been loaded.
=20
> Moreover Josip Rodin seems pretty away currently.

ACK

> > Personally, I would remove that mikmod plugin completely and replace the
> > Recommends: entry with xmms-modplug. Why? The plugin is crap. No control
> > options, no information box, not even the progress bar is working.
> > xmms-modplug and its library need only few kilobytes more, but provide
> > all those features, and better sound quality and are not crashing in
> > that way.
>=20
> According to xmms-modplug, xmms is not required. I am not sure that
> putting a such Recommands is really obvious.

It is not required because there is a very simple player application
included in the package which is supposed to do the same thing as xmms
(though, it has very limited features).

Regards,
Eduard.
--=20
Vermutungen sind die Ausflucht jener Leute, die nichts wissen.
  -- O'Connor

Message-ID: <email address hidden>
Date: Sat, 25 Sep 2004 15:28:55 +0200
From: Pierre Machard <email address hidden>
To: Eduard Bloch <email address hidden>
Cc: <email address hidden>, <email address hidden>
Subject: Re: xmms/libmikmod2 bug is grave

--K8nIJk4ghYZn606h
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

reassing 261001 glibc
thanks,

Hi Eduard,=20

thanks for your quick reply

On Sat, Sep 25, 2004 at 01:55:07PM +0200, Eduard Bloch wrote:
> #include <hallo.h>
> * Pierre Machard [Sat, Sep 25 2004, 11:02:41AM]:
>=20
> > > Why did you set the severity back if you did not understand the issue?
> > > The problem here is not a plugin that breaks because of some missing
> > > extra library (which would be okay).=20
> > >=20
> > > > The fact that libmikmod2 is not installed does not prevent xmms to =
work.
> > >=20
> > > Wrong. That is the core of the problem. xmms application does not sta=
rt
> > > at all. I tried to get a backtrace now, but gdb does not produce any
> > > data, maybe it is confused with its thread model. No idea.
> > > However, xmms starts with LD_ASSUME_KERNEL=3D2.4.1 and this problem m=
ay be
> > > somehow related to TLS.
> >=20
> > On my environment (sarge) I have not this problem. I am running a
> > 2.6.7-1-k7 kernel, but when I was running a 2.4.x I had not this
> > problem. Are you running a Debian kernel or are you running a home made
> > kernel ?
>=20
> A-Ha. I think, something reported by several people cannot be just
> random irreproducible problem. In fact, you need following conditions to
> reproduce this bug:
>=20
> - run a 2.6.x kernel (as stated in other bug reports!)
> - have a libc with NTPL/TLS support
> - install the binary nvidia drivers (and make sure it setups its TLS
> libraries)
>
> 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=20
that Eduard described break xmms.

If you prefer, you can duplicate the bug repport and reassign it to
xmms and/or nvidia.

Cheers,
--=20
                                Pierre Machard
<email address hidden> http://debian.org
GPG: 1024D/23706F87 : B906 A53F 84E0 49B6 6CF7 82C2 B3A0 2D66 2370 6F87

--K8nIJk4ghYZn606h
Content-Type: application/pgp-signature; name="signature.asc"
Content-Description: Digital signature
Content-Disposition: inline

-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.2.4 (GNU/Linux)

iD8DBQFBVXKXs6AtZiNwb4cRAqcoAJ49dva8DLhgb4klLiioNN2l3Z4i9QCeO7DJ
Z8gLPi5zWmDV4APRnDkuz/k=
=16Lp
-----END PGP SIGNATURE-----

--K8nIJk4ghYZn606h--

Message-ID: <email address hidden>
Date: Sat, 25 Sep 2004 18:35:42 +0200
From: Pierre Machard <email address hidden>
To: GNU Libc Maintainers <email address hidden>
Cc: <email address hidden>
Subject: [<email address hidden>: Re: xmms/libmikmod2 bug is grave]

--UKNXkkdQCYZ6W5l3
Content-Type: multipart/mixed; boundary="UBnjLfzoMQYIXCvq"
Content-Disposition: inline

--UBnjLfzoMQYIXCvq
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

reassign 261001 glibc
thanks,
--=20
                                Pierre Machard
<email address hidden> http://debian.org
GPG: 1024D/23706F87 : B906 A53F 84E0 49B6 6CF7 82C2 B3A0 2D66 2370 6F87

--UBnjLfzoMQYIXCvq
Content-Type: message/rfc822
Content-Disposition: inline

Date: Sat, 25 Sep 2004 15:28:55 +0200
From: Pierre Machard <email address hidden>
To: Eduard Bloch <email address hidden>
Cc: <email address hidden>, <email address hidden>
Subject: Re: xmms/libmikmod2 bug is grave
Message-ID: <email address hidden>
References: <email address hidden> <email address hidden>
 <email address hidden>
Mime-Version: 1.0
Content-Type: multipart/signed; micalg=pgp-sha1;
 protocol="application/pgp-signature"; boundary="K8nIJk4ghYZn606h"
Content-Disposition: inline
In-Reply-To: <email address hidden>
Organization: debian.org
User-Agent: Mutt/1.5.6+20040722i

--K8nIJk4ghYZn606h
Content-Type: text/plain; charset=us-ascii
Content-Disposition: inline
Content-Transfer-Encoding: quoted-printable

reassing 261001 glibc
thanks,

Hi Eduard,=20

thanks for your quick reply

On Sat, Sep 25, 2004 at 01:55:07PM +0200, Eduard Bloch wrote:
> #include <hallo.h>
> * Pierre Machard [Sat, Sep 25 2004, 11:02:41AM]:
>=20
> > > Why did you set the severity back if you did not understand the issue?
> > > The problem here is not a plugin that breaks because of some missing
> > > extra library (which would be okay).=20
> > >=20
> > > > The fact that libmikmod2 is not installed does not prevent xmms to =
work.
> > >=20
> > > Wrong. That is the core of the problem. xmms application does not sta=
rt
> > > at all. I tried to get a backtrace now, but gdb does not produce any
> > > data, maybe it is confused with its thread model. No idea.
> > > However, xmms starts with LD_ASSUME_KERNEL=3D2.4.1 and this problem m=
ay be
> > > somehow related to TLS.
> >=20
> > On my environment (sarge) I have not this problem. I am running a
> > 2.6.7-1-k7 kernel, but when I was running a 2.4.x I had not this
> > problem. Are you running a Debian kernel or are you running a home made
> > kernel ?
>=20
> A-Ha. I think, something reported by several people cannot be just
> random irreproducible problem. In fact, you need following conditions to
> reproduce this bug:
>=20
> - run a 2.6.x kernel (as stated in other bug reports!)
> - have a libc with NTPL/TLS support
> - install the binary nvidia drivers (and make sure it setups its TLS
> libraries)
>
> Then, for some reason, XMMS does this (not) funny thing right after
> libGL.so.1 has been loaded.

The problem is really nvidia driver...

Message-ID: <email address hidden>
Date: Sun, 26 Sep 2004 15:56:01 +0900
From: GOTO Masanori <email address hidden>
To: Pierre Machard <email address hidden>
Cc: <email address hidden>, Eduard Bloch <email address hidden>
Subject: Re: [<email address hidden>: Re: xmms/libmikmod2 bug is grave]

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

This bug has been marked as a duplicate of bug 8474.

Message-ID: <email address hidden>
Date: Sat, 16 Oct 2004 10:25:58 +0200
From: Eduard Bloch <email address hidden>
To: GOTO Masanori <email address hidden>
Cc: Pierre Machard <email address hidden>, <email address hidden>
Subject: Re: [<email address hidden>: Re: xmms/libmikmod2 bug is grave]

reopen 261001
thanks

#include <hallo.h>
* GOTO Masanori [Sun, Sep 26 2004, 03:56:01PM]:
> 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.

WTF? Do not just close this bug report, violating the social contract.
Damn, if you are not able to fix it, reassign it back, there there could
be at least a workaround.

Regards,
Eduard.
--
<Ganneff> kde und tastatur? passt doch nicht mit dem nutzerprofil
 "windepp" zusammen :)

Message-ID: <email address hidden>
Date: Sat, 16 Oct 2004 11:01:58 +0200
From: Eduard Bloch <email address hidden>
To: <email address hidden>
Subject: Re: [<email address hidden>: Re: xmms/libmikmod2 bug is grave]

reopen 261001

Message-ID: <email address hidden>
Date: Tue, 19 Oct 2004 23:34:08 +0900
From: GOTO Masanori <email address hidden>
To: Eduard Bloch <email address hidden>
Cc: GOTO Masanori <email address hidden>, Pierre Machard <email address hidden>, <email address hidden>,
 <email address hidden>
Subject: Re: [<email address hidden>: Re: xmms/libmikmod2 bug is grave]

reassign 261001 xmms
thanks

At Sat, 16 Oct 2004 10:25:58 +0200,
Eduard Bloch wrote:
> #include <hallo.h>
> * GOTO Masanori [Sun, Sep 26 2004, 03:56:01PM]:
> > 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.
>
> WTF? Do not just close this bug report, violating the social contract.
> Damn, if you are not able to fix it, reassign it back, there there could
> be at least a workaround.

Read #219943 before claiming social contract. We can't fix it. I
reassign it back following your suggestion.

-- gotom

Message-Id: <1099648348.3654.426.camel@thanatos>
Date: Fri, 05 Nov 2004 10:52:29 +0100
From: Thomas Hood <email address hidden>
To: <email address hidden>
Subject: Not RC

retitle 261001 xmms: "Assertion ... failed" with libmikmod.so.2, kernel 2.6.6, libc6 with NTPL/TLS, nvidia drivers
severity 261001 normal
thanks

This bug can't be RC if it is only triggered when non-free software is used.

--
Thomas Hood

Message-Id: <email address hidden>
Date: Sun, 18 Sep 2005 00:06:00 -0500 (CDT)
From: <email address hidden> (David Moreno Garza)
To: <email address hidden>
Subject: tagging 261001, tagging 261001

 # The bug is not really fixed with the patch sent.
tags 261001 - patch
tags 261001 upstream