I have suddenly got the problem that amarok will not play any files, it zooms through the playlist and then pops up a message "Too many errors encountered in playlist". Running amarok in debug mode I see the message "xine is asking to seek behind the end of the data stream". Googling on that message there are many hits but no definitive solution, just "windoze"-style responses like "I reinstalled and it went away". I have just updated to KDE 4.2.4 and amarok 2.1 and it didn't go away.

However, if I login as a new user the problem doesn't occur. So the problem must be with the config files in my home directory, right? I deleted ~/.kde4/share/apps/amarok/*, ~/.kde4/share/config/amarokrc, ~/.kde4/share/config/phonondevicerc, the contents of ~/.kde4/cache-host and ~/.kde4/tmp-host but it made no difference. I cannot see anything under ~/.config and ~/.local that looks suspicious, so what else could it be? This is really very strange! I have a current Gentoo system, so amarok is compiled from pristine sources from your site.

TIA

If you really wiped out all amarok related files and folders and it works with a new user, try moving your config folder to config.bak and retry.
If that works, try to copy your needed configs over to your fresh folder, checking if your install still works. (Although I would prefer reconfiguring my apps, cause data is kept in the apps folder)
Unfortunately you didn't report, if the update was from KDE3 -> KDE4 or just a minor update like 4.2.3->4.2.4

m0nk

My update was from 4.2.3 to 4.2.4. Removing ~/.config makes no difference, as I expected.

Dieter Schroeder wrote:If you really wiped out all amarok related files and folders and it works with a new user

This is the substance of my question, did I really wipe out all amarok files? Which are all the amarok related files?

Amarok stores its configuration in ~/.kde(4)/share/config/amarokrc and ~/.kde(4)/share/apps/amarok/

(.kde or .kde4 depending on distro )

Sorry, that was a misunderstanding, I meant the folder ~/.kde4/share/config

m0nk

After leaving it for a few days I took a fresh look and deleted ~/.xine/* - problem solved! Should have been obvious really since xine was giving the errors.