Amarok crashes often, what can I do?
Upgrade your ALSA libs and utils to the latest version, or use OSS, or OSS emulation. If you use MySQL as the database backend, try the SQLite one, it is slightly more mature (the Amarok code, not the db itself) Try a different audio-engine. Make sure that all the libraries that Amarok uses were compiled with the same GCC version as Amarok itself. The situation when Amarok is compiled using GCC 3.4.x and linked against taglib which was compiled using GCC 3.3.x can lead to crashes during tag editing. If you’re using KDE with artsd, try disabling “auto suspend if idle after…” in the sound system settings or at least don’t use a value of 1 second since that will interfere every time amarok switches songs. Otherwise, forward us the backtraces when the email pops-up (you’ll see). If you get a crash often you will get it fixed for sure if you forward a really good backtrace to us. See the next sections for assistance there.
• Upgrade your ALSA libs and utils to the latest version, or use OSS, or OSS emulation • If you use MySQL as the database backend, try the SQLite one, it is slightly more mature (the Amarok code, not the db itself) • Try a different audio-engine. • Make sure that all the libraries that Amarok uses were compiled with the same GCC version as Amarok itself. The situation when Amarok is compiled using GCC 3.4.x and linked against taglib which was compiled using GCC 3.3.x can lead to crashes even if you are not editing tags. • If you’re using KDE with artsd, try disabling “auto suspend if idle after…” in the sound system settings or at least don’t use a value of 1 second since that will interfere every time amarok switches songs. • Generally other apps blocking the sound devices might cause trouble. Sound demons like esd, Flash (also look for open web browsers in general), RealPlayer, older versions of Skype,… Otherwise, forward us the backtraces when the email pops-up (you’ll see). If
