Important: we do not accept reports against Amarok 1.x as we do not maintain it anymore. So please do not file any bug reports against it, those will be closed immediately!

Amarok's official bug tracker is http://bugs.kde.org

You can use this link to post Amarok bugs directly, it will spare you some time:
https://bugs.kde.org/enter_bug.cgi?product=amarok

Before reporting any bug, please check if it is not already reported. We have compiled a query for an easy search which can be found here: http://tinyurl.com/allamarokbugs

For all bug reports it is vital to tell us:

• the exact Amarok version, or whether you use Amarok from GIT (please provide at least the 'git pull' date and the commit hash number if possible)
• Which distro you're using
• What type of music you're trying to play
• What sound backend you use! - I can't emphasise this enough!
• What you were doing exactly when the bug occured

If it's a crash bug, a valid backtrace is mandatory. Normally, if you are using KDE, the bug report GUI application Dr. Konqi shows up and will guide you through the report. To be able to reproduce a valid backtrace, you should read this:

http://techbase.kde.org/Development/Tutorials/Debugging/How_to_create_useful_crash_reports

Hint: if you don't know which debugging package to install and if you don't have space restrictions on your computer, just install all the debug packages of the applications you are running, so you are sure you don't miss anything.

When reporting with Dr. Konqi, watch your screen, as Dr. Konqi will tell you if the backtrace is useful. In the KDE 4.3 version it even shows you a rating of the quality of the backtrace with yellow stars on the top right

Also, when a crash report starts with (no debugging symbols found) then it is useless, the same is the case if it is full of ?? (double question marks) which means it lacks debugging symbols.

Dr. Konqi also checks a list of potential duplicate bugs for you, please check those to avoid reporting a duplicate. Please see also the above link to the already reported bugs.

I should also say that it's far more likely that you'll get attention for the bug if you report it at bugs.kde.org. The developers find it quite hard to keep up with the reports on the forums. But you do get more attention from fellow users here and they might be able to help you too.

With respect to bugs against GIT, it is better to come to the channel #amarok (on irc.freenode.net) and ask if it's a bug that is known or not. Often bugs appear in GIT and get fixed within a few hours.

Post edited by:
mxcl, at: 2005/01/30 19:44
dangle_wtf, on Tue Jul 24, 2007 8:56 pm
Mamarok, on Sat Aug 22, 2009, 12:04

Max, you wrote:

I should also say that it\'s far more likely that you\'ll get attention for the bug if you report it at bugs.kde.org. I personally find it quite hard to keep up with the forums currently! But you do get more attention from fellow users here and they might be able to help you too.

I've tried to submit a bug using the bugzilla wizard, however I only received an error page as reply when I tried to submit the bug. I've reported this to the webmaster@kde.org, as requested on the error page. Is this a known problem?

Afterwards I've sent my bug info to amarok@kde.org (subject: Collection scanner fails for some sampler CDs), but have not yet received any reply mail, e.g. that someone would take a look at it.

Martin

Little OT but how can I prevent Amarok from opening thunderbird/kmail/whatever when it crashes? i.e. how can I disable automatic bug reporting?

Thanks a lot

Please be more specific how to check what engine is used!

Look in the Engine tab in Amarok settings on the Tools menu.

There is no engine tab in the settings window. Is that a bug? (I'm not joking)

Pah wrote:There is no engine tab in the settings window. Is that a bug? (I'm not joking)

The above instructions are a bit old, they still refer to Amarok 1.x.

This is the route

Settings>>>>configure amarok>>>>>>engine

If the bug reporting mechanism is at another location, that should have been a selection on the main home page for Amarok.  At least, that's the way it is done usually.

When you want people to use a particular thing, always link to it on the home page.  I wasted a lot of time looking for something that was hidden here.

Mark Kretschmann wrote:

Pah wrote:There is no engine tab in the settings window. Is that a bug? (I'm not joking)

The above instructions are a bit old, they still refer to Amarok 1.x.

What are the bug report instructions for Amarok 2?

Just a test for the new forum notifications...

Note that notifications are only sent when other users post....