Version: digikam-0.9.3-70.1 (using KDE 3.5.9) Installed from: SuSE RPMs OS: Linux When I download selected files from my memory card using digikam several files will not transfer and show up with a red X. The problem is that the photo that digikam tells me did not transfer is not the file that failed, the file that failed is the one before it. e.g. If I select photo-1 photo-2 photo-3 photo-4 for download this is the sort of thing that happens. photo-1 - Digikam shows completed transfer - File is transferred correctly photo-2 - Digikam shows completed transfer - Contents of file is actually photo-3 but has been named photo-2 photo-3 - Digikam shows failed transfer - File is actually been transferred named as photo-2 photo-4 - Digikam shows completed transfer - File is transferred correctly So photo-3 gets named photo-2 and photo-2 never gets transferred. As you might guess this makes it VERY confusing to work out which files have been transferred and which haven't. I have had this problem on openSUSE 10.3 and openSUSE 11.0. I have tried different card readers, different USB cables and different memory cards. There are no errors on the console other than complaining about Exif size for every file. I have used both the default exiv2 program and an updated SVN source build (exiv2 0.17.91) and both give the same error. >>> Warning: Directory Canon has an unhandled next pointer. Warning: Size 5352 of Exif.Canon.0x4002 exceeds 4096 bytes limit. Not decoded. >>> 5-10% of files will fail in this way every time I transfer photos. If I reselect the files with the red cross and the files before them and retranser with "overwrite all" then the transfer completes correctly. I have screen shots to show this happening.
Created attachment 25869 [details] Screen shots Here are some screen shots with explanations
Wasn't something like this recently fixed for the upcoming 0.9.4? (I only found http://bugs.kde.org/show_bug.cgi?id=159236). Maybe you could try to install the release candidate digiKam 0.9.4-rc1 (rc2 is about to come very soon), and check whether the issue remains? Best, Arnd
rc2 is already out: http://sourceforge.net/project/showfiles.php?group_id=42641 I have not prepared a blog entry yet, never done this before... :-) Maybe you, Arnd, want to volunteer?
To Arnd #2, Yes, i have already fixed this problem into 0.9.4. Gilles
Finn, are you able to compile 0.9.4-rc2 for SUSE? If so, is the problem still existing? If not we might close this one again...
Finn, What's news about this file ? It still valid using digiKam 0.9.4 ? Gilles Caulier
We need a fresh feedback here. Please use digiKam 0.10.0 for KDE4 and try again... Gilles Caulier
No response since a long time... Gilles Caulier
New digiKam 4.11.0 is available. https://www.digikam.org/node/740 Can you reproduce the problem with this release ? Gilles Caulier
With digiKam 5.0.0, this problem is not reproducible. I close this file now. Don't hesitate to re-open if necessary. Gilles Caulier