digiKam 8.4.0 is released

system · July 16, 2024, 3:52am

Dear digiKam fans and users, After five months of active maintenance and long bugs triage, the digiKam team is proud to present version 8.4.0 of its open source digital photo manager. Long time bugs present in older versions have been fixed and we spare a lot of time to contact users to validate changes in pre-release to confirm fixes before deploying the program in production. The application internationalization has also been updated.

This is a companion discussion topic for the original entry at https://www.digikam.org/news/2024-07-14-8.4.0_release_announcement/

dansroka · July 16, 2024, 12:23pm

Just to let you know, when I use the online version checker in Digicam 8.3, I get the following error message:

charlie84 · July 16, 2024, 12:59pm

On Mac M1 Sonoma the installation stops here.

Edit: Solved, installation completed in 5 minutes.

Per · July 17, 2024, 8:36am

Yeah, that’s Rosetta 2 taking a long time recompiling all the Intel code to ARM ahead of time.
That’s a good thing, but let’s hope that 8.5.0 will come as a native ARM Qt6 application.

charlie84 · July 17, 2024, 8:57am

Ok, thank you.

TorsteinO · July 22, 2024, 8:46pm

What are the differences between qt5 and qt6. Just wondering what file, I should download for Windows 11 with a Ryzen processor?

biokomiker_biokomike · July 23, 2024, 8:01pm

Thanks a lot - seems to work. But - for the first time ever - I have a problem with the Appimage laucher integration. I get this message:

Any clue?

journalctl:

> Jul 23 21:53:14 appimagelauncherd[5365]: Integrating: /home/xxxx/Applications/digiKam-8.4.0-Qt6-x86-64_97532ebe62ba5dabb5109d0c795a129c.appimage
> Jul 23 21:53:14 appimagelauncherd[5365]: WARNING: AppImage shall not be integrated, skipping
> Jul 23 21:53:14 appimagelauncherd[5365]: Cleaning up old desktop integration files
> Jul 23 21:53:14 appimagelauncherd[5365]: Updating desktop database and icon caches

dkdeveloper · July 24, 2024, 6:37am

There is a bug report in our bug tracker:

https://bugs.kde.org/show_bug.cgi?id=490657

And one in the AppImageLauncher bug tracker:

github.com/TheAssassin/AppImageLauncher

AppImageLauncher does not integrate Digikam 8.4.0 AppImage

opened 09:47AM - 23 Jul 24 UTC

rlfschmd

bug needs verification

### Pre-submit checks - [X] I [checked for similar issues](https://github.com/T…heAssassin/AppImageLauncher/issues?q=) beforehand, but could not find any, not even closed ones. I could not add my bug report to any existing issue. - [X] I am going to take the time to to fill in all the required details. I know that the bug report will be dismissed otherwise. ### Describe the bug Exceuting the 'Integrate to system and run' command when first clicking the AppImage moves the AppImage to the desired location but shows the error 'Failed to register AppImage in system via libappimage' after. The AppImage won't show in the menu and no .desktop file is created. Until Digikam 8.3.0 it all worked fine. The Digikam developers sent me here, since they are sure it is an AIL issue. Trying the integration via Terminal, I receive the following: ``` $ chmod a+x /home/xxxx/Applications/digiKam-8.4.0-Qt6-x86-64.appimage $ /home/rs/Applications/digiKam-8.4.0-Qt6-x86-64.appimage install AppImageLauncher error: appimage_shall_not_be_integrated() failed (returned -1) AppImageLauncher error: appimage_is_terminal_app() failed (returned -1) (process:5399): GLib-CRITICAL **: 10:03:35.339: g_file_test: assertion 'filename != NULL' failed (process:5399): GLib-CRITICAL **: 10:03:46.030: g_path_get_basename: assertion 'file_name != NULL' failed ** (process:5399): CRITICAL **: 10:03:46.030: Failed to find desktop file path ``` ### Expected behavior Exceuting the 'Integrate to system and run' command when first clicking the AppImage usually moves the AppImage to the desired location and saves an appropriate .desktop file to ~/.local/share/applications/. The app is launchabke from start menu then and behaves more lesse than any othe app. ### Steps to reproduce the issue 1. Execute the 'Integrate to system and run' command when first clicking the AppImage. ### Screenshots _No response_ ### Distribution and desktop environment Kubuntu 22.04 KDE Plasma Version: 5.27.11 KDE Frameworks Version: 5.104.0 Qt Version: 5.15.3 (Exactly the same issue happens on Mint 21.3) ### Installed AppImageLauncher version AppImageLauncher version 2.2.0 (git commit 0f91801), built on 2022-11-02 23:51:55 UTC ### List of AppImages you tried https://download.kde.org/stable/digikam/8.4.0/digiKam-8.4.0-Qt6-x86-64.appimage (not working) https://download.kde.org/stable/digikam/8.4.0/digiKam-8.4.0-Qt5-x86-64.appimage (not working) ### Additional context _No response_

nuno_cool · July 25, 2024, 4:55pm

I don’t manage to install any of the two windows versions digiKam-8.4.0-Qt5-Win64 and digiKam-8.4.0-Qt6-Win64 on Windows 11. However, it works on an Windows 10. When I click on the exe file, nothing happens.

dkdeveloper · July 25, 2024, 6:03pm

Probably an OpenGL graphics driver problem. Get a config file at this bug report:

https://bugs.kde.org/show_bug.cgi?id=489310#c1

and copy the “digikam_systemrc” into the appropriate directory:

C:\Users%USERNAME%\AppData\Local\

nuno_cool · July 25, 2024, 6:38pm

Thanks. Copied the digikam_systemrc into the folder but still it doesn’t install

dkdeveloper · July 25, 2024, 6:56pm

Did I understand correctly that the installer doesn’t work? I have no idea about that, you confirmed the security warning that you want to run digiKam? The warning appears on both Windows 10 and Windows 11 due to the missing signature. I just installed digiKam on a new Windows 11 installation without any problems. Which antivirus program do you use?

nuno_cool · July 25, 2024, 6:58pm

I use windows defender, but tried to turn it off. I don’t even get to that stage that I have to confirm the warning…

nuno_cool · July 25, 2024, 8:10pm

I managed by running the exe from the shell…

makosol · August 31, 2024, 5:36pm

Hi, i installed digikam 8.4 on Windows 10 but I have an error message about ExifTool not working correctly. Can you help me please ? thank you

Harri · September 1, 2024, 5:33am

Sounds familiar, I think I had the same problem. My solution was to install the executable version from exiftool.org (this worked on windows).

Later when doing something completely unrelated I noticed that there is an exiftool.exe in the digiKam installation folder, so there seems to be something wrong in the version of exiftool bundled with the digiKam installer.

makosol · September 1, 2024, 7:26am

Thanks ! it worked