Removing dirs after organizing goes too far up the dir tree.
Steps to Reproduce:
1.Organize some album so that an empty dir should be removed afterwards (e.g. /mnt/music/v/various artists/year/album)
Not only the empty dir is removed but also all dirs 3 levels up. (e.g. /mnt/music/v)
empty dir removed, everything else untouched.
If you need more info (log, etc.) I'll try and reproduce...
We need a konsole output started with 'amarok -d -nofork' when this happens.
Before I do that, I think I found something interesting:
Why does it think that first file _is_ /mnt/music/V/ ? It must have tried (and succeeded) to delete that file afterwards.
Created attachment 76879 [details]
screenshot of organize collection showing an invalid path for a file.
Doing a full rescan of my collection didn't help fixing those invalid paths. What I noticed, however, are duplicates which quite often have those invalid paths. The invalid path to that file in the screenshot was also a file that existed twice. Perhaps this report should be closed and a new one opened.
As a work-around I can try to exclude tracks with no valid filepath.
Git commit f6d38898e0cfbe41c3a03d95e31ad7072b9430ad by Ralf Engels.
Committed on 03/02/2013 at 19:58.
Pushed by rengels into branch 'master'.
Fix Organize collection folder deletion going 'too far'
M +11 -3 src/core-impl/collections/db/sql/SqlCollectionLocation.cpp
M +1 -1 src/core/collections/CollectionLocation.cpp