Comment 25 for bug 841806

The originally reported bug had no crash relation at all.

I can imagine some scripts not correctly handling server failures and doing stuff like dividing by zero if they do not get their expexted data. This in turn should just result in an exception (can be seen in debug output) and a non functional script, not an Amarok crash.

The originally reported issue is fixed.

@"dupe" reporters: if this is scripting related try to find the cause by running Amarok from a shell with debug output enabled and check if the output after a crash points to script involvement. Which one? Which version? Try to deactivate it to verify.