Hi, it happens that today I came by the solution to this old post.
Since someone else might have the same problem, I decided to post it here.

The original post was:
viewtopic.php?f=116&t=86234
which is locked so I can't post this solution there.

The solution is found here:
http://forum.sabayon.org/viewtopic.php?t=20120

Quote:
"
-> check your installation for multiple XINE installs:
=> /usr/lib/xine/plugins
==> drwxr-xr-x 4 root root 4096 Jun 17 13:53 1.28

IF NOT: you have the same problem as I had.

The FIX
Check:
/usr/lib $ ll libxine.*
-rw-r--r-- 1 root root 1046 Apr 25 15:11 libxine.la
lrwxrwxrwx 1 root root 17 Jun 17 13:53 libxine.so -> libxine.so.1.28.0
lrwxrwxrwx 1 root root 17 Jun 17 13:53 libxine.so.1 -> libxine.so.1.28.0
-rwxr-xr-x 1 root root 309384 Apr 25 15:12 libxine.so.1.28.0

If you have libxine.so.1.27* there, DELETE IT.
Delete the cruft in /usr/lib/xine/plugins
(i.e.: delete /usr/lib/xine/plugins/1.27)

if you EMERGED xine-lib:
-> emerge -C --nodeps xine-lib

remove xine-lib:
equo remove --nodeps xine-lib

For fun I also zapped AMAROK:
emerge -C amarok amarok-utils
equo remove amarok amarok-ultis

RE-INSTALL:
equo install xine-lib amarok amarok-utils

Now it should work again
"

The thanks go to the guy who found this solution.
Regards

Apart from being a bit out of date and of topic (xine related), it would have been nice to post the distro you're using or this solution works.

m0nk

Hi,
indeed late, but if it helps someone then it's worth it.

An indicator of how hard this thing was to track is the fact that amarok couldn't start because of xine, and nobody had even a hint about it.
Because of that I couldn't use amarok for a year. lol
gdb and the amarok debug mode didn't help much. (or maybe I didn't try hard enough)

As for the distro that would be sabayon (as the link suggests).

Cheers