Bug 466363

Please start the appimage from a console with "debug" argument as explained here :

https://www.digikam.org/contribute/

Gilles Caulier

Sorry! Debug below:

./digiKam-7.9.0-x86-64.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.
-- Detected host Linux -64-
-- AppImage mounted directory: /tmp/.mount_digiKaRKnfkr
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: :/tmp/.mount_digiKaRKnfkr/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
Starting digiKam into GDB...
Use 'bt' command on debugger prompt to get a crash backtrace.
Use 'q' command to quit debugger session.
/tmp/.mount_digiKaRKnfkr/AppRun: line 183: gdb: command not found

gdb is the gnu debugger. install it on your system before

Aha. Ok - installed it and re-ran, the output: 

./digiKam-7.9.0-x86-64.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.
-- Detected host Linux -64-
-- AppImage mounted directory: /tmp/.mount_digiKaK8aoyC
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: :/tmp/.mount_digiKaK8aoyC/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
Starting digiKam into GDB...
Use 'bt' command on debugger prompt to get a crash backtrace.
Use 'q' command to quit debugger session.
GNU gdb (Debian 12.1-4+b1) 12.1
Copyright (C) 2022 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:
<https://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...
(No debugging symbols found in digikam)
Starting program: /tmp/.mount_digiKaK8aoyC/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 0x7fffbc1ff6c0 (LWP 132701)]
[New Thread 0x7fffbb5ff6c0 (LWP 132702)]
[New Thread 0x7fffb27ff6c0 (LWP 132704)]
[New Thread 0x7fffb1ffe6c0 (LWP 132705)]
[New Thread 0x7fffb17fd6c0 (LWP 132706)]
[New Thread 0x7fffb0ffc6c0 (LWP 132707)]
[New Thread 0x7fffa4dff6c0 (LWP 132708)]
[New Thread 0x7fff8ffff6c0 (LWP 132709)]
[New Thread 0x7fff87fff6c0 (LWP 132710)]
[New Thread 0x7fff8f7fe6c0 (LWP 132711)]
[New Thread 0x7fff8effd6c0 (LWP 132712)]
[New Thread 0x7fff8e7fc6c0 (LWP 132713)]
[New Thread 0x7fff8dffb6c0 (LWP 132714)]
[New Thread 0x7fff8d7fa6c0 (LWP 132715)]
[New Thread 0x7fff8cff96c0 (LWP 132716)]
[New Thread 0x7fff877fe6c0 (LWP 132717)]
[New Thread 0x7fff86ffd6c0 (LWP 132718)]
[New Thread 0x7fff867fc6c0 (LWP 132719)]
[New Thread 0x7fff85ffb6c0 (LWP 132720)]

Thread 1 "digikam" received signal SIGSEGV, Segmentation fault.
__strlen_avx2 () at ../sysdeps/x86_64/multiarch/strlen-avx2.S:76
76	../sysdeps/x86_64/multiarch/strlen-avx2.S: No such file or directory.
(gdb)

After the crash you have to type "bt" + enter for the backtrace.

Maik

We are getting there! :-) 
Now with backtrace: 


./digiKam-7.9.0-x86-64.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.
-- Detected host Linux -64-
-- AppImage mounted directory: /tmp/.mount_digiKamWVPvz
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: :/tmp/.mount_digiKamWVPvz/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
Starting digiKam into GDB...
Use 'bt' command on debugger prompt to get a crash backtrace.
Use 'q' command to quit debugger session.
GNU gdb (Debian 12.1-4+b1) 12.1
Copyright (C) 2022 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:
<https://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...
(No debugging symbols found in digikam)
Starting program: /tmp/.mount_digiKamWVPvz/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 0x7fffbc1ff6c0 (LWP 133345)]
[New Thread 0x7fffbb5ff6c0 (LWP 133346)]
[New Thread 0x7fffb27ff6c0 (LWP 133348)]
[New Thread 0x7fffb1ffe6c0 (LWP 133349)]
[New Thread 0x7fffb17fd6c0 (LWP 133350)]
[New Thread 0x7fffb0ffc6c0 (LWP 133351)]
[New Thread 0x7fffa4dff6c0 (LWP 133352)]
[New Thread 0x7fff97fff6c0 (LWP 133353)]
[New Thread 0x7fff977fe6c0 (LWP 133354)]
[New Thread 0x7fff96ffd6c0 (LWP 133355)]
[New Thread 0x7fff967fc6c0 (LWP 133356)]
[New Thread 0x7fff95ffb6c0 (LWP 133357)]
[New Thread 0x7fff957fa6c0 (LWP 133358)]
[New Thread 0x7fff94ff96c0 (LWP 133359)]
[New Thread 0x7fff6bfff6c0 (LWP 133360)]
[New Thread 0x7fff6b7fe6c0 (LWP 133361)]
[New Thread 0x7fff63fff6c0 (LWP 133362)]
[New Thread 0x7fff6affd6c0 (LWP 133363)]
[New Thread 0x7fff6a7fc6c0 (LWP 133364)]

Thread 1 "digikam" received signal SIGSEGV, Segmentation fault.
__strlen_avx2 () at ../sysdeps/x86_64/multiarch/strlen-avx2.S:76
76	../sysdeps/x86_64/multiarch/strlen-avx2.S: No such file or directory.
(gdb) bt
#0  __strlen_avx2 () at ../sysdeps/x86_64/multiarch/strlen-avx2.S:76
#1  0x00007ffff29354f0 in QByteArray::QByteArray(char const*, int) ()
   from /tmp/.mount_digiKamWVPvz/usr/lib/libQt5Core.so.5
#2  0x00007fffbaa09175 in ?? ()
   from /tmp/.mount_digiKamWVPvz/usr/plugins/xcbglintegrations/libqxcb-glx-integration.so
#3  0x00007fffbaa0a654 in ?? ()
   from /tmp/.mount_digiKamWVPvz/usr/plugins/xcbglintegrations/libqxcb-glx-integration.so
#4  0x00007fffbaa07ee7 in ?? ()
   from /tmp/.mount_digiKamWVPvz/usr/plugins/xcbglintegrations/libqxcb-glx-integration.so
#5  0x00007fffbea3ea22 in QXcbIntegration::createPlatformOpenGLContext(QOpenGLContext*) const () from /tmp/.mount_digiKamWVPvz/usr/lib/libQt5XcbQpa.so.5
#6  0x00007ffff3367b8f in QOpenGLContext::create() ()
   from /tmp/.mount_digiKamWVPvz/usr/lib/libQt5Gui.so.5
#7  0x00007fffe2d20f1e in QtWebEngineCore::initialize() ()
   from /tmp/.mount_digiKamWVPvz/usr/lib/libQt5WebEngineCore.so.5
#8  0x00007ffff2ad96a7 in QCoreApplicationPrivate::init() ()
   from /tmp/.mount_digiKamWVPvz/usr/lib/libQt5Core.so.5
#9  0x00007ffff331bb0f in QGuiApplicationPrivate::init() ()
   from /tmp/.mount_digiKamWVPvz/usr/lib/libQt5Gui.so.5
#10 0x00007ffff3d63849 in QApplicationPrivate::init() ()
--Type <RET> for more, q to quit, c to continue without paging--
   from /tmp/.mount_digiKamWVPvz/usr/lib/libQt5Widgets.so.5
#11 0x0000555555404673 in ?? ()
#12 0x00007ffff6a4618a in __libc_start_call_main (
    main=main@entry=0x555555404540, argc=argc@entry=1, 
    argv=argv@entry=0x7fffffffd668)
    at ../sysdeps/nptl/libc_start_call_main.h:58
#13 0x00007ffff6a46245 in __libc_start_main_impl (main=0x555555404540, argc=1, 
    argv=0x7fffffffd668, init=<optimized out>, fini=<optimized out>, 
    rtld_fini=<optimized out>, stack_end=0x7fffffffd658)
    at ../csu/libc-start.c:381
#14 0x000055555540627a in ?? ()
(gdb)

It crash in Qt XCB plugin used to deal with X11 extension to render on screen. Did you use Wayland instead X11 ?

(In reply to caulier.gilles from comment #7)
> It crash in Qt XCB plugin used to deal with X11 extension to render on
> screen. Did you use Wayland instead X11 ?

Yes, I ran loginctl

SESSION  UID USER    SEAT  TTY 
      2 1000 andreas seat0 tty2

 and then 

loginctl show-session 2 -p Type" 

and it says 

Type=wayland

It's the default in Debian, I didn't change anything about this.

@Andreas,

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

Best regards

Gilles Caulier

Created attachment 158677 [details]
Screenshot from 2023-05-04 07-35-07.png

Hi Gilles - thanks for checking. 

I can't check whether it works in 8.0.0 via the default repositories because Debian Bookworm is still with package 7.9.0: https://packages.debian.org/bookworm/digikam

I tried to install 7.9.0 now and I can open the app. Perhaps other packages in Bookworm were updated and so 7.9.0 works better on Debian Bookworm (from Digikam about page: "Build date: 13/01/2023 07:08 (target: Debian)")

However: 7.9.0 has serious UI issues. It looks much better and is more stable than the Flathub version, but displays similar random "twitches" to Flathub 8.0.0 version - see below, triggering these seems random: (Screenshot from 2023-05-04 07-50-10.png) and (Screenshot from 2023-05-04 07-51-15.png)



I installed 8.0.0 via Flathub just now to check it out as well - https://flathub.org/en-GB/apps/org.kde.digikam

The Flathub version can start on Debian Bookworm but has many UI issues. For example, in Flathub version when I open Settings and close it  the app will (often) start to look funny (Screenshot from 2023-05-04 07-38-02.png). 

The contrasts will be a bit off always on buttons (Screenshot from 2023-05-04 07-35-07.png) or the app will go blank (Screenshot from 2023-05-04 07-37-30.png). I can't tie this to any particular thing I'm doing, it could be browsing photos or changing settings.

Another experience of the Flathub version for me was that it crashed quite often for no reason. For example on 8.0.0, it crashes when I try to switch the colour scheme. 

I tried Flathub earlier mostly on Ubuntu 20.04 LTS and it had too many issues to be usable. It seems the issues are the same for the Debian Flathub version. 

Usually the version from Ubuntu repositories didn't have so many issues and worked well, but now the Debian repository version displays similar issues (but a bit less) than the Flathub version. 

Thanks!
Andreas 


3 May 2023, 1:31 pm by bugzilla_noreply@kde.org:

> https://bugs.kde.org/show_bug.cgi?id=466363
>
> --- Comment #9 from caulier.gilles@gmail.com ---
> @Andreas,
>
> digiKam 8.0.0 is out. This entry still valid with this release ?
>
> Best regards
>
> Gilles Caulier
>
> -- 
> You are receiving this mail because:
> You reported the bug.
>

Created attachment 158678 [details]
Screenshot from 2023-05-04 07-37-30.png

Created attachment 158679 [details]
Screenshot from 2023-05-04 07-38-02.png

Created attachment 158680 [details]
Screenshot from 2023-05-04 07-50-10.png

Created attachment 158681 [details]
Screenshot from 2023-05-04 07-51-15.png

Andreas,

This issue is not for Flatpak or Snap bundles, it's for "AppImage"

Forget flatpak and snap, there are sand-boxed and mostly unusable with complex application as digiKam.

Try the AppImage bundle that WE (digiKam team) provide and support officially.

The 8.0.0 files are available here :

https://download.kde.org/stable/digikam/8.0.0/digiKam-8.0.0-x86-64.appimage.mirrorlist

How to run? it's very very simple :

https://docs.digikam.org/en/getting_started/installation.html#digikam-on-linux

Best

Gilles Caulier

Created attachment 158682 [details]
attachment-1365594-0.html

Ah yes, now I remember (and read the subject line) :-)

I just tried to download the appimage and run and it works perfectly so far. 

This is great - thank you!

4 May 2023, 8:17 am by bugzilla_noreply@kde.org:

> https://bugs.kde.org/show_bug.cgi?id=466363
>
> --- Comment #15 from caulier.gilles@gmail.com ---
> Andreas,
>
> This issue is not for Flatpak or Snap bundles, it's for "AppImage"
>
> Forget flatpak and snap, there are sand-boxed and mostly unusable with complex
> application as digiKam.
>
> Try the AppImage bundle that WE (digiKam team) provide and support officially.
>
> The 8.0.0 files are available here :
>
> https://download.kde.org/stable/digikam/8.0.0/digiKam-8.0.0-x86-64.appimage.mirrorlist
>
> How to run? it's very very simple :
>
> https://docs.digikam.org/en/getting_started/installation.html#digikam-on-linux
>
> Best
>
> Gilles Caulier
>
> -- 
> You are receiving this mail because:
> You reported the bug.
>