Version: 1.2-CVS (using KDE KDE 3.3.1) Installed from: Compiled From Sources Compiler: gcc-Version 3.3.4 20040623 OS: Linux xine engine seems to be used as default engine after deleting $KDEHOME/share/config/amarokrc and crashes amarok on startup. workaround was --engine=gst-engine. Is this one of the evil threading problems everyone is talking about? :-) amarok: PluginManager Service Info: amarok: --------------------------- amarok: name : xine-Treiber amarok: library : libamarok_xine-engine amarok: desktopEntryPath : amarok_xine-engine.desktop amarok: X-KDE-amaroK-plugintype : engine amarok: X-KDE-amaroK-name : xine-engine amarok: X-KDE-amaroK-authors : (Max Howell) amarok: X-KDE-amaroK-rank : 254 amarok: X-KDE-amaroK-version : 1 amarok: X-KDE-amaroK-framework-version: 3 amarok: amarok: [xine-engine] Welcome! 9 out of 10 cats prefer xine! Please report bugs to http://bugs.kde.org Build stamp: Nov 14 2004 21:45:36 amarok: [xine-engine] Using configuration: /home/bogi/.kaffeine/config amarok: dl-close.c:365: _dl_close: Zusicherung »imap->l_type == lt_loaded || imap->l_opencount > 0« nicht erfüllt. Program received signal SIGABRT, Aborted. [Switching to Thread 16384 (LWP 27715)] 0x41c8fd61 in kill () from /lib/libc.so.6 (gdb) bt #0 0x41c8fd61 in kill () from /lib/libc.so.6 #1 0x41975e6d in pthread_kill () from /lib/libpthread.so.0 #2 0x419761c1 in raise () from /lib/libpthread.so.0 #3 0x41c8fb14 in raise () from /lib/libc.so.6 #4 0x41c90ed4 in abort () from /lib/libc.so.6 #5 0x41c892c5 in __assert_fail () from /lib/libc.so.6 #6 0x41d47e0b in _dl_close () from /lib/libc.so.6 #7 0x41d65d8b in in6addr_loopback () from /lib/libc.so.6 #8 0x0000016d in ?? () #9 0x41d65e36 in in6addr_loopback () from /lib/libc.so.6 #10 0x00000000 in ?? () #11 0x00000001 in ?? () #12 0x00000048 in ?? ()
The xine engine being picked over the gst-engine is bizarre. However I am almost certain this is a xine bug. What xine version are you using? Also --engine=gst-engine shouldn't work, you have to specify --engine='Gst engine' to get the gst-engine, as that's the name in the thingy. So I'm fairly surprised that worked too! I could do with a bt of this with xine compiled with debug. I've had a few of these reported. As I say, I'm fairly sure it's a xine bug as they repeatedly seem to be.
I recompiled xine-lib with --enable-debug + amarok, now the xine engine is working again. Closing.
Weird! Thanks for trying the debug though Bochi-san.