[digiKam-users] Seg Fault

[Jim Dory]

Hello Gilles,

Apologies for replies off-list.. forgot to check on my To: field when replying.

I couldn't get things to work.. even the latest 7.10 appimage did the same fault.

So I went ahead and compiled digikam with its dependencies (qtwebengine, node.js, etc) and that works fine. What would 
have been about a day compile on my old computer ended up being about 2 hours.

thanks, Jim

On 1/27/23 23:26, Gilles Caulier wrote:
> Hi,
>
> 1/ Get the digiKamAppImage with "debug" symbols (the huge file to download).
> 2/ run the appimage from the command line with the "debug" argument.
> When it crashes, enter "bt" in gdb to get a backtrace.
> 3/ Post the backtrace here for investigation.
> 4/ Another simple test is to create a fresh account and start digiKam
> from scratch to see if crash is reproducible. If not, it can be a
> problem with your configuration files.
>
> Best
>
> Gilles Caulier
>
> Le sam. 28 janv. 2023 à 06:36, Jim Dory <james at dorydesign.com> a écrit :
>> So I just built a new computer linux and am getting this:
>>
>>
>> ./digiKam-7.9.0-x86-64.appimage
>> -- 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 gentoo-64-
>> -- AppImage mounted directory: /tmp/.mount_digiKav6Nqtc
>> 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_digiKav6Nqtc/usr/lib/libavif.so.13:/usr/lib64/libxcb-dri3.so.0:/usr/
>> lib64/libcrypto.so.1.1:/usr/lib64/libssl.so.1.1:/usr/lib64/libnss3.so:/usr/lib64/libnssutil3.so:/usr/lib64/l
>> ibsmime3.so:/usr/lib64/libgmodule-2.0.so.0
>> /tmp/.mount_digiKav6Nqtc/AppRun: line 204:  3209 Segmentation fault      digikam $@
>>
>>
>> and in the /var/log/messages:
>>
>>
>> Jan 28 04:23:56 Asus_tux kernel: digikam[3209]: segfault at fffffffffffffd68 ip 00007f6254984799 sp 00007fff
>> 096ae018 error 5 in libc.so.6[7f6254859000+151000]
>> Jan 28 04:23:56 Asus_tux kernel: Code: fe 7f 5c 17 e1 c5 f8 77 c3 0f 1f 84 00 00 00 00 00 89 f8 48 89 fa c5
>> f9 ef c0 25 ff 0f 00 00 3d e0 0f 00 00 0f 87 37 01 00 00 <c5> fd 74 0f c5 fd d7 c1 85 c0 74 5b f3 0f bc c0 c
>> 5 f8 77 c3 0f 1f
>>
>> I migrated my /home from the old gentoo linux computer to this new one. My database is on the local disk but collection
>> on a Network Attached Storage (NAS). The old computer was working fine. I rsync'd the files over preserving permissions
>> and stuff.
>>
>> The old computer also now is segmentation faulting. Baffles my mind why that is the case. Thought maybe it had to do
>> something with both machines mounted on the photo share, but turned it off and still getting the faults.
>>
>> Ideas?  thanks, Jim
>>