[Pkg-kde-extras] Bug#1042376: digikam crashes with "Illegal instruction"

[Detlef Matthiessen]

   Hi Steve,

   I'm afraid, it doesn't prevent digikam from crashing.

   Here is what I did (after fetching the latest updates from "testing" this morning):

root at fluke:/etc/apt# sed -i 's/trixie/sid/' sources.list
root at fluke:/etc/apt# apt-get update
Get:1 http://ftp.de.debian.org/debian sid InRelease [210 kB]
(...)

root at fluke:/etc/apt# apt-get install digikam
(...)
The following additional packages will be installed:
   digikam-data digikam-private-libs
Suggested packages:
   digikam-doc
The following packages will be upgraded:
   digikam digikam-data digikam-private-libs
3 upgraded, 0 newly installed, 0 to remove and 212 not upgraded.
Need to get 19.2 MB of archives.
After this operation, 2,048 B disk space will be freed.
Do you want to continue? [Y/n]
Get:1 http://ftp.de.debian.org/debian sid/main amd64 digikam amd64 4:8.1.0-3 [100 kB]
Get:2 http://ftp.de.debian.org/debian sid/main amd64 digikam-private-libs amd64 4:8.1.0-3 [9,949 kB]
Get:3 http://ftp.de.debian.org/debian sid/main amd64 digikam-data all 4:8.1.0-3 [9,121 kB]
Fetched 19.2 MB in 2s (12.0 MB/s)
Reading changelogs... Done
(Reading database ... 475773 files and directories currently installed.)
Preparing to unpack .../digikam_4%3a8.1.0-3_amd64.deb ...
Unpacking digikam (4:8.1.0-3) over (4:8.1.0-2+b1) ...
Preparing to unpack .../digikam-private-libs_4%3a8.1.0-3_amd64.deb ...
Unpacking digikam-private-libs (4:8.1.0-3) over (4:8.1.0-2+b1) ...
Preparing to unpack .../digikam-data_4%3a8.1.0-3_all.deb ...
Unpacking digikam-data (4:8.1.0-3) over (4:8.1.0-2) ...
Setting up digikam-private-libs (4:8.1.0-3) ...
Setting up digikam-data (4:8.1.0-3) ...
Setting up digikam (4:8.1.0-3) ...
(...)

dm at fluke:~$ digikam
Illegal instruction
dm at fluke:~$ export DEBUGINFOD_URLS="https://debuginfod.debian.net"
dm at fluke:~$ gdb digikam
(...)
Program received signal SIGILL, Illegal instruction.
0x00007ffff6cc2103 in operator* (m1=..., m2=...) at /usr/include/x86_64-linux-gnu/qt5/QtGui/qmatrix4x4.h:642
642	        QMatrix4x4 m = m1;
(gdb) bt
#0  0x00007ffff6cc2103 in operator* (m1=..., m2=...) at /usr/include/x86_64-linux-gnu/qt5/QtGui/qmatrix4x4.h:642
#1  0x00007ffff65b861d in __static_initialization_and_destruction_0 () at ./core/libs/video/qtav/utils/ColorTransform.cpp:59
#2  0x00007ffff7fcfe2e in call_init (env=0x7fffffffe0b8, argv=0x7fffffffe0a8, argc=1, l=<optimized out>) at ./elf/dl-init.c:70
#3  call_init (l=<optimized out>, argc=1, argv=0x7fffffffe0a8, env=0x7fffffffe0b8) at ./elf/dl-init.c:26
#4  0x00007ffff7fcff14 in _dl_init (main_map=0x7ffff7ffe2c0, argc=1, argv=0x7fffffffe0a8, env=0x7fffffffe0b8) at ./elf/dl-init.c:117
#5  0x00007ffff7fe5170 in _dl_start_user () from /lib64/ld-linux-x86-64.so.2
#6  0x0000000000000001 in ?? ()
#7  0x00007fffffffe3d4 in ?? ()
#8  0x0000000000000000 in ?? ()

   Not sure if my approach is the preferred way to test something across different branches, though. I didn't want to switch my entire system to "sid" (this is my main machine, after all :) ). Hope that's OK. If there's a better way of testing your version, please let me know.

   I'm willing to repeat the test once 8.1.0-3 lands in "testing" although I'm not expecting the result to be different.

   Cheers,

     Detlef