I try to re-organize my local collection and move images from one local collection to a new one, without losing meta information like tags etc. I thought this should be possible through using digikam instead of a file manager, because I expect that it adjusts the corresponding entries in the digikam database when doing it that way. (Is that right?) Reproducible: Always Steps to Reproduce: 1. assume you have an old collection, e.g. /usr/local/old 2. and a new collection, e.g. /usr/local/new 3. add both to digikam as local collections 4. in the Album view, try to drag and drop albums from old to new 5. in the context menu that shows up select "Move here" Actual Results: In the console I see only the following debug message: digikam.general: Using 4 CPU core to run threads QMetaObject::indexOfSignal: signal finished() from Digikam::ActionThreadBase redefined in Digikam::IOJobsThread digikam.general: Action Thread run 1 new jobs digikam.iojob: Thread Finished digikam.general: One job is done But after that nothing has happened, nothing has been moved. No job running in background. Moving albums within the same collection works as expected.
A question: are the collections on different partitions? Maik
Git commit 2065450d991966c46e9a96dbe87d7a28b7d13ee0 by Maik Qualmann. Committed on 16/01/2016 at 20:57. Pushed by mqualmann into branch 'master'. if QDir::rename fails, try copy and remove M +10 -0 libs/iojobs/iojob.cpp http://commits.kde.org/digikam/2065450d991966c46e9a96dbe87d7a28b7d13ee0
Please try the latest git commit. Maik
No, the collections were on the same partition. I tried the latest git commit and now it works! Thanks for fixing it :-) (unfortunately I found out that moving files with special characters does not work too, I will file a new bug report for that...)
(In reply to Thomas Eschenbacher from comment #4) > No, the collections were on the same partition. Strange, I can confirm the problem only for different partitions. What a file system do you use? Maik
Sorry, my mistake! You are right, that test was indeed across different partitions, even different disks (both using btrfs). But with your latest patch it is no longer reproducible here.