Bug 471310

Summary: digiKam 8.1.0 Win64 Nightly build fails to folderize imported PNG & HEIC files
Product: [Applications] digikam Reporter: Judah Richardson <judahrichardson>
Component: Import-PostProcessingAssignee: Digikam Developers <digikam-bugs-null>
Status: RESOLVED FIXED    
Severity: normal CC: caulier.gilles, metzpinguin
Priority: NOR    
Version First Reported In: 8.1.0   
Target Milestone: ---   
Platform: Microsoft Windows   
OS: Microsoft Windows   
Latest Commit: Version Fixed/Implemented In: 8.1.0
Sentry Crash Report:

Description Judah Richardson 2023-06-21 21:52:11 UTC
SUMMARY
***
NOTE: If you are reporting a crash, please try to attach a backtrace with debug symbols.
See https://community.kde.org/Guidelines_and_HOWTOs/Debugging/How_to_create_useful_crash_reports
***


STEPS TO REPRODUCE
1. Install the nightly build as a normal, non-admin user on Windows 10 x64 21H2
2. Assemble source folder containing JPG, PNG, and HEIC files
3. Attempt to import the above via Import -> Add Images...
4. In the import Settings, request folderization via ISO standard

OBSERVED RESULT

All files will be imported, but only the JPGs will be folderized.

EXPECTED RESULT

All files should be imported and folderized.
SOFTWARE/OS VERSIONS
Windows: 10 21H2
macOS: 
Linux/KDE Plasma: 
(available in About System)
KDE Plasma Version: 
KDE Frameworks Version: 
Qt Version: 

ADDITIONAL INFORMATION
Comment 1 caulier.gilles 2023-06-22 03:45:22 UTC
Where did you take the Windows installer exactly ?
Comment 2 Maik Qualmann 2023-06-22 06:06:34 UTC
Git commit 1143bd77e92364a96f2ad66da9170697c29d5b0e by Maik Qualmann.
Committed on 22/06/2023 at 06:05.
Pushed by mqualmann into branch 'master'.

fallback to file time for images without Exif creation date
FIXED-IN: 8.1.0

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

https://invent.kde.org/graphics/digikam/-/commit/1143bd77e92364a96f2ad66da9170697c29d5b0e
Comment 3 Judah Richardson 2023-06-22 14:20:37 UTC
(In reply to caulier.gilles from comment #1)
> Where did you take the Windows installer exactly ?

From the Nightly builds page you previously linked me to on a different bug ;) https://binary-factory.kde.org/view/Windows%2064-bit/job/Digikam_Nightly_win64/ I chose the Nightly build as the regular release needs admin permissions for installation on Windows, and I don't have admin permissions on the affected PC.
Comment 4 Maik Qualmann 2023-06-22 17:12:03 UTC
The Nightly build from https://binary-factory.kde.org is a pure test version and not recommended for productive use. Although this version has a valid signature due to the compilation with the MSVC compiler and the KDE infrastructure.. But it is a fully automatic build with many missing functions. No HEIF or JPEG2000 support, no MySQL support and much more.

We strongly recommend using digiKam from here: https://files.kde.org/digikam/

The defender message can be ignored, there was a problem with users who downloaded the debug version not starting. The problem is solved and the debug version is not needed for log messages.

Maik
Comment 5 Judah Richardson 2023-06-22 17:29:01 UTC
(In reply to Maik Qualmann from comment #4)
> The Nightly build from https://binary-factory.kde.org is a pure test version
> and not recommended for productive use. Although this version has a valid
> signature due to the compilation with the MSVC compiler and the KDE
> infrastructure.. But it is a fully automatic build with many missing
> functions. No HEIF or JPEG2000 support, no MySQL support and much more.
> 
> We strongly recommend using digiKam from here: https://files.kde.org/digikam/
> 
> The defender message can be ignored, there was a problem with users who
> downloaded the debug version not starting. The problem is solved and the
> debug version is not needed for log messages.
> 
> Maik

Thanks Maik, but as I said the problem with the builds you linked to is they require admin authority on the target PC for installation.

Is there any way to install them under non-admin permissions, perhaps to %appdata% instead?
Comment 6 Judah Richardson 2023-06-22 17:31:31 UTC
Ah nvm. I just realized the folder you linked to has portable builds in it. So I'll just have to manually install it to my user folder. Thanks for the details!
Comment 7 Judah Richardson 2023-06-22 17:41:54 UTC
Aaaack. Now I can't uninstall the Nightly build due to https://bugs.kde.org/show_bug.cgi?id=470391

*sigh*
Comment 8 Maik Qualmann 2023-06-22 17:50:48 UTC
Yes, unfortunately another problem of the Nightly version. It doesn't work even after a reboot. We have limited control over how the installer is configured in this build.
Since we don't write anything in Windows or in the registry (the installer creates a path), simply delete the directory, which is probably not easy to do without admin rights.

Maik
Comment 9 Judah Richardson 2023-06-22 19:33:52 UTC
No worries, I was able to find and kill the orphan process using Process Explorer. I've switched to portable digiKam release now. It appears to support HEIC files as you promised. I'll see how the next import attempt goes. Thanks!
Comment 10 Maik Qualmann 2023-06-22 19:37:24 UTC
However, the current version from 06/18/2023 does not yet contain the fix from your bug report.

Maik
Comment 11 Judah Richardson 2023-06-22 19:48:03 UTC
You said "yet", so I'm optimistic. Cautiously, haha.
Comment 12 Judah Richardson 2023-08-02 18:14:45 UTC
(In reply to Judah Richardson from comment #9)
> No worries, I was able to find and kill the orphan process using Process
> Explorer. I've switched to portable digiKam release now. It appears to
> support HEIC files as you promised. I'll see how the next import attempt
> goes. Thanks!

So I tried importing a few JPGs into the portable stable 8.1.0 version of digiKam just now and folderization failed there too despite the ISO standard option being checked. Any ideas?
Comment 13 Judah Richardson 2023-08-02 18:15:11 UTC
Reopening this ...
Comment 14 Judah Richardson 2023-08-02 18:25:50 UTC
False alarm: was using a portable nightly build and not the stable build as I'd thought. Stable build doesn't have the issue.