Inconsistency detected by ld.so: ../sysdeps/generic/dl-tls.c: 75: _dl_next_tls_modid: Assertion

thats the error from the command line when i try to run xine-ui
I am running xine-lib-1.1.0 and xine-ui-0.99.4. anyone know a fix?

thanks

this is a strange problem
after much confusion it was decided this was a glibc bug
if you are running Debian this was fixed with
glibc-2.3.2.ds1-21
- Jeff Bailey <jbailey@raspberryginger.com>:
- debian/patches/glibc232-tls-crashfix.dpatch: Fix tls assertion that
crashes xmms/nvidia. (Closes: #219352)

if you are running some other distro or a more modern version of glibc than mentioned above you might want to take this one to your distributons bug reports

Hi

I figured out how to fix it not what was really wrong with the setup. I installed xine-lib-1.1.1 over xine-lib-1.1.0. Everything is working up to par now. I am running gcc-4.0.2, glibc-2.3.6, and binutils-2.16.1. My distro is self built scratch build. Also I'm running linux-2.6.14.3. I have an nvidia video card and am using there kernel modules for video. I have a suspicion it has to do with the libnvidia-tls.so.1 library being problem.

yea there are always ways to remask the problem but the problem is that bogus assert in glibc. I think the other libs are not presenting invalid data
but rather glibc is not properly handeling a valid case that happens just rarely in the GL code. this would be a fun one to study actually.
it's just some code where it checks for gaps when it loads a library i think
somewhere in the logic as it sprawles across multiple files must be a chack for <= when it should just be < or something like that. Curious the bug has persisted in the main branch code for all this time.

Hi,

I bet you are right, and I was googling around on this function, and similar errors. I couldn't find any for my version of glibc. I am using glibc-2.3.6. I was wondering how such a bug could persist for such a long time. I do not know much about writing code, but this bug has been around since at least glibc-2.3.4. Maybe that's not allot of time. Anyway how does one send in a bug report for this.

you can try
http://www.gnu.org/software/libc/bugs.html
it will most likely be something they can't replicate for one reason or another
which i guess is why it has not been fixed in the first place.
and they always say file only bugs on current cvs which is the most absurd thing.They are the only people capable of constantly recompling new versions of glibc -- i can't imagine how they do that. plus you already upgraded past the problem as well.
It is, on their side, quite a difficult thing to determine who or what is at fault in this case if they can't reproduce the problem.