SUMMARY Mainenance-SyncMeta with 'from DB to Pictures' produces a few jpg files with wrong extension (example .jpg12345). The jpg.xmp seems ok. STEPS TO REPRODUCE 1. Menu: Tools|Maintenance, enable (only) sync, direction to Pictures 2. Wait until it is finished (long... to be expected) 3. A cmd line in the Album root OBSERVED RESULT find . -name '*.jpg?????' Result: ./1998/1998 USA Urlaub/06_08.jpg26526 ./1998/1998 USA Urlaub/08_43.jpg26912 ./1998/1998 USA Urlaub/07_09.jpg26845 ./1998/1998 USA Urlaub/06_20.jpg26599 ./1998/1998 USA Urlaub/02_48.jpg26778 ./1998/1998 USA Urlaub/05_17.jpg26859 ./1998/1998 USA Urlaub/05_35.jpg27129 ./1998/1998 USA Urlaub/06_49.jpg26956 ./1998/1998 USA Urlaub/06_19.jpg27082 ./1998/1998 USA Urlaub/05_34.jpg26717 ./1998/1998 USA Urlaub/06_17.jpg26613 ./1998/1998 USA Urlaub/06_07.jpg26299 ./1998/1998 USA Urlaub/04_35.jpg26183 ./1998/1998 USA Urlaub/07_29.jpg26506 ./1998/1998 USA Urlaub/06_12.jpg26782 ./1998/1998 USA Urlaub/08_45.jpg26376 ./1998/1998 USA Urlaub/06_35.jpg26339 ./1998/1998 USA Urlaub/06_37.jpg26446 ./1998/1998 USA Urlaub/07_27.jpg26872 ./1998/1998 USA Urlaub/05_33.jpg26116 ./1981 1982 Misc/00_27.jpg24842 EXPECTED RESULT No files with broken extension SOFTWARE/OS VERSIONS Linux/KDE Plasma: (available in About System) KDE Plasma Version: Using Gnome flashback, Ubuntu 18.04 KDE Frameworks Version: 5.61.0 Qt Version: 5.13.1 ADDITIONAL INFORMATION Total number of pictures: ~13000 The files with broken extension are not visible in digikam, but can be opend with other image viewers. Use this to fix: find . -name '*.jpg?????' -exec rename -v 's|(.*)\.jpg.....|$1.jpg|' {} \; One of the files above could not be renamed since its original version still existed. Checking the date/time showed the 00_27.jpg is time from running sync and the 00_27.jpg24842 is older. Looks like these jpg12345 are temp names and the cleanup failed at two stages.
Well, this type of TMP file does not come from digiKam directly, but should create Exiv2. Exiv2 has certainly issued an error message in the console. So, see if the problem is to reproduce with a small album and post the log here. And possibly also a file that fails. Original files may be read-only? Maik
digiKam 7.0.0 stable release is now published and now available as FlatPak: https://www.digikam.org/news/2020-07-19-7.0.0_release_announcement/ We need a fresh feedback on this file using this version. Thanks in advance Gilles Caulier
With next digiKam 7.4.0 release, AppImage bundle is compiled using a more recent Linux Mageia 7.1 host. Last stable Qt 5.15.2 and KF5 5.84 are used. ImageMagick codec 7 and libav 58 (ffmpeg) are used to supports extra image and video formats. https://i.imgur.com/XV1tZkL.png Please check if problem still reproducible with this version available as pre-release here: https://files.kde.org/digikam/ Gilles Caulier
Hi Dieter and happy new year, Can you check if problem remain with digiKam 7.5.0 pre-release bundle available here : https://files.kde.org/digikam/ Thanks in advance Gilles Caulier
@Dieter, Do you seen the comment #1 from Maik ? Gilles Caulier
Hi, I have not seen that behavior recently in new imports or other mass changes. I think this can be closed. Thanks, Dieter Fauth