docs.kde.org
Troubleshooting
Prev
Next

Troubleshooting

1. Amarok crashes during the Collection scan, always at the same point. What's happenning?
2. Amarok crashes when I play a certain track, everytime, what's wrong?
3. Amarok crashes often, what can I do?
4. How can I obtain a decent backtrace?
5. Amarok is not using the tags I know are in my files!
6. Amarok is not displaying my utf-8 id3v2 tags properly!
7. Why do my statusbar icons always look active?
8. Why does Amarok complain about undefined symbols and then refuses to start?
1.

Amarok crashes during the Collection scan, always at the same point. What's happenning?

It's likely that one file in your Collection triggers a bug in the TagLib library, and makes Amarok crash. You can identify this file by looking at ~/.kde/share/apps/amarok/collection_scan.log. You should report this crash to the TagLib bug database on bugs.kde.org and attach the broken file. Afterward you can remove the file from your Collection and repeat the scanning.

2.

Amarok crashes when I play a certain track, everytime, what's wrong?

This usually means TagLib is crashing while reading that track's tags. Report the bug against TagLib at bugs.kde.org.

3.

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.

4.

How can I obtain a decent backtrace?

See the Debugging HowTo.

5.

Amarok is not using the tags I know are in my files!

If Konqueror or other apps are displaying different Title, Artist, Album or Genre information than Amarok is picking up when it creates your collection, it may be reading the older ID3v1 format tags rather than the newer ID3v2 tags. This can be due to your Encodings setting: Go to Settings->Configure Amarok, and then find the Encodings section of the Settings panel. Uncheck all checkboxes to "Do not decode the following as latin1". Rescan your collection to pick up the ID3v2 tags.

6.

Amarok is not displaying my utf-8 id3v2 tags properly!

This is because most applications put utf8 data into id3v2 tags but do not specify the encoding as unicode. This perl script will fix that.

#!/usr/bin/perl
die "File $ARGV[0] doesn't exist" unless -f $ARGV[0];
use MP3::Mplib;
my $mp3 = MP3::Mplib->new($ARGV[0]);
my $v2tag = $mp3->get_v2tag;
print "Error writing tags of $ARGV[0]\n" unless $mp3->set_v2tag($v2tag,&UTF8);

Note

This script requires the perl module MP3::Mplib which can be installed by issuing this command perl -MCPAN -e 'install MP3::Mplib'

7.

Why do my statusbar icons always look active?

Amarok statusbar icons(Random/Repeat/Append) look constantly Active on KDE 3.4.0. This is a known bug in KDE 3.4.0. The icon effects are sometimes forgotten. Simple fix kcontrol Appearance->Icons->Advanced, set disabled state to "Gray" and "Semi-transparent". Note that sometimes you must click on the icon 3 times before it has an effect after making this change.

8.

Why does Amarok complain about undefined symbols and then refuses to start?

if you get this error : "amarokapp: symbol lookup error: amarokapp: undefined symbol: _ZN11KSystemTray9setPixmapERK7QPixmap", then check that amarokapp uses the correct libqt (check with : ldd `which amarokapp` | grep qt).

To fix it, you might have to remove any conflicting libqt and/or edit /etc/ld.so.conf so it pick up the correct version first.

Prev
Next
Home


docs.kde.org