I suffer from the same problem (which I already reported in bug #92321, probably also a duplicate of this bug). The crash happens always when amarok is started at KDE startup (because it was running when KDE was shut down). This makes it difficult to produce a good backtrace.
I suffer from the same problem (which I already reported in bug #92321, probably also a duplicate of this bug). The crash happens always when amarok is started at KDE startup (because it was running when KDE was shut down). This makes it difficult to produce a good backtrace.