Bug 185054

Summary: In playlist search's with option "Show only matches" Amarok redirects track actions to wrong tracks
Product: [Applications] amarok Reporter: Lasse Liehu <lasse.liehu>
Component: PlaylistAssignee: Amarok Developers <amarok-bugs-dist>
Status: RESOLVED FIXED    
Severity: normal CC: kdebugs, lamarque, nhn
Priority: NOR    
Version: 2.0.1   
Target Milestone: ---   
Platform: Gentoo Packages   
OS: Linux   
Latest Commit: Version Fixed In:

Description Lasse Liehu 2009-02-20 19:39:02 UTC 
Version:           2.0.1 (using KDE 4.2.0)
Compiler:          gcc (Gentoo 4.3.3 p1.0, pie-10.1.5) 4.3.3  
OS:                Linux
Installed from:    Gentoo Packages

That is, when I'm searching something in the playlist and the option "Show only matches" is on, usually the track actions like "Remove from playlist", "Queue track" etc. affect wrong tracks, i.e. not the tracks I wanted to be affected.

Steps to reproduce:
1. load up a playlist
2. search for example a track that's not the first track in the playlist by name, using the "show only matches" option
3. remove the first track in the list showing matches
4. clear the search
5. notice how the first track in playlist was affected, not the one you selected to be removed.
Comment 1 Lamarque V. Souza 2009-03-06 09:17:28 UTC 
I have this same problem here using Qt-4.4.2, KDE-4.2.0 and Amarok-2.0.1.1. That also happens when using Qt-4.5.0, KDE-4.2.1 and Amarok-2.0.2. I use Gentoo Linux amd64/2008.0/desktop and gcc version 4.1.2 (Gentoo 4.1.2 p1.0.1).
Comment 2 Johannes Felko 2009-03-16 20:47:21 UTC 
I can confirm this. Arch Linux Chakra KDE 4.2.1 Qt4.5 Amarok 2.0.2

If someone needs to unterstand better i made some screenshots.
http://peperjohnny.de/Bildschirmfoto1.png <- here you see the first songs in playlist
http://peperjohnny.de/Bildschirmfoto2.png <- searching for a band
http://peperjohnny.de/Bildschirmfoto3.png <- queued marked song. 2nd in search.
http://peperjohnny.de/Bildschirmfoto4.png <- song 2 in playlist was marked instead the one in search
Comment 3 Nikolaj Hald Nielsen 2009-03-17 08:12:08 UTC 
This is fixed for 2.1.0