Created attachment 129086 [details] Digikam traces SUMMARY STEPS TO REPRODUCE 1. Original Organisation Folder 1: 20200305_scan600dpi_test.scanned22 – 2 images 1952+T_Papa18ans+1001.jpg 1953-juil+T_Papa19ans_Chevaux+Z_Papa_en_cheval+1002.jpg Folder 2: AlbumLouise3000_test.scanned22 – a single image All of three are TAGged NetB – because they are White and Black... 2. Going under Tags -> Type -> NetB This will display all 3 images - 2 from Folder 1 and the single one in folder 2. 3. Renaming the image in Folder 2. Raname the from directly from Digikan by removing the first letter from the file name. OBSERVED RESULT One of the images from Folder 1 does not show anymore. EXPECTED RESULT I should continue to see all 3 images. SOFTWARE/OS VERSIONS Windows: macOS: Linux/KDE Plasma: (available in About System) KDE Plasma Version: KDE Frameworks Version: Qt Version: About: ------ Professional Photo Management with the Power of Open Source - A KDE Family Project IRC: irc.freenode.net - #digikam Feedback: digikam-user@kde.org Build date: Oct 30 2019 (target: RelWithDebInfo) Rev.: d4189399d3b9a70e172e2e4c619548c5dd933280 (c) 2002-2019, digiKam developers team https://www.digikam.org Libraries: ---------- KDE Frameworks 5.61.0 Qt 5.13.1 (built against 5.13.1) The xcb windowing system ADDITIONAL INFORMATION I will include an open office document with snapshot... I'm also adding the digikam traces.
Created attachment 129087 [details] Snapshot example
I tried the problem with the same folder and file name. Here with digiKam-7.0.0-RC the problem cannot be reproduced. Please test it with the current AppImage from here: https://files.kde.org/digikam/ There is an error message in your log that the modification date of each file cannot be changed. This suggests that the file rights are incorrect, please check it. ------------------ DFileOperations::renameFile[0m: Failed to restore modification time for file "/vol/work/photo-scan/AlbumLouise3000_test.scanned22/1953Approx_T_Papa_Z_Avec_deux_chiots_et_la_mere.jpg" ------------------ Maik
Hello Mark, I was not able to reproduce the problem with the RC version provided, even on a larger scale. I will continue to do some more testings and keep you posted. Thank you very much, Guy
I close the bug for digiKam-7.0.0. If necessary, open the bug again. Maik