<!DOCTYPE html><html><head>
<meta http-equiv="Content-Type" content="text/html; charset=utf-8">
</head>
<body>
Hey Maik,<br>
<br>
thanks! Just tested the latest build, which works as expected
without any issues.<br>
<br>
Best regards,<br>
Jan<br>
<br>
<div class="moz-cite-prefix">On 10/25/25 22:56, Maik Qualmann wrote:<br>
</div>
<blockquote type="cite" cite="mid:2203501.9o76ZdvQCi@linux.fritz.box">
<pre wrap="" class="moz-quote-pre">Please try the latest AppImage built from git/master, I am sure the issue is
resolved now, from here:
<a class="moz-txt-link-freetext" href="https://files.kde.org/digikam/">https://files.kde.org/digikam/</a>
Maik
Am Samstag, 25. Oktober 2025, 15:58:23 Mitteleuropäische Sommerzeit schrieb
Jan Wolter:
</pre>
<blockquote type="cite">
<pre wrap="" class="moz-quote-pre">Hi Maik,
thanks for the feedback. But even that does not help. No dgb session
were opened. After the 30 seconds count-down, the SegFault appears:
$ ./digiKam-8.8.0-Qt6-x86-64-debug.appimage 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"'. -- to extract the
bundle contents locally, use option '--appimage-extract' on the command
line. awk: read error (Is a directory)
awk: read error (Is a directory)
-- Detected host Linux LinuxMint-64-22
-- AppImage mounted directory: /tmp/.mount_digiKahNS6iO
Preloading skipped for libudev.so.0
Preloading /usr/lib/x86_64-linux-gnu/libxcb-dri3.so.0
Preloading skipped for libcrypto.so.1.1
Preloading skipped for libssl.so.1.1
Preloading /usr/lib/x86_64-linux-gnu/libnss3.so
Preloading /usr/lib/x86_64-linux-gnu/libnssutil3.so
Preloading /usr/lib/x86_64-linux-gnu/libsmime3.so
Preloading /usr/lib/x86_64-linux-gnu/libgmodule-2.0.so.0
Preloading skipped for libgnutls.so.30
Preloading /usr/lib/x86_64-linux-gnu/libnettle.so.8
-- Preloading shared libs:
:/usr/lib/x86_64-linux-gnu/libxcb-dri3.so.0:/usr/lib/x86_64-linux-gnu/libns
s3.so:/usr/lib/x86_64-linux-gnu/libnssutil3.so:/usr/lib/x86_64-linux-gnu/lib
smime3.so:/usr/lib/x86_64-linux-gnu/libgmodule-2.0.so.0:/usr/lib/x86_64-linu
x-gnu/libnettle.so.8 Starting delayed digiKam for remote debugging...
*Use 'bt' command on debugger prompt to get a crash backtrace. Use 'q'
command to quit debugger session.*
unknown: fromIccProfile: failed size sanity 2
unknown: fromIccProfile: failed size sanity 2
unknown: QSvgHandler: Image filename is empty
unknown: QSvgHandler: Image filename is empty
/tmp/.mount_digiKahNS6iO/AppRun: line 263: 22018 Segmentation fault
(core dumped) digikam ${@:2}
When I start it as root via "sudo
./digiKam-8.8.0-Qt6-x86-64-debug.appimage debug" it opens a "Welcome to
digiKam 8.8.0" dialog.
Could it be that there is any problem with my user? Nevertheless, all
previous dk versions works out quite well.
Best regards,
Jan
On 10/25/25 15:05, Maik Qualmann wrote:
</pre>
<blockquote type="cite">
<pre wrap="" class="moz-quote-pre">The downloaded debug app image is launched in a terminal with the debug
option.
For example:
./digiKam-8.8.0-20250719T191430-Qt6-x86-64.appimage debug
Maik
Am Samstag, 25. Oktober 2025, 14:53:13 Mitteleuropäische Sommerzeit
schrieb
Jan Wolter:
</pre>
<blockquote type="cite">
<pre wrap="" class="moz-quote-pre">Hello Gilles,
thanks for the fast response. But unfortunately, it does not work as
described in the how-to:
When I call "./squashfs-root/AppRun debug" it does not show within 30
seconds a command line to attach the debugger. Output is more or less
same as before:
$ ./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"'. -- to extract the
bundle contents locally, use option '--appimage-extract' on the command
line. awk: read error (Is a directory)
awk: read error (Is a directory)
-- Detected host Linux LinuxMint-64-22
-- AppImage mounted directory: /home/jan/tmp/digikam-8.8.0/squashfs-root
Preloading skipped for libudev.so.0
Preloading /usr/lib/x86_64-linux-gnu/libxcb-dri3.so.0
Preloading skipped for libcrypto.so.1.1
Preloading skipped for libssl.so.1.1
Preloading /usr/lib/x86_64-linux-gnu/libnss3.so
Preloading /usr/lib/x86_64-linux-gnu/libnssutil3.so
Preloading /usr/lib/x86_64-linux-gnu/libsmime3.so
Preloading /usr/lib/x86_64-linux-gnu/libgmodule-2.0.so.0
Preloading skipped for libgnutls.so.30
Preloading /usr/lib/x86_64-linux-gnu/libnettle.so.8
-- Preloading shared libs:
:/usr/lib/x86_64-linux-gnu/libxcb-dri3.so.0:/usr/lib/x86_64-linux-gnu/lib
:ns
s3.so:/usr/lib/x86_64-linux-gnu/libnssutil3.so:/usr/lib/x86_64-linux-gnu/
lib
smime3.so:/usr/lib/x86_64-linux-gnu/libgmodule-2.0.so.0:/usr/lib/x86_64-
linu x-gnu/libnettle.so.8 Starting delayed digiKam for remote
debugging... Use 'bt' command on debugger prompt to get a crash
backtrace.
Use 'q' command to quit debugger session.
unknown: fromIccProfile: failed size sanity 2
unknown: fromIccProfile: failed size sanity 2
unknown: QSvgHandler: Image filename is empty
unknown: QSvgHandler: Image filename is empty
./squashfs-root/AppRun: line 263: 18536 Segmentation fault (core
dumped) digikam ${@:2}
Instead I tested to run gdb as follows:
*$ gdb ./squashfs-root/usr/bin/digikam*
GNU gdb (Ubuntu 15.0.50.20240403-0ubuntu1) 15.0.50.20240403-git
Copyright (C) 2024 Free Software Foundation, Inc.
License GPLv3+: GNU GPL version 3 or
later<a class="moz-txt-link-rfc2396E" href="http://gnu.org/licenses/gpl.html"><http://gnu.org/licenses/gpl.html></a> 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:
<a class="moz-txt-link-rfc2396E" href="https://www.gnu.org/software/gdb/bugs/"><https://www.gnu.org/software/gdb/bugs/></a>.
Find the GDB manual and other documentation resources online at:
<a class="moz-txt-link-rfc2396E" href="http://www.gnu.org/software/gdb/documentation/"><http://www.gnu.org/software/gdb/documentation/></a>.
For help, type "help".
Type "apropos word" to search for commands related to "word"...
Reading symbols from ./squashfs-root/usr/bin/digikam...
*(gdb) run*
Starting program:
/home/jan/tmp/digikam-8.8.0/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".
warning: could not find '.gnu_debugaltlink' file for
/home/jan/tmp/digikam-8.8.0/squashfs-root/usr/lib64/libgphoto2.so.6
warning: could not find '.gnu_debugaltlink' file for
/home/jan/tmp/digikam-8.8.0/squashfs-root/usr/lib64/libgphoto2_port.so.12
warning: could not find '.gnu_debugaltlink' file for
/lib/x86_64-linux-gnu/libglib-2.0.so.0 warning: could not find
'.gnu_debugaltlink' file for
/home/jan/tmp/digikam-8.8.0/squashfs-root/usr/lib64/libicui18n.so.70
warning: could not find '.gnu_debugaltlink' file for
/home/jan/tmp/digikam-8.8.0/squashfs-root/usr/lib64/libicuuc.so.70
warning:
could not find '.gnu_debugaltlink' file for
/home/jan/tmp/digikam-8.8.0/squashfs-root/usr/lib64/libxslt.so.1 warning:
could not find '.gnu_debugaltlink' file for
/home/jan/tmp/digikam-8.8.0/squashfs-root/usr/lib64/libtheoraenc.so.1
warning: could not find '.gnu_debugaltlink' file for
/home/jan/tmp/digikam-8.8.0/squashfs-root/usr/lib64/libtheoradec.so.1
warning: could not find '.gnu_debugaltlink' file for
/home/jan/tmp/digikam-8.8.0/squashfs-root/usr/lib64/libcanberra.so.0
warning: could not find '.gnu_debugaltlink' file for
/home/jan/tmp/digikam-8.8.0/squashfs-root/usr/lib64/libpulse.so.0
warning:
could not find '.gnu_debugaltlink' file for
/home/jan/tmp/digikam-8.8.0/squashfs-root/usr/lib64/libplc4.so warning:
could not find '.gnu_debugaltlink' file for
/home/jan/tmp/digikam-8.8.0/squashfs-root/usr/lib64/libplds4.so warning:
could not find '.gnu_debugaltlink' file for
/home/jan/tmp/digikam-8.8.0/squashfs-root/usr/lib64/libpulsecommon-15.99.
so
[New Thread 0x7fffd8bff6c0 (LWP 18752)]
[New Thread 0x7fffd3fff6c0 (LWP 18753)]
qt.gui.icc: fromIccProfile: failed size sanity 2
qt.gui.icc: fromIccProfile: failed size sanity 2
warning: could not find '.gnu_debugaltlink' file for
/lib/x86_64-linux-gnu/libtinfo.so.6 [New Thread 0x7fffd09ff6c0 (LWP
18754)]
[New Thread 0x7fffbffff6c0 (LWP 18755)]
[New Thread 0x7fffbf7fe6c0 (LWP 18756)]
[New Thread 0x7fffbeffd6c0 (LWP 18757)]
[New Thread 0x7fffbe7fc6c0 (LWP 18758)]
[New Thread 0x7fffbdffb6c0 (LWP 18759)]
[New Thread 0x7fffbd7fa6c0 (LWP 18760)]
[New Thread 0x7fffbcff96c0 (LWP 18761)]
[New Thread 0x7fff9ffff6c0 (LWP 18762)]
[New Thread 0x7fff9f7fe6c0 (LWP 18763)]
[New Thread 0x7fff9effd6c0 (LWP 18764)]
[New Thread 0x7fff9e7fc6c0 (LWP 18765)]
[Thread 0x7fff9e7fc6c0 (LWP 18765) exited]
qt.svg: QSvgHandler: Image filename is empty
qt.svg: QSvgHandler: Image filename is empty
[New Thread 0x7fff9e7fc6c0 (LWP 18767)]
[New Thread 0x7fff9dffb6c0 (LWP 18768)]
[New Thread 0x7fff9d7fa6c0 (LWP 18769)]
[New Thread 0x7fff9cff96c0 (LWP 18770)]
[Detaching after vfork from child process 18771]
[Detaching after vfork from child process 18772]
[Detaching after vfork from child process 18773]
[Detaching after vfork from child process 18774]
[Detaching after vfork from child process 18775]
[Detaching after vfork from child process 18776]
[Detaching after vfork from child process 18777]
[Detaching after vfork from child process 18778]
[Detaching after vfork from child process 18779]
[Detaching after vfork from child process 18780]
[Detaching after vfork from child process 18781]
[Detaching after vfork from child process 18782]
[Detaching after vfork from child process 18783]
[Detaching after vfork from child process 18784]
[Detaching after vfork from child process 18785]
[Detaching after vfork from child process 18786]
qt.svg: QSvgHandler: Image filename is empty
qt.svg: QSvgHandler: Image filename is empty
qt.svg: QSvgHandler: Image filename is empty
qt.svg: QSvgHandler: Image filename is empty
qt.svg: QSvgHandler: Image filename is empty
qt.svg: QSvgHandler: Image filename is empty
qt.svg: QSvgHandler: Image filename is empty
qt.svg: QSvgHandler: Image filename is empty
qt.svg: QSvgHandler: Image filename is empty
qt.svg: QSvgHandler: Image filename is empty
qt.svg: QSvgHandler: Image filename is empty
qt.svg: QSvgHandler: Image filename is empty
[New Thread 0x7fff7ffff6c0 (LWP 18787)]
[Thread 0x7fff7ffff6c0 (LWP 18787) exited]
[Thread 0x7fff9cff96c0 (LWP 18770) exited]
[Thread 0x7fff9d7fa6c0 (LWP 18769) exited]
[Thread 0x7fff9dffb6c0 (LWP 18768) exited]
[Thread 0x7fff9e7fc6c0 (LWP 18767) exited]
[New Thread 0x7fff9dffb6c0 (LWP 18875)]
[New Thread 0x7fff9e7fc6c0 (LWP 18876)]
[New Thread 0x7fff7ffff6c0 (LWP 18877)]
[New Thread 0x7fff9cff96c0 (LWP 18878)]
[New Thread 0x7fff9d7fa6c0 (LWP 18880)]
[Thread 0x7fff9d7fa6c0 (LWP 18880) exited]
[Detaching after vfork from child process 18881]
[Detaching after vfork from child process 18882]
[Detaching after vfork from child process 18883]
[Detaching after vfork from child process 18884]
[Detaching after vfork from child process 18885]
[Detaching after vfork from child process 18886]
[Detaching after vfork from child process 18887]
[Detaching after vfork from child process 18888]
[Detaching after vfork from child process 18889]
[Detaching after vfork from child process 18890]
[Detaching after vfork from child process 18891]
[Detaching after vfork from child process 18892]
[Detaching after vfork from child process 18893]
[Detaching after vfork from child process 18894]
[Detaching after vfork from child process 18895]
[Detaching after vfork from child process 18896]
[Thread 0x7fff9cff96c0 (LWP 18878) exited]
[Thread 0x7fff7ffff6c0 (LWP 18877) exited]
[Thread 0x7fff9e7fc6c0 (LWP 18876) exited]
[Thread 0x7fff9dffb6c0 (LWP 18875) exited]
Within that call following window appears:
Clicking on "OK" has no effect, the windows remains as it is. The
mentioned location of the digikam DBs is correct.
What is meant with the configuration file in the red box?
My config files are located under ~/.config:
<a class="moz-txt-link-abbreviated" href="mailto:jan@Jans-Desktop:~/.config$">jan@Jans-Desktop:~/.config$</a> pwd
/home/jan/.config
<a class="moz-txt-link-abbreviated" href="mailto:jan@Jans-Desktop:~/.config$">jan@Jans-Desktop:~/.config$</a> ls -la digikam*
-rw-r--r-- 1 jan users 294 Dec 21 2024 digikam_oauthrc
-rw------- 1 jan users 85289 Oct 25 14:46 digikamrc
-rw-r--r-- 1 jan users 379 Oct 24 21:58 digikam_systemrc
-rw------- 1 jan users 22 Dec 21 2024 digikam_tagsmanagerrc
Can I provide you further information to nail down the problem?
Best regards,
Jan
On 10/25/25 13:37, Gilles Caulier wrote:
</pre>
<blockquote type="cite">
<pre wrap="" class="moz-quote-pre">Hi Jan,
Download the "-debug" suffixed appimage bundle that we provide and run
it in GDB as explained here :
<a class="moz-txt-link-freetext" href="https://www.digikam.org/contribute/#linux-host-using-gdb">https://www.digikam.org/contribute/#linux-host-using-gdb</a>
At end, list the GDB backtrace here for investigation.
Note : the both awk error at startup are suspect:
awk: read error (Is a directory)
awk: read error (Is a directory)
AppImage start through a bash script internally which can be viewed here
:
<a class="moz-txt-link-freetext" href="https://invent.kde.org/graphics/digikam/-/blob/master/project/bundles/ap">https://invent.kde.org/graphics/digikam/-/blob/master/project/bundles/ap</a>
pi
mage/data/AppRun?ref_type=heads
Best regards
Gilles Caulier
Le sam. 25 oct. 2025 à 13:22, Jan Wolter<a class="moz-txt-link-rfc2396E" href="mailto:jan@wolter.re"><jan@wolter.re></a> a écrit :
</pre>
<blockquote type="cite">
<pre wrap="" class="moz-quote-pre">Hello Gilles and Team,
I tested digiKam 8.8.0 on Linux Mint 22 (Wilma) and got following
Segmentation Fault (DK 8.7.0 works fine before):
$ ./digiKam-8.8.0-Qt6-x86-64.appimage
-- 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. awk: read error (Is a directory)
awk: read error (Is a directory)
-- Detected host Linux LinuxMint-64-22
-- AppImage mounted directory: /tmp/.mount_digiKa6qQ3nb
Preloading skipped for libudev.so.0
Preloading /usr/lib/x86_64-linux-gnu/libxcb-dri3.so.0
Preloading skipped for libcrypto.so.1.1
Preloading skipped for libssl.so.1.1
Preloading /usr/lib/x86_64-linux-gnu/libnss3.so
Preloading /usr/lib/x86_64-linux-gnu/libnssutil3.so
Preloading /usr/lib/x86_64-linux-gnu/libsmime3.so
Preloading /usr/lib/x86_64-linux-gnu/libgmodule-2.0.so.0
Preloading skipped for libgnutls.so.30
Preloading /usr/lib/x86_64-linux-gnu/libnettle.so.8
-- Preloading shared libs:
:/usr/lib/x86_64-linux-gnu/libxcb-dri3.so.0:/usr/lib/x86_64-linux-gnu/l
:i
bnss3.so:/usr/lib/x86_64-linux-gnu/libnssutil3.so:/usr/lib/x86_64-linux
-g
nu/libsmime3.so:/usr/lib/x86_64-linux-gnu/libgmodule-2.0.so.0:/usr/lib/
x8
6_64-linux-gnu/libnettle.so.8 unknown: fromIccProfile: failed size
sanity
2
unknown: fromIccProfile: failed size sanity 2
unknown: QSvgHandler: Image filename is empty
unknown: QSvgHandler: Image filename is empty
/tmp/.mount_digiKa6qQ3nb/AppRun: line 263: 6612 Segmentation fault
(core dumped) digikam $@
Could you please give me advice how to fix that problem?
Best regards,
Jan
On 10/19/25 12:36, Gilles Caulier wrote:
The digiKam development team is proud to release digiKam 8.8.0. For
more details, see announcement on digikam.org:
<a class="moz-txt-link-freetext" href="https://www.digikam.org/news/2025-10-19-8.8.0_release_announcement/">https://www.digikam.org/news/2025-10-19-8.8.0_release_announcement/</a>
Best regards
digiKam team
</pre>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
</blockquote>
<pre wrap="" class="moz-quote-pre">
</pre>
</blockquote>
</body>
</html>