Bug 478954 - No visible images in target folder after import from SD card
Summary: No visible images in target folder after import from SD card
Status: RESOLVED FIXED
Alias: None
Product: digikam
Classification: Applications
Component: Import-UMS (show other bugs)
Version: 8.1.0
Platform: openSUSE Linux
: NOR normal
Target Milestone: ---
Assignee: Digikam Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2023-12-23 21:22 UTC by Rafael Linux User
Modified: 2023-12-27 17:58 UTC (History)
3 users (show)

See Also:
Latest Commit:
Version Fixed In: 8.3.0
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Rafael Linux User 2023-12-23 21:22:00 UTC
SUMMARY
After importing images from an SD card of my Panasonic Lumix camera from Digikam, Digikam does not show the imported files in the destination folder. However, if I go into the destination folder with the file manager, the JPG files appear with different names from the camera originals. All images have been renamed. The names of the original images are preceded with the text "Camera-asINHu-f4689986.digikamtempfile.P1013811_v1.JPG" (in this case, the original image name was "P1013811.JPG".

This happens every time I import from the card. Some time ago this didn't happen, everything worked fine.


STEPS TO REPRODUCE
1. Insert SD card in my SD card reader
2. Launch Digikam and click on "Import, USB Stick Lumix" button in toolbar
3. Select 1 or more photos
4. Click "Download selection" button in toolbar
5. After Digikam finish, destination folder is showed, but images doesn't appear (no thumbnails at all)

OBSERVED RESULT
The imported images are in destination folder, but names are all changed.

EXPECTED RESULT
To show thumbnails of imported images with their original names.

SOFTWARE/OS VERSIONS
Operating System: openSUSE Tumbleweed 20231222
KDE Plasma Version: 5.27.10
KDE Frameworks Version: 5.113.0
Qt Version: 5.15.11
Kernel Version: 6.6.6-1-default (64-bit)
Graphics Platform: Wayland
Processors: 24 × AMD Ryzen 9 3900X 12-Core Processor
Memory: 31.3 GiB of RAM

ADDITIONAL INFORMATION
Imported photos are viewable with any other image viewer (like Gwenview).

This is an example of imported files renamed by Digikam (not visible by Digikam after imported)
Camera-asINHu-f4689986.digikamtempfile.P1013811_v1.JPG
Camera-bfEnbp-aab80cf7.digikamtempfile.P1013821_v1.JPG
Camera-buliuJ-509a2658.digikamtempfile.P1013803_v1.JPG
Camera-dmcwoS-40666d0d.digikamtempfile.P1013794_v1.JPG
Camera-dmzAdf-fa7b2035.digikamtempfile.P1013819_v1.JPG
Camera-GrbHjG-f94be021.digikamtempfile.P1013809_v1.JPG
Camera-iguiTl-0a9ee8af.digikamtempfile.P1013813_v1.JPG
Camera-LHvIdr-21de74ac.digikamtempfile.P1013816_v1.JPG
Camera-mLcALG-fc00b276.digikamtempfile.P1013795_v1.JPG
Camera-pZgWWP-7d515c58.digikamtempfile.P1013804_v1.JPG
Camera-RaWLyM-29597c12.digikamtempfile.P1013820_v1.JPG
Camera-rDfuKP-62c24358.digikamtempfile.P1013792_v1.JPG
Camera-ZGHpDx-8e02493b.digikamtempfile.P1013808_v1.JPG
Comment 1 Maik Qualmann 2023-12-23 22:29:28 UTC
A test here with digiKam-8.2.0/8.3.0 shows no problems when importing via SD card reader. A test with auto creation of date and/or extension based folders also works.

What are your exact settings in the import tool? Especially the renaming settings. A debug log from the terminal from an import would also help.

Maik
Comment 2 Maik Qualmann 2023-12-24 07:36:28 UTC
Another note: The fact that the files do not appear in digiKam is not a bug; the addition of the extension ".digikamtempfile" means they are ignored by the item scanner. This is to ensure that files in the process of being created are not captured by the scanner and scan invalid metadata.
So something went wrong with the renaming. Therefore I need your rename string. However, there were already bug fixes compared to digiKam-8.1.0, so it is also possible that the problem has already been resolved.

Maik
Comment 3 Rafael Linux User 2023-12-26 00:44:36 UTC
(In reply to Maik Qualmann from comment #2)
> Another note: The fact that the files do not appear in digiKam is not a bug;
> the addition of the extension ".digikamtempfile" means they are ignored by
> the item scanner. This is to ensure that files in the process of being
> created are not captured by the scanner and scan invalid metadata.
> So something went wrong with the renaming. Therefore I need your rename
> string. However, there were already bug fixes compared to digiKam-8.1.0, so
> it is also possible that the problem has already been resolved.
> 
> Maik

What do you mean with "my rename scan". Those names I pasted was created by Digikam. I can access, copy and view same images from that SD with Dolphin and Gwenview. I didn't change anything in import tool and not used any renaming tool neither.
Comment 4 Rafael Linux User 2023-12-26 00:45:20 UTC
I mean "rename string"
Comment 5 Maik Qualmann 2023-12-26 08:09:12 UTC
Git commit 567d795e1409a28d635ffd9e3b2dae41eb727c1e by Maik Qualmann.
Committed on 26/12/2023 at 09:08.
Pushed by mqualmann into branch 'master'.

fix item import if rename fails
FIXED-IN: 8.3.0

M  +1    -1    NEWS
M  +5    -0    core/utilities/import/main/importui.cpp

https://invent.kde.org/graphics/digikam/-/commit/567d795e1409a28d635ffd9e3b2dae41eb727c1e
Comment 6 Rafael Linux User 2023-12-26 08:30:49 UTC
I imagine it was some specific bug related to some kind of card readers, cause I didn't have that issue previously some months ago. SD card remain same, but I think last time without issues I imported directly from camera (I'm not sure). 

I'll test with your AppImage when ready.

Thank you for your quick fix!!!

Have a Merry Christmas
Comment 7 Maik Qualmann 2023-12-26 08:44:19 UTC
You set a custom rename in the import settings, which fails.
I was able to reproduce this particular case here. Because their temporary files had the _v1 extension, it became clear to me where the problem was occurring.

Maik
Comment 8 Rafael Linux User 2023-12-26 09:02:50 UTC
Really I don't remember to change that, so I'll check tonight in "Configuration, Camera" section, where I presume could be changed.
Comment 9 caulier.gilles 2023-12-26 09:12:18 UTC
Rafael,

I will rebuild the AppImage this morning.

Gilles
Comment 10 Maik Qualmann 2023-12-26 10:06:21 UTC
Not in the camera settings, directly in the settings of the Import Tool window in the renaming section. The problem also occurred if you only activated the checkbox for custom renaming and left the renaming string empty.

Maik
Comment 11 Rafael Linux User 2023-12-27 17:58:43 UTC
I confirm that I selected "Personalized" but didn't put any parameter.

Thank you for you quick fix!!!