Version: 2.3.1-GIT (using KDE 4.4.4) OS: Linux Not so long ago I have already described this problem in amarok.kde.org. The problem in the next: when I did the second click on an item in the play list, amarok opens it for rename. But it's possible that I did the first click about half an hour ago, or, I could never do this (If I clicked on the album header and there would selected all the tracks, or pressed ctrl+a). I can't understand, what's the complexity? All that is needed — is two variables, that would contain item_id (id of the item, which is the latest clicked), and timestamp (when this event occured). When the next click event happened, you need to compare saved in the "timestamp" value with the current timestamp. And only if difference is < 1/2/etc seconds you have to compare item_id with id of the latest clicked item. And if this comparison will return true you have to open item for renaming. Reproducible: Always
This is an automated message from the triager: Amarok 2.4.1 has been released on May 8 already. Could you please upgrade and test if you can still reproduce this bug? Without feedback within a month we will close this bug as resolved. Thank you for your understanding.
Amarok 2.4.1 Bug is not fixed.
Thank you for the fast feedback.
Renaming the report as it was not quite clear on first sight.
Oh, and it is a duplicate, sorry for the noise. *** This bug has been marked as a duplicate of bug 220818 ***