Summary: | No visible images in target folder after import from SD card | ||
---|---|---|---|
Product: | [Applications] digikam | Reporter: | Rafael Linux User <rafael.linux.user> |
Component: | Import-UMS | Assignee: | Digikam Developers <digikam-bugs-null> |
Status: | RESOLVED FIXED | ||
Severity: | normal | CC: | caulier.gilles, metzpinguin, rafael.linux.user |
Priority: | NOR | ||
Version First Reported In: | 8.1.0 | ||
Target Milestone: | --- | ||
Platform: | openSUSE | ||
OS: | Linux | ||
Latest Commit: | https://invent.kde.org/graphics/digikam/-/commit/567d795e1409a28d635ffd9e3b2dae41eb727c1e | Version Fixed In: | 8.3.0 |
Sentry Crash Report: |
Description
Rafael Linux User
2023-12-23 21:22:00 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 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 (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. I mean "rename string" 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 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 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 Really I don't remember to change that, so I'll check tonight in "Configuration, Camera" section, where I presume could be changed. Rafael, I will rebuild the AppImage this morning. Gilles 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 I confirm that I selected "Personalized" but didn't put any parameter. Thank you for you quick fix!!! |