Version: 2.0 beta3 (using KDE 4.1.2) OS: Linux Installed from: Ubuntu Packages When pushing the "Repopulate" button in Dynamic random play-list, it uses the hole ~/Music folder and not the defined sub-folder (~/Music/pop). The same happens when right-click and select Append to Playlist at Local Collection. But by selecting the contents of Local Collection and then Append to Playlist, it puts only the contents of the sub-folder.
When you submit bug reports, you need to be general, in a way that lets us reproduce the problem. Please explain the steps you took, the results you obtained and the expected outcome. If you cannot do this, I will have to close the report.
What I think is happening here is that ~/Music was scanned automatically at first startup. Then the reporter sets it to ~/Music/pop. The db still includes files which are in ~/Music but outside of ~/Music/pop. They are not shown in the collection browser but still get included in the dynamic playlist.
Sory, I though I was. I installed the Amarok 2 beta 3 at intrepid ibex. When I opened it, It had selected the ~/Music folder at the Collection Folders. I then went and deselected it and then selected the ~/Music/pop folder (and not the other sub-folders at the Music folder). Then I pressed Rescan Collection. At the Local Collection there are only the files of the ~/Music/pop folder. But when I press the Repopulate button at Playlist the playlist repopulates with files from the other sub-folders at the Music folder. When I right-click the Local Collection "folder" at Local Collection and select Append to Playlist, The playlist appends files from the other subfolders (which are non visible whet I search the Local Collection). If I select the first file at Local Collection and then Shift-select the last, and right-click and select Append to Playlist NO files from subfolders append to the playlist. I have pressed Rescan Collection several times, and removing the subfolders from the directory and re-pressing Rescan Collection didn't solve it ether.
dupe of http://bugs.kde.org/show_bug.cgi?id=171418
*** This bug has been marked as a duplicate of bug 171418 ***