Hi. I’m using fedora 42 installed on a small x86_64 tablet and last week I noticed that discover is not opening anymore. Trying to opening through terminal it just shows “Illegal instruction (core dumped)”.
The system is fully updated and searching on google it seems it’s related to some missing instruction that my CPU don’t have. I’ve found this case that looks like similar: 465548 – digiKam crashes with illegal instruction on AMD Athlon II due to SSE detection with CMake
I also tried to follow the same steps and found this:
Thread 1 “plasma-discover” received signal SIGILL, Illegal instruction.
0x00007fffc079eb55 in lcevc_dec::decoder::Pool<lcevc_dec::decoder::Decoder>::Pool(unsigned long) () from /lib64/liblcevc_dec_api.so.3
Missing rpms, try: dnf --enablerepo=‘debug’ install kf6-kio-core-libs-debuginfo-6.13.0-2.fc42.switcheroo.x86_64 kf6-kio-file-widgets-debuginfo-6.13.0-2.fc42.switcheroo.x86_64 kf6-kio-widgets-libs-debuginfo-6.13.0-2.fc42.switcheroo.x86_64 kf6-kio-gui-debuginfo-6.13.0-2.fc42.switcheroo.x86_64 libavformat-debuginfo-7.1.1-1.fc42.x86_64 libavcodec-debuginfo-7.1.1-1.fc42.x86_64 libavutil-debuginfo-7.1.1-1.fc42.x86_64 openh264-debuginfo-2.4.1-2.fc42.x86_64 librtmp-debuginfo-2.6^20240301git6f6bb13-1.fc42.x86_64 libswresample-debuginfo-7.1.1-1.fc42.x86_64 LCEVCdec-debuginfo-3.3.5-1.fc42.x86_64 davs2-libs-debuginfo-1.7-1.20220903gitb41cf11.fc42.x86_64 uavs3d-libs-debuginfo-1.2.0-4.20230223git1fd0491.fc42.x86_64 vvenc-libs-debuginfo-1.12.1-1.fc42.x86_64 x264-bootstrap-libs-debuginfo-0.0.164-15.20231001git31e19f92_bootstrap.fc42.x86_64 x265-libs-debuginfo-4.1-1.fc42.x86_64 libxavs-debuginfo-0.1.55-1.fc42.x86_64 xavs2-libs-debuginfo-1.4-1.20190422giteae1e8b.fc42.x86_64 kvazaar-libs-debuginfo-2.3.1-2.fc42.x86_64
(gdb) disas /s $pc-10,+20
Dump of assembler code from 0x7fffc079eb4b to 0x7fffc079eb5f:
0x00007fffc079eb4b <_ZN9lcevc_dec7decoder4PoolINS0_7DecoderEEC2Em+43>: pop %rsp
0x00007fffc079eb4c <_ZN9lcevc_dec7decoder4PoolINS0_7DecoderEEC2Em+44>: and $0x18,%al
0x00007fffc079eb4e <_ZN9lcevc_dec7decoder4PoolINS0_7DecoderEEC2Em+46>: mov %rdi,%rbx
0x00007fffc079eb51 <_ZN9lcevc_dec7decoder4PoolINS0_7DecoderEEC2Em+49>: add $0x10,%rax
=> 0x00007fffc079eb55 <_ZN9lcevc_dec7decoder4PoolINS0_7DecoderEEC2Em+53>: vmovq %rax,%xmm0
0x00007fffc079eb5a <_ZN9lcevc_dec7decoder4PoolINS0_7DecoderEEC2Em+58>: vmovdqu %ymm0,(%rdi)
0x00007fffc079eb5e <_ZN9lcevc_dec7decoder4PoolINS0_7DecoderEEC2Em+62>: vpxor %xmm0,%xmm0,%xmm0
End of assembler dump.
(gdb)
Should this be also a bug as the other case with digikam?
Or is there any other thing that I’m missing?