SUMMARY: see $SUBJECT. Console output when starting appimage and choosing "Integrate and start application": $ ./digiKam-8.5.0-20240908T100120-Qt6-x86-64-debug.appimage ERROR: appimage_shall_not_be_integrated : Entry doesn't exists: org.kde.digikam.desktop AppImageLauncher error: appimage_shall_not_be_integrated() failed (returned -1) ERROR: appimage_is_terminal_app : Entry doesn't exists: org.kde.digikam.desktop AppImageLauncher error: appimage_is_terminal_app() failed (returned -1) ERROR: appimage_register_in_system : Entry doesn't exists: org.kde.digikam.desktop There is no more logging even with export QT_LOGGING_RULES="digikam*=true". Also, double clicking the appimage freezes the complete desktop (Wayland) for >10 seconds until the appimage starts. This started happening some versions ago somewhere in July (I think). I don't remember the exact build, unfortunately. Other appimages integrate correctly, e.g. Subsurface https://subsurface-divelog.org/current-release/ (scroll all the way down for the appimage) which seems to be a showcase app for the Appimage concept. So this does not seem to be a KDE Neon bug. STEPS TO REPRODUCE 1. Download appimage x86-64 with or without debug enabled) 2. Start it in KDE Neon 3. Choose "Integrate and start" when asked OBSERVED RESULT Error see above. The appimage is moved to ~/Applications though, so part of the integration actually happens. EXPECTED RESULT Appimage should integrate and start. SOFTWARE/OS VERSIONS: KDE Neon 6.1 22.04 (x86_64), digikam 8.5 2024-09-08 Appimage,
This could be a problem with the AppImageLauncher, see Bug 490657. If you start the AppImage without integration in a terminal, does it run without problems? Maik
It works, but none of the apps that Digikam tries to start will launch. For example, Firefox (browser) to report bugs, or "open in file manager" context menu item, all do nothing. If I run them in the console I get something like this: Dolphin: unknown: No language dictionaries for the language: "en_US" unknown: Could not find the Qt platform plugin "wayland" in "" /usr/bin/dolphin: symbol lookup error: /usr/bin/dolphin: undefined symbol: _ZN11KIconEffect10toDisabledER7QPixmap Firefox: unknown: Could not find the Qt platform plugin "wayland" in "" XPCOMGlueLoad error for file /usr/lib/firefox/libnss3.so: /usr/lib/x86_64-linux-gnu/libnssutil3.so: version `NSSUTIL_3.101' not found (required by /usr/lib/firefox/libnss3.so) Couldn't load XPCOM. All apps run normally when *not* started from within Digikam. This may be a library preloading issue. Can we fix this for the Appimage?
Try the Qt5 AppImage from here: https://files.kde.org/digikam/legacy/ Maik
*** Bug 492836 has been marked as a duplicate of this bug. ***
Qt5 appimage shows the same issue when starting or integrating. But starting apps from within Digikam - e.g. Dolphin file manager or Firefox or VLC - works here, as opposed to in the Qt6 version. However, the Qt5 build does not have the KDE styling.
*** Bug 493578 has been marked as a duplicate of this bug. ***
Git commit c6233799319bab43efcc055a7631a10512206bef by Maik Qualmann. Committed on 24/09/2024 at 17:38. Pushed by mqualmann into branch 'master'. remove application desktop files for a test M +2 -2 project/bundles/appimage/04-build-appimage.sh https://invent.kde.org/graphics/digikam/-/commit/c6233799319bab43efcc055a7631a10512206bef
(In reply to Maik Qualmann from comment #8) > Git commit c6233799319bab43efcc055a7631a10512206bef by Maik Qualmann. > Committed on 24/09/2024 at 17:38. > Pushed by mqualmann into branch 'master'. > > remove application desktop files for a test > > M +2 -2 project/bundles/appimage/04-build-appimage.sh > > https://invent.kde.org/graphics/digikam/-/commit/ > c6233799319bab43efcc055a7631a10512206bef see my last comment in https://bugs.kde.org/show_bug.cgi?id=493578 it might help
Hi, digiKam 8.5.0. is out with many fixes and improvements. https://www.digikam.org/news/2024-11-16-8.5.0_release_announcement/ This report still valid with this version? Thanks in advance Gilles Caulier
With the December 3rd release of Digikam pre-8.6.0, this again worked today on my machine. Integration went as planned. Thank you :-)