The Linux Dbus service do not run on your system. This is why the low level libraries (qt) used in background by digiKam generate an exception.

Typically, digiKam do not use Dbus internal. It's only used to communicate with the desktop, or with other applications. For ex, Dbus is used (if available) to push a notification to the desktop, but it's optional. Under Windows and MacOS, Dbus do not exists and it's not a problem.

So check the Dbus service activity first.

Gilles Caulier

(In reply to caulier.gilles from comment #1)
> The Linux Dbus service do not run on your system. This is why the low level
> libraries (qt) used in background by digiKam generate an exception.
Yes, I've checked this. d-bus is not running. But why? Or better: What do I have to do to fix this?

> Typically, digiKam do not use Dbus internal. 
It seems to do as I have the error messages.

> It's only used to communicate
> with the desktop, or with other applications. For ex, Dbus is used (if
> available) to push a notification to the desktop, but it's optional. Under
> Windows and MacOS, Dbus do not exists and it's not a problem.
Hm, I didn't experience an issue so far, but this doesn't mean that there is none. If it's not a problem, then please remove the error messages.

> So check the Dbus service activity first.
> 
> Gilles Caulier
Thanks, I did. Maybe it's related to my specific setup on Windows?

You run Linux for Windows sub-system... we never try this yet...

The problem is not Windows at all, but Ubuntu services configuration. Start Ubuntu Dbus service and this must fix the problem.

http://manpages.ubuntu.com/manpages/bionic/man1/dbus-launch.1.html

Why not to use the native Windows version of digiKam instead AppImage ?

Gilles Caulier

I'm not even sure that the message come directly from digiKam. An "unknown: Failed enumerating UDisks2 objects:" message always precedes. It could possibly also come from the Solid API.

Maik

MAik,

It's sure : it do not come from digiKam, as i disable fully the dbus support in AppImage.

So all dbus trace come from Qt5 or KF5.

Gilles

(In reply to caulier.gilles from comment #3)
> You run Linux for Windows sub-system... we never try this yet...
> [snip]
> Why not to use the native Windows version of digiKam instead AppImage ?
> 
> Gilles Caulier

I have a Windows installation of digikam 6.4.0. I don't want to destroy this installation for just testing the new beta.

(In reply to caulier.gilles from comment #1)
> The Linux Dbus service do not run on your system. This is why the low level
> libraries (qt) used in background by digiKam generate an exception.
> 
> Typically, digiKam do not use Dbus internal. It's only used to communicate
> with the desktop, or with other applications. For ex, Dbus is used (if
> available) to push a notification to the desktop, but it's optional. Under
> Windows and MacOS, Dbus do not exists and it's not a problem.
> 
> So check the Dbus service activity first.
> 
> Gilles Caulier

Now I've started dbus before launching digikam.
``sudo /etc/init.d/dbus restart´´

The error messages related to dbus don't appear any longer.

Bute the following error messages remain:
user@machine:~$ ./digikam-7.0.0-beta2-1-x86-64/squashfs-root/AppRun
-- digiKam Linux AppImage Bundle
-- Use 'help' as CLI argument to know all available options for digiKam application.
-- Notes: to integrate this bundle to your desktop, use AppImageLauncher.
--        to enable all debug messages on the console, use 'export QT_LOGGING_RULES="digikam*=true"'.
libudev.so.0
-- Preloading shared libs:
[221:245:0222/093447.660666:ERROR:address_tracker_linux.cc(171)] Could not bind NETLINK socket: Address already in use (98)
QtAV 1.13.0(Jan 27 2020, 02:49:13)
Multimedia framework base on Qt and FFmpeg.
Distributed under the terms of LGPLv2.1 or later.
Shanghai, China Copyright (C) 2012-2019 Wang Bin (aka. Lucas Wang) wbsecg1@gmail.com
Donate: http://qtav.org/donate.html
Source: https://github.com/wang-bin/QtAV
Home page: http://qtav.org
unknown: Unhandled container to remove :  Digikam::DigikamApp
unknown: Uncaught SyntaxError: Invalid or unexpected token
unknown: Uncaught SyntaxError: Invalid or unexpected token
unknown: Uncaught SyntaxError: Invalid or unexpected token

Ok, now download the "-debug" version of AppImage bundle (largest file) and run it with "debug" argument on the command line to get a verbose backtrace from debugger.

I suspect that the Ubuntu Linux running in low level abstract layer on Windows is not able to start a GUI application or something like that.

Did you tried to run a simple text editor, just to see ?

Gilles Caulier

In this tutorial is explained : 

https://www.youtube.com/watch?v=ymV7j003ETA

1/ you need to install a X11 server on windows
2/ connect from the Windows to the WSL ubuntu over a SSH connection with X11 fowarding.

==> It's not simple !

So, GUI application cannot be run in native, and there is a more simpler way to test digiKam beta on Windows with to uninstall the production version:

1/ create a new "test" account on your Windows.
2/ Download the archive tarball of the binary version of digiKAm for Windows (aka digiKam-7.0.0-beta3-20200220T172843-Win64.tar.xz)
3/ uncompress the tarball on the test user home directory
4/ run the digikam.exe

Like this, you will not touch to the production settings and database. Of course you will start this version from scratch, but it will be safe

Gilles Caulier

(In reply to caulier.gilles from comment #9)
> In this tutorial is explained : 
> 
> https://www.youtube.com/watch?v=ymV7j003ETA
> 
> 1/ you need to install a X11 server on windows
> 2/ connect from the Windows to the WSL ubuntu over a SSH connection with X11
> fowarding.
> 
> ==> It's not simple !
> 
> So, GUI application cannot be run in native, and there is a more simpler way
> to test digiKam beta on Windows with to uninstall the production version:
> 
> 1/ create a new "test" account on your Windows.
> 2/ Download the archive tarball of the binary version of digiKAm for Windows
> (aka digiKam-7.0.0-beta3-20200220T172843-Win64.tar.xz)
> 3/ uncompress the tarball on the test user home directory
> 4/ run the digikam.exe
> 
> Like this, you will not touch to the production settings and database. Of
> course you will start this version from scratch, but it will be safe
> 
> Gilles Caulier

In general, the setup "Win10 + VxXsrv + Linux Subsystem + Ubuntu" works. Digikam starts, scans the folders etc.

There is just the flaw with dbus which is not started in this setup automatically, but which must be started manually. And the Windows drives which are not mounted utomatically, but mst be mounted manually. Let's see what else.

The option of "use a different Windows account" is not really a way forward. Rather, I'd prefer the tar-ball to contain a "Portable App". It should not use the standard "AppData" folders to store the basic configuration but should store it in a different folder.

(In reply to caulier.gilles from comment #8)
> Ok, now download the "-debug" version of AppImage bundle (largest file) and
> run it with "debug" argument on the command line to get a verbose backtrace
> from debugger.
> 
> I suspect that the Ubuntu Linux running in low level abstract layer on
> Windows is not able to start a GUI application or something like that.
The GUI starts despite the messages.

> 
> Did you tried to run a simple text editor, just to see ?
xeyes

> 
> Gilles Caulier

There is no "-debug" version in https://download.kde.org/unstable/digikam/
Where can I find it?

https://files.kde.org/digikam/

(In reply to caulier.gilles from comment #12)
> https://files.kde.org/digikam/

So, now I've got the debug version running.
Here is the output of the startup phase of digikam:

user@machine:~$ ./squashfs-root/AppRun debug
-- digiKam Linux AppImage Bundle
-- Use 'help' as CLI argument to know all available options for digiKam application.
-- Notes: to integrate this bundle to your desktop, use AppImageLauncher.
--        to enable all debug messages on the console, use 'export QT_LOGGING_RULES="digikam*=true"'.
libudev.so.0
libnss3.so
-- Preloading shared libs: :/home/thomas/squashfs-root/usr/lib64/libnss3.so
Starting digiKam into GDB...
Use 'bt' command on debugger prompt to get a crash backtrace.
Use 'q' command to quit debugger session.
GNU gdb (Ubuntu 8.1-0ubuntu3.2) 8.1.0.20180409-git
Copyright (C) 2018 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or later <http://gnu.org/licenses/gpl.html>
This is free software: you are free to change and redistribute it.
There is NO WARRANTY, to the extent permitted by law.  Type "show copying"
and "show warranty" for details.
This GDB was configured as "x86_64-linux-gnu".
Type "show configuration" for configuration details.
For bug reporting instructions, please see:
<http://www.gnu.org/software/gdb/bugs/>.
Find the GDB manual and other documentation resources online at:
<http://www.gnu.org/software/gdb/documentation/>.
For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from digikam...done.
Starting program: /home/thomas/squashfs-root/usr/bin/digikam
[Thread debugging using libthread_db enabled]
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[New Thread 0x7fffd7c80700 (LWP 128)]
[New Thread 0x7fffd4b80700 (LWP 129)]
[New Thread 0x7fffcfff0700 (LWP 130)]
[New Thread 0x7fffcf240700 (LWP 143)]
[Thread 0x7fffcf240700 (LWP 143) exited]
[New Thread 0x7fffcf240700 (LWP 145)]
[New Thread 0x7fffc0b20700 (LWP 146)]
[New Thread 0x7fffb7ff0700 (LWP 148)]
[New Thread 0x7fffb77e0700 (LWP 149)]
[New Thread 0x7fffb6fd0700 (LWP 150)]
[New Thread 0x7fffb67c0700 (LWP 151)]
[New Thread 0x7fffb5fb0700 (LWP 152)]
[New Thread 0x7fffb57a0700 (LWP 153)]
[New Thread 0x7fffb4f90700 (LWP 154)]
[124:151:0301/104402.143710:ERROR:address_tracker_linux.cc(171)] Could not bind NETLINK socket: Address already in use (98)
[New Thread 0x7fffa7ff0700 (LWP 155)]
[New Thread 0x7fffa77e0700 (LWP 156)]
[New Thread 0x7fffa6fd0700 (LWP 157)]
QtAV 1.13.0(Feb 24 2020, 04:10:10)
Multimedia framework base on Qt and FFmpeg.
Distributed under the terms of LGPLv2.1 or later.
Shanghai, China Copyright (C) 2012-2019 Wang Bin (aka. Lucas Wang) wbsecg1@gmail.com
Donate: http://qtav.org/donate.html
Source: https://github.com/wang-bin/QtAV
Home page: http://qtav.org
[New Thread 0x7fffa67c0700 (LWP 158)]
unknown: Unhandled container to remove :  Digikam::DigikamApp
[Thread 0x7fffb4f90700 (LWP 154) exited]
[New Thread 0x7fffb4f90700 (LWP 169)]
[New Thread 0x7fffa55a0700 (LWP 170)]
[Thread 0x7fffb77e0700 (LWP 149) exited]
[Thread 0x7fffb5fb0700 (LWP 152) exited]
[New Thread 0x7fffb5fb0700 (LWP 171)]
[New Thread 0x7fffb77e0700 (LWP 172)]
[New Thread 0x7fffa4d90700 (LWP 173)]
[New Thread 0x7fff7fff0700 (LWP 174)]
[New Thread 0x7fff7f7e0700 (LWP 175)]
[New Thread 0x7fff7efd0700 (LWP 176)]
[New Thread 0x7fff7e7c0700 (LWP 177)]
[New Thread 0x7fff7dfb0700 (LWP 178)]
[New Thread 0x7fff7d7a0700 (LWP 179)]
[Thread 0x7fffb4f90700 (LWP 169) exited]
[Thread 0x7fffb5fb0700 (LWP 171) exited]
[Thread 0x7fffa55a0700 (LWP 170) exited]
[Thread 0x7fffb77e0700 (LWP 172) exited]
[Thread 0x7fff7f7e0700 (LWP 175) exited]
[Thread 0x7fffa4d90700 (LWP 173) exited]
[New Thread 0x7fffa4d90700 (LWP 180)]
[New Thread 0x7fff7f7e0700 (LWP 181)]
[New Thread 0x7fffb77e0700 (LWP 182)]
[Thread 0x7fff7dfb0700 (LWP 178) exited]
[Thread 0x7fff7efd0700 (LWP 176) exited]
[Thread 0x7fff7fff0700 (LWP 174) exited]
[Thread 0x7fff7e7c0700 (LWP 177) exited]
[Thread 0x7fff7d7a0700 (LWP 179) exited]
[New Thread 0x7fff7d7a0700 (LWP 183)]
[New Thread 0x7fff7e7c0700 (LWP 184)]
[New Thread 0x7fff7fff0700 (LWP 185)]
[New Thread 0x7fff7efd0700 (LWP 186)]
unknown: Uncaught SyntaxError: Invalid or unexpected token
unknown: Uncaught SyntaxError: Unexpected end of input
unknown: Uncaught SyntaxError: Invalid or unexpected token
[Thread 0x7fff7d7a0700 (LWP 183) exited]
[Thread 0x7fffb67c0700 (LWP 151) exited]
[Thread 0x7fff7fff0700 (LWP 185) exited]
[Thread 0x7fff7efd0700 (LWP 186) exited]


Not much new information, and the program doesn't stop with a gdb prompt. 
Does the output mean something to you?
Is there somewhere a log file?

We never seen this before.

If GDB prompt do not appear, this want mean that digiKam go out without crash.

So, it miss something on your computer or something like that.

There is no specific log file. All is on the console.

You can try to enable all debug spaces from digiKam with this variable set before to run appimage :

export QT_LOGGING_RULES="digikam*=true"

Gilles Caulier

digiKam 7.0.0 stable release is now published:

https://www.digikam.org/news/2020-07-19-7.0.0_release_announcement/

We need a fresh feedback on this file using this version.

Best Regards

Gilles Caulier

*** Bug 429793 has been marked as a duplicate of this bug. ***

With next digiKam 7.4.0 release, AppImage bundle is compiled using a more recent Linux Mageia 7.1 host. Last stable Qt 5.15.2 and KF5 5.84 are used. ImageMagick codec 7 and libav 58 (ffmpeg) are used to supports extra image and video formats.

https://i.imgur.com/XV1tZkL.png

Please check if problem still reproducible with this version available as pre-release here:

https://files.kde.org/digikam/

Gilles Caulier

Stable digiKam 7.4.0 AppImage is published. Please check if problem is
reproducible.

Thanks in advance

Hi,

We need a fresh feedback here, especially using current 7.5.0 pre-release AppImage :

https://files.kde.org/digikam/

... and if possible under Windows 11, which improve the WSL with GUI application support.

Thanks in advance and happy new year

Best

Gilles Caulier

Sorry, my computer isn't fit for Win11...

On Win10, I had issues recently suing the appimage. Although QT
libraries are contained in the image, the app didn't start with "QT lib
not found". :-(

Am 01.01.2022 um 15:45 schrieb bugzilla_noreply@kde.org:
> https://bugs.kde.org/show_bug.cgi?id=417885
>
> --- Comment #19 from caulier.gilles@gmail.com ---
> Hi,
>
> We need a fresh feedback here, especially using current 7.5.0 pre-release
> AppImage :
>
> https://files.kde.org/digikam/
>
> ... and if possible under Windows 11, which improve the WSL with GUI
> application support.
>
> Thanks in advance and happy new year
>
> Best
>
> Gilles Caulier
>

Can you provide a full trace of appimage bundle startup from the console ?

(In reply to caulier.gilles from comment #21)
> Can you provide a full trace of appimage bundle startup from the console ?

Fresh download of https://files.kde.org/digikam/digiKam-7.5.0-20211231T102525-x86-64-debug.appimage

```
$ ./digiKam-7.5.0-20211231T102525-x86-64-debug.appimage --appimage-extract
[...]

$ ./squashfs-root/AppRun
-- digiKam Linux AppImage Bundle
-- Use 'help' as CLI argument to know all available options for digiKam application.
-- Notes: to integrate this bundle to your desktop, use AppImageLauncher.
--        to enable all debug messages on the console, use 'export QT_LOGGING_RULES="digikam*=true"'.
Check library libudev.so.0
Check library libxcb-dri3.so.0
Check library libcrypto.so.1.1
Check library libssl.so.1.1
-- Preloading shared libs: :/usr/lib/x86_64-linux-gnu/libxcb-dri3.so.0:/usr/lib/x86_64-linux-gnu/libcrypto.so.1.1:/usr/lib/x86_64-linux-gnu/libssl.so.1.1
digikam: error while loading shared libraries: libQt5Core.so.5: cannot open shared object file: No such file or directory

$ ll /usr/lib/x86_64-linux-gnu/libxcb-dri3.so.0
lrwxrwxrwx 1 root root 20 Mar 27  2020 /usr/lib/x86_64-linux-gnu/libxcb-dri3.so.0 -> libxcb-dri3.so.0.0.0

$ ll /usr/lib/x86_64-linux-gnu/libcrypto.so.1.1
-rw-r--r-- 1 root root 2954080 Nov 24 14:20 /usr/lib/x86_64-linux-gnu/libcrypto.so.1.1

$ ll /usr/lib/x86_64-linux-gnu/libssl.so.1.1
-rw-r--r-- 1 root root 598104 Nov 24 14:20 /usr/lib/x86_64-linux-gnu/libssl.so.1.1
```

>digikam: error while loading shared libraries: libQt5Core.so.5: cannot open shared object file: No such file or directory

==> this library come from the AppImage bundle, decompressed in memory ... Very starnge

Gilles Caulier

Yes, and it is there, decompressed in the squash-fs folder.

It is not missing, just not found - maybe related to my installation?


Am 01.01.2022 um 18:02 schrieb bugzilla_noreply@kde.org:
> https://bugs.kde.org/show_bug.cgi?id=417885
>
> --- Comment #23 from caulier.gilles@gmail.com ---
>> digikam: error while loading shared libraries: libQt5Core.so.5: cannot open shared object file: No such file or directory
> ==> this library come from the AppImage bundle, decompressed in memory ... Very
> starnge
>
> Gilles Caulier
>

I don't understand why this do not work.

In your decompressed appimage content, go to the Qt5 library file and run ldd like this 

[gilles@localhost lib]$ pwd 
/tmp/.mount_digiKafKsuVU/usr/lib

[gilles@localhost lib]$ ll libQt5Core.so.5 
-rwxr-xr-x 1 root root 6715872 Jan  1 19:50 libQt5Core.so.5*

[gilles@localhost lib]$ ldd libQt5Core.so.5 
        linux-vdso.so.1 (0x00007fff1cf29000)
        libpthread.so.0 => /lib64/libpthread.so.0 (0x00007f61ff4cc000)
        libzstd.so.1 => /lib64/libzstd.so.1 (0x00007f61ff3f1000)
        libdl.so.2 => /lib64/libdl.so.2 (0x00007f61ff3ec000)
        libgthread-2.0.so.0 => /lib64/libgthread-2.0.so.0 (0x00007f61ff3e7000)
        libglib-2.0.so.0 => /lib64/libglib-2.0.so.0 (0x00007f61ff2bb000)
        libstdc++.so.6 => /lib64/libstdc++.so.6 (0x00007f61ff0eb000)
        libm.so.6 => /lib64/libm.so.6 (0x00007f61fefa6000)
        libgcc_s.so.1 => /lib64/libgcc_s.so.1 (0x00007f61fef8c000)
        libc.so.6 => /lib64/libc.so.6 (0x00007f61fedd2000)
        /lib64/ld-linux-x86-64.so.2 (0x00007f61ffb81000)
        libpcre.so.1 => /lib64/libpcre.so.1 (0x00007f61fed60000)

Note : this is mine from the last AppImage bundle 7.5.0 : digiKam-7.5.0-20220101T175533-x86-64.appimage

GilleS Caulier

Looks all okay-ish:

```

$ pwd
/home/thomas/squashfs-root/usr/lib

$ ll libQt5Core.so.5
-rwxr-xr-x 1 thomas thomas 6715872 Jan  1 17:39 libQt5Core.so.5*

$ ldd libQt5Core.so.5
         linux-vdso.so.1 (0x00007fffd922b000)
         libpthread.so.0 => /lib/x86_64-linux-gnu/libpthread.so.0
(0x00007f9575bcd000)
         libzstd.so.1 => /lib/x86_64-linux-gnu/libzstd.so.1
(0x00007f9575b20000)
         libdl.so.2 => /lib/x86_64-linux-gnu/libdl.so.2 (0x00007f9575b10000)
         libgthread-2.0.so.0 =>
/lib/x86_64-linux-gnu/libgthread-2.0.so.0 (0x00007f9575b00000)
         libglib-2.0.so.0 => /lib/x86_64-linux-gnu/libglib-2.0.so.0
(0x00007f95759d0000)
         libstdc++.so.6 => /lib/x86_64-linux-gnu/libstdc++.so.6
(0x00007f95757e0000)
         libm.so.6 => /lib/x86_64-linux-gnu/libm.so.6 (0x00007f9575681000)
         libgcc_s.so.1 => /lib/x86_64-linux-gnu/libgcc_s.so.1
(0x00007f9575660000)
         libc.so.6 => /lib/x86_64-linux-gnu/libc.so.6 (0x00007f9575460000)
         /lib64/ld-linux-x86-64.so.2 (0x00007f957627c000)
         libpcre.so.3 => /lib/x86_64-linux-gnu/libpcre.so.3
(0x00007f95753e0000)

```


Am 01.01.2022 um 20:24 schrieb bugzilla_noreply@kde.org:
> https://bugs.kde.org/show_bug.cgi?id=417885
>
> --- Comment #25 from caulier.gilles@gmail.com ---
> I don't understand why this do not work.
>
> In your decompressed appimage content, go to the Qt5 library file and run ldd
> like this
>
> [gilles@localhost lib]$ pwd
> /tmp/.mount_digiKafKsuVU/usr/lib
>
> [gilles@localhost lib]$ ll libQt5Core.so.5
> -rwxr-xr-x 1 root root 6715872 Jan  1 19:50 libQt5Core.so.5*
>
> [gilles@localhost lib]$ ldd libQt5Core.so.5
>          linux-vdso.so.1 (0x00007fff1cf29000)
>          libpthread.so.0 => /lib64/libpthread.so.0 (0x00007f61ff4cc000)
>          libzstd.so.1 => /lib64/libzstd.so.1 (0x00007f61ff3f1000)
>          libdl.so.2 => /lib64/libdl.so.2 (0x00007f61ff3ec000)
>          libgthread-2.0.so.0 => /lib64/libgthread-2.0.so.0 (0x00007f61ff3e7000)
>          libglib-2.0.so.0 => /lib64/libglib-2.0.so.0 (0x00007f61ff2bb000)
>          libstdc++.so.6 => /lib64/libstdc++.so.6 (0x00007f61ff0eb000)
>          libm.so.6 => /lib64/libm.so.6 (0x00007f61fefa6000)
>          libgcc_s.so.1 => /lib64/libgcc_s.so.1 (0x00007f61fef8c000)
>          libc.so.6 => /lib64/libc.so.6 (0x00007f61fedd2000)
>          /lib64/ld-linux-x86-64.so.2 (0x00007f61ffb81000)
>          libpcre.so.1 => /lib64/libpcre.so.1 (0x00007f61fed60000)
>
> Note : this is mine from the last AppImage bundle 7.5.0 :
> digiKam-7.5.0-20220101T175533-x86-64.appimage
>
> GilleS Caulier
>

Hi all,

What's about the 7.9.0 pre-release available here :

https://files.kde.org/digikam/

Problem still reproducible ?

Thanks in advance

Gilles Caulier

(In reply to caulier.gilles from comment #27)
> Hi all,
> 
> What's about the 7.9.0 pre-release available here :
> 
> https://files.kde.org/digikam/
> 
> Problem still reproducible ?
> 
> Thanks in advance
> 
> Gilles Caulier

Yes, sorry.
I still have htis problem.
Still all the same symptoms... :-(
I don't paste the output again, it's just the same.

Got everything freshly updated to latest:
Win10 + WSL + Ubuntu + VcXsrv
Digikam 7.9.0 64 bit app image

Hi all,

digiKam 8.0.0 is out. This entry still valid with this release ?

Best regards

Gilles Caulier

(In reply to caulier.gilles from comment #29)
> Hi all,
> 
> digiKam 8.0.0 is out. This entry still valid with this release ?
> 
> Best regards
> 
> Gilles Caulier

Unfortunately no change:

$ ./digiKam-8.0.0-x86-64/squashfs-root/AppRun
-- digiKam Linux AppImage Bundle
-- Use 'help' as CLI argument to know all available options for digiKam application.
-- Notes: to integrate this bundle to your desktop, use AppImageLauncher.
--        to enable all debug messages on the console, use 'export QT_LOGGING_RULES="digikam*=true"'.
--        to extract the bundle contents locally, use option '--appimage-extract' on the command line.
-- Detected host Linux ubuntu-64-22.4
-- AppImage mounted directory: /home/thomas/digiKam-8.0.0-x86-64/squashfs-root
Check library libudev.so.0
Check library libxcb-dri3.so.0
Check library libcrypto.so.1.1
Check library libssl.so.1.1
Check library libnss3.so
Check library libnssutil3.so
Check library libsmime3.so
Check library libgmodule-2.0.so.0
-- Preloading shared libs: :/home/thomas/digiKam-8.0.0-x86-64/squashfs-root/usr/lib/libavif.so.13:/usr/lib/x86_64-linux-gnu/libxcb-dri3.so.0:/usr/lib/x86_64-linux-gnu/libnss3.so:/usr/lib/x86_64-linux-gnu/libnssutil3.so:/usr/lib/x86_64-linux-gnu/libsmime3.so:/usr/lib/x86_64-linux-gnu/libgmodule-2.0.so.0
digikam: error while loading shared libraries: libQt5Core.so.5: cannot open shared object file: No such file or directory

Please try the Linix AppImage bundle pre-release 8.2.0 avaialble here :

https://files.kde.org/digikam/

This one is now ported to last Qt 5.15.11

Gilles Caulier

(In reply to caulier.gilles from comment #31)
> Please try the Linix AppImage bundle pre-release 8.2.0 avaialble here :
> 
> https://files.kde.org/digikam/
> 
> This one is now ported to last Qt 5.15.11
> 
> Gilles Caulier

There must be something wrong with my WSL2 / Ubuntu installation...
I don't get it working, still the same error with libQt5Core not found.

I guess this use case isn't worth spending more efforts, so you may close the ticket as "won't fix".