Version: 1.1-beta2 (using KDE KDE 3.3.0) Installed from: Gentoo Packages Compiler: gcc-3.4.1 OS: Linux When running amarok-1.1-beta2 on amd64, I'm unable to play mp3 files - amarok would crash instantly. The still running instances of amarokapp would then use 100% CPU-Power. The only way to get rid of them is to do killall -SIGKILL amarokapp I have not been able to gather a backtrace. My binaries aren't stripped and have debug-symbols, but I so far was unable to create a backtrace. Just running 'gdb amarok', let it crash and then 'bt' would tell me: no stack I can't tell you so far, if it's due to xine-backend (it worked all with amarok-1.0.1) or some other reason. The Gstreamer backend would not work here (crash too, can't even load gstreamer. So this is another bug, and I'll look at it some other time. Oh, and running gst-register-0.8 wouldn't help) The output from amarok is: amarok: PluginManager Service Info: amarok: --------------------------- amarok: name : xine Engine 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 to xine-engine! 9 out of 10 cats prefer xine! Please report bugs to amarok-devel@lists.sourceforge.net Build stamp: Sep 17 2004 14:46:19 amarok: END [static EngineBase* EngineController::loadEngine()] amarok: END [void App::applySettings(bool)] amarok: [App] Pruned 0 of 2 amazon cover images. [amaroK loader] startup successful. [amaroK loader] exiting. Program exited normally. (gdb) amarok: [virtual void LoaderServer::newConnection(int)] amarok: Received: STARTUP (8 bytes) QColor::setRgb: RGB parameter(s) out of range QColor::setRgb: RGB parameter(s) out of range QColor::setRgb: RGB parameter(s) out of range KCrash: Application 'amarok' crashing... So, if you could tell me how to debug this thing (gdb amarokapp doesn't help either), let me know
**bump** This bug seems to be a 64bit issue. If so, amarok is plain unusable on any 64bit arches. If somebody could give me some hints on how to debug amarok (Since I was unsucessful in getting a backtrace), I would dig into it by myself. I don't think it's okay to have a bug like this in a 1.1 relese (Sorry for the ranting, but I really think this bug needs attention)
To debug I'd say you need some symbols, so xine and amarok with debug info would be grand. if you compile ./configure --enable-debug=full it gives lots of info. I imagine this is a xine issue and not an amaroK issue, even if the files work with Kaffeine. I see bug reports like this often and they seem to get fixed when upgrading xine.
as far as i can tell, you have to run your backtrace against amarokapp, not amarok cheers
please look at the instructions at http://amarok.kde.org/component/option,com_staticxt/staticfile,dev-faq.html#id251275 and reopen this report with a valid backtrace, if it's still appearing. thanks, muesli