Bug 494115 - DigiKam crash during startup (SIGILL)
Summary: DigiKam crash during startup (SIGILL)
Status: RESOLVED NOT A BUG
Alias: None
Product: digikam
Classification: Applications
Component: Portability-Runtime (show other bugs)
Version: 8.2.0
Platform: Kubuntu Linux
: NOR crash
Target Milestone: ---
Assignee: Digikam Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2024-10-04 14:09 UTC by Michal Kec (MiK)
Modified: 2024-10-05 16:39 UTC (History)
2 users (show)

See Also:
Latest Commit:
Version Fixed In: 8.5.0
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Michal Kec (MiK) 2024-10-04 14:09:18 UTC
SUMMARY
Since I've upgraded my Kubuntu from 22.04 to 24.04 LTS, digiKam won't start.

STEPS TO REPRODUCE
1. konsole
2. export QT_LOGGING_RULES="digikam*=true"
3. digikam

OBSERVED RESULT
Illegal instruction (SIGILL)

EXPECTED RESULT
digiKam app started

SOFTWARE/OS VERSIONS
Operating System: Kubuntu 24.04
KDE Plasma Version: 5.27.11
KDE Frameworks Version: 5.115.0
Qt Version: 5.15.13
Kernel Version: 6.8.0-45-generic (64-bit)
Graphics Platform: X11
Processors: 2 × Intel® Core™2 Duo CPU T7500 @ 2.20GHz
Memory: 3.8 GiB of RAM
Graphics Processor: NV84
Manufacturer: Hewlett-Packard
Product Name: HP Compaq 8710w
System Version: F.0F

ADDITIONAL INFORMATION
Every start emits following syslog entry: kernel: traps: digikam[11339] trap invalid opcode ip:7bdba18e91a0 sp:7fff5c8e5a98 error:0 in libdigikamcore.so.8.2.0[7bdba1088000+97e000]
DigiKam installed via APT, deb version 4:8.2.0-0ubuntu6.2.
Bug is valid for recent 6.8 kernels as well as for previous kernel 5.15.
Comment 1 Maik Qualmann 2024-10-04 14:46:33 UTC
Please create a GDB backtrace:

gdb digikam
type "r" + enter for run
crash...
type "bt" + enter for backtrace -> post backtrace

Maik
Comment 2 Michal Kec (MiK) 2024-10-04 15:07:31 UTC
Hello Maik, thanks for reaching out. I've followed your instructions and this is the output. Is this the backtrace you wanted?

Program received signal SIGILL, Illegal instruction.
0x00007b4ba96e91a0 in ?? () from /usr/lib/digikam/libdigikamcore.so.8.2.0
(gdb) bt
#0  0x00007b4ba96e91a0 in ?? () from /usr/lib/digikam/libdigikamcore.so.8.2.0
#1  0x00007b4ba8f8907b in ?? () from /usr/lib/digikam/libdigikamcore.so.8.2.0
#2  0x00007b4baa8ab71f in call_init (l=<optimized out>, argc=argc@entry=1, argv=argv@entry=0x7ffe07db7a78, env=env@entry=0x7ffe07db7a88) at ./elf/dl-init.c:74
#3  0x00007b4baa8ab824 in call_init (env=<optimized out>, argv=<optimized out>, argc=<optimized out>, l=<optimized out>) at ./elf/dl-init.c:120
#4  _dl_init (main_map=0x7b4baa8df2e0, argc=1, argv=0x7ffe07db7a78, env=0x7ffe07db7a88) at ./elf/dl-init.c:121
#5  0x00007b4baa8c55a0 in _dl_start_user () from /lib64/ld-linux-x86-64.so.2
#6  0x0000000000000001 in ?? ()
#7  0x00007ffe07db8c8f in ?? ()
#8  0x0000000000000000 in ?? ()
(gdb)
Comment 3 caulier.gilles 2024-10-04 17:09:05 UTC
Hi, 

There is no debug symbols to identify where is the problem.

Please try the 8.5.0 pre-release AppImage bundle for Linux available here :

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

Best

Gilles Caulier
Comment 4 Maik Qualmann 2024-10-04 18:53:46 UTC
Hmm, even without debug you would at least see a backtrace. Here it looks like the loading of the digiKam library fails. We also have an "illegal instruction" abort. Are you sure that you have installed a digiKam version that matches your processor architecture?

Maik
Comment 5 Michal Kec (MiK) 2024-10-05 09:14:54 UTC
Hello, the application is installed directly from the Ubuntu repo during the dist-upgrade. The entire OS is amd64 and so is the application architecture.

AppImages of the 8.5.0 pre-release works without any issues.

Maybe some other optimization that Canonical puts in their debs? I am aware that the CPU on this laptop is not modern.
Comment 6 caulier.gilles 2024-10-05 16:38:45 UTC
No ideas about the Ubuntu packaging. You needs to report this UPSTREAM problem to the Ubuntu packagers.

Best

Gilles Caulier