Summary: | Organize collection folder deletion going 'too far' | ||
---|---|---|---|
Product: | [Applications] amarok | Reporter: | Thierry Göckel <thierry> |
Component: | Collections/Organize Files Dialog | Assignee: | Amarok Developers <amarok-bugs-dist> |
Status: | RESOLVED FIXED | ||
Severity: | critical | CC: | ralf-engels |
Priority: | NOR | ||
Version: | 2.7-git | ||
Target Milestone: | 2.8 | ||
Platform: | Debian unstable | ||
OS: | Linux | ||
Latest Commit: | http://commits.kde.org/amarok/f6d38898e0cfbe41c3a03d95e31ad7072b9430ad | Version Fixed In: | 2.8 |
Attachments: | screenshot of organize collection showing an invalid path for a file. |
Description
Thierry Göckel
2013-02-03 12:45:27 UTC
We need a konsole output started with 'amarok -d -nofork' when this happens. Before I do that, I think I found something interesting: http://i.imgur.com/JS5I943.png 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. Thanks 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' FIXED-IN: 2.8 M +11 -3 src/core-impl/collections/db/sql/SqlCollectionLocation.cpp M +1 -1 src/core/collections/CollectionLocation.cpp http://commits.kde.org/amarok/f6d38898e0cfbe41c3a03d95e31ad7072b9430ad |