I've had 3 random crashes tonight. A couple of times while playing a track and doing nothing else. One more time when I was using the delete key to remove items from the playback list.

Sorry, but reporting crashes here is not very useful, especially with no additional information of what you were doing when it crashed and a valid backtrace.

Do you have a backtrace? Then please file it on http://bugs.kde.org

Mamarok wrote:Sorry, but reporting crashes here is not very useful, especially with no additional information of what you were doing when it crashed and a valid backtrace.

Do you have a backtrace? Then please file it on http://bugs.kde.org

> useful
I disagree. I think it is useful for the community to know that there is some degree of instability with the latest version. People may not want to upgrade to the latest version due to this information.

> additional information
There is no additional information to provide. I was doing nothing else except what was originally stated -> "playing a track"

>backtrace
No idea what this is or how to obtain it.

devehf: if you want to be useful to the community you provide a valid backtrace so the developers can fix it.
If you have installed your system correctly, a crash will trigger Dr. Konqi to start and generate a backtrace you can submit to the bug tracker.

JFYI: Amarok 2.2.1 is rock stable on my test PC and so is Amarok 2.2-git

Everything else is just pure trolling.

installed your system correctly

Ah, there is the contradiction. How are users supposed to know the definition of "correct"?

I installed "correctly" per the blog post and other sparse documentation.

Dr. Konqi does not start and generate a backtrace when Amarok crashes.

I have now included the debug components of Amarok in the hopes that this will help with obtaining a backtrace. I have no idea if this will produce the desired observation data. So far it has not.

Perhaps the crashing is due to the rescan on my collection. It is worth some discussion and absolutely not "trolling".

@Devehf: When the application crashes, a dialog of some form should open up. What is the name of this?

I did not receive a dialog.

I have re-scanned my collection again and the crashing appears to have stopped.

Anyone who has upgraded to 2.2.1 should definitely re-scan their collection.

Is there anyway the installations process can do this rescanning automatically based on previous preferences? Just a suggestion, since it sounds like the underlying data storage structure for collection information has changed significantly.

Please see the stick topic in this forum section...

Mamarok wrote:Please see the stick topic in this forum section...

Right. Thanks. I already had the issue and started this post before your sticky topic was posted.