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

            Bug ID: 502003
           Summary: digiKam exits abruptly when attempting to open help
    Classification: Applications
           Product: digikam
           Version: 8.6.0
          Platform: Solus
                OS: Linux
            Status: REPORTED
          Severity: crash
          Priority: NOR
         Component: Setup-FirstRun
          Assignee: digikam-bugs-n...@kde.org
          Reporter: signup+...@anthonymcook.com
  Target Milestone: ---

SUMMARY

STEPS TO REPRODUCE
1. Start digiKam-8.6.0-Qt6-x86-64.appimage
2. In the setup wizard, click the "Help" button

OBSERVED RESULT

A black window briefly appears and the application "crashes".

According to GDB this is not technically a crash, but an erroneous exit:

MESA-LOADER: failed to open nouveau: ././/lib/dri/nouveau_dri.so: cannot open
shared object file: No such file or directory (search paths
././/lib/x86_64-linux-gnu/dri:\$${ORIGIN}/dri:././/lib/dri, suffix _dri)
MESA-LOADER: failed to open zink: ././/lib/dri/zink_dri.so: cannot open shared
object file: No such file or directory (search paths
././/lib/x86_64-linux-gnu/dri:\$${ORIGIN}/dri:././/lib/dri, suffix _dri)
MESA-LOADER: failed to open kms_swrast: ././/lib/dri/kms_swrast_dri.so: cannot
open shared object file: No such file or directory (search paths
././/lib/x86_64-linux-gnu/dri:\$${ORIGIN}/dri:././/lib/dri, suffix _dri)
MESA-LOADER: failed to open swrast: ././/lib/dri/swrast_dri.so: cannot open
shared object file: No such file or directory (search paths
././/lib/x86_64-linux-gnu/dri:\$${ORIGIN}/dri:././/lib/dri, suffix _dri)
[Inferior 1 (process 11469) exited with code 01]

EXPECTED RESULT

Help should be displayed.

SOFTWARE/OS VERSIONS
Linux Distro: Solus
Linux Kernel: 6.12.19-315.current #1 SMP PREEMPT_DYNAMIC 2025-03-14 x86_64
GNU/Linux
GlibC: version: 2.41
QT: 6 (according to appimage)

ADDITIONAL INFORMATION

I also tested it with the official Solus package and the same issue occurred. 

I just tested on Debian and is also exits erroneously there, although in GDB
there are no messages printed when it terminates, just the process exit line
itself.

So this is a cross-distro issue with the package in general.

-- 
You are receiving this mail because:
You are watching all bug changes.

Reply via email to