Segmentation fault starting digiKam 5.5 and 5.6 appimage
Gilles Caulier
caulier.gilles at gmail.com
Mon Apr 17 09:02:28 BST 2017
The trace do not show any backtrace.
Run AppImage with "debug". This will use GDB. When it crash you have a
prompt to enter command with gdb. Enter 'bt' to get the backtrace in
digiKam source code. The AppImage has all debug symbols.
I want to know why the AppImage crash and not your system version. Probably
there is a difference at compilation time.
Gilles Caulier
2017-04-17 9:50 GMT+02:00 Anders Stedtlund <falolaf at gmail.com>:
> Attached debug output from run with digiKam 5.6.0 appimage. Same result
> when running 5.5.0 appimage.
>
> I have installed precompiled digiKam 5.5.0 from OBS which runs just fine.
>
> /Anders
>
>
> tis 11 apr. 2017 kl 06:53 skrev Gilles Caulier <caulier.gilles at gmail.com>:
>
>> run digiKam appimahe with "debug" argument. This will use GDB to get the
>> backtrace of crash.
>>
>> Gilles Caulier
>>
>> 2017-04-11 5:24 GMT+02:00 Anders Stedtlund <falolaf at gmail.com>:
>>
>> Hello,
>>
>> I get a segmentation fault when starting either digiKam 5.5 or 5.6
>> appimage:
>> [09:03]$ ./digikam-5.5.0-01-x86-64.appimage
>> -- digiKam AppImage Bundle
>> -- Use 'help' as CLI argument to know all available options
>> digikam.widgets: Breeze icons ressource file found
>> digikam.general: AlbumWatch use QFileSystemWatcher
>> digikam.general: Database Parameters:
>> Type: "QSQLITE"
>> DB Core Name: "/stedtlund/media/digiKam/digikam4.db"
>> DB Thumbs Name: "/stedtlund/media/digiKam/
>> thumbnails-digikam.db"
>> DB Face Name: "/stedtlund/media/digiKam/recognition.db"
>> Connect Options: ""
>> Host Name: ""
>> Host port: -1
>> Internal Server: false
>> Internal Server Path: ""
>> Internal Server Serv Cmd: ""
>> Internal Server Init Cmd: ""
>> Username: ""
>> Password: ""
>>
>> digikam.dbengine: Loading SQL code from config file
>> "/tmp/.mount_76NVZv/usr/share/digikam/database/dbconfig.xml"
>> digikam.dbengine: Checking XML version ID => expected: 3 found: 3
>> digikam.coredb: Core database: running schema update
>> digikam.coredb: Core database: have a structure version 8
>> digikam.coredb: Core database: makeUpdates 8 to 8
>> digikam.database: Creating new Location "/media/Andras bilder" uuid
>> "volumeid:?uuid=f7ef6339-6327-4405-8df3-58ce862b9eaf"
>> digikam.database: Creating new Location "/media/Fotosidan" uuid
>> "volumeid:?uuid=f7ef6339-6327-4405-8df3-58ce862b9eaf"
>> digikam.database: Creating new Location "/media/Skrivbordsbilder" uuid
>> "volumeid:?uuid=f7ef6339-6327-4405-8df3-58ce862b9eaf"
>> digikam.database: Creating new Location "/media/Våra filmer" uuid
>> "volumeid:?uuid=f7ef6339-6327-4405-8df3-58ce862b9eaf"
>> digikam.database: Creating new Location "/media/Våra bilder" uuid
>> "volumeid:?uuid=f7ef6339-6327-4405-8df3-58ce862b9eaf"
>> digikam.database: Creating new Location "/media/Almanackor" uuid
>> "volumeid:?uuid=f7ef6339-6327-4405-8df3-58ce862b9eaf"
>> digikam.database: Creating new Location "/media/Förstoringar" uuid
>> "volumeid:?uuid=f7ef6339-6327-4405-8df3-58ce862b9eaf"
>> digikam.database: Creating new Location "/media/Inskanningar" uuid
>> "volumeid:?uuid=f7ef6339-6327-4405-8df3-58ce862b9eaf"
>> digikam.database: Creating new Location "/media/Boende" uuid
>> "volumeid:?uuid=f7ef6339-6327-4405-8df3-58ce862b9eaf"
>> digikam.database: Creating new Location "/media/Annonser" uuid
>> "volumeid:?uuid=f7ef6339-6327-4405-8df3-58ce862b9eaf"
>> digikam.database: Creating new Location "/media/G+" uuid
>> "volumeid:?uuid=f7ef6339-6327-4405-8df3-58ce862b9eaf"
>> digikam.database: Creating new Location "/media/Diverse" uuid
>> "volumeid:?uuid=f7ef6339-6327-4405-8df3-58ce862b9eaf"
>> digikam.database: Creating new Location "/media/Edvins bilder" uuid
>> "volumeid:?uuid=f7ef6339-6327-4405-8df3-58ce862b9eaf"
>> digikam.database: location for "/stedtlund/media/Andras bilder" is
>> available true
>> digikam.database: location for "/stedtlund/media/Fotosidan" is
>> available true
>> digikam.database: location for "/stedtlund/media/Skrivbordsbilder" is
>> available true
>> digikam.database: location for "/stedtlund/media/Våra filmer" is
>> available true
>> digikam.database: location for "/stedtlund/media/Våra bilder" is
>> available true
>> digikam.database: location for "/stedtlund/media/Almanackor" is
>> available true
>> digikam.database: location for "/stedtlund/media/Förstoringar" is
>> available true
>> digikam.database: location for "/stedtlund/media/Inskanningar" is
>> available true
>> digikam.database: location for "/stedtlund/media/Boende" is available
>> true
>> digikam.database: location for "/stedtlund/media/Annonser" is
>> available true
>> digikam.database: location for "/stedtlund/media/G+" is available true
>> digikam.database: location for "/stedtlund/media/Diverse" is available
>> true
>> digikam.database: location for "/stedtlund/media/Edvins bilder" is
>> available true
>> KMemoryInfo: Platform identified : "LINUX"
>> KMemoryInfo: TotalRam: 8303431680
>> digikam.general: Allowing a cache size of 200 MB
>> digikam.thumbsdb: ThumbDB SelectThumbnailSetting val ret = 0
>> digikam.thumbsdb: ThumbDB SelectThumbnailSetting val ret = 0
>> digikam.thumbsdb: Thumbs database: have a structure version "3"
>> digikam.general: Thumbnails database ready for use
>> digikam.general: Switch to widget style: ""
>> /tmp/.mount_76NVZv/AppRun: rad 73: 6782 Segmenteringsfel
>> (minnesutskrift skapad) digikam.wrapper $@
>>
>> dmesg shows:
>> digikam[6704]: segfault at 6 ip 00007fada0797c04 sp 00007ffc3bd3d228
>> error 4 in libc-2.22.so[7fada071c000+19a000]
>>
>> digiKam 5.4 appimage still works as expected.
>>
>> I'm on openSUSE Leap42.2.
>>
>> Any suggestion would be most welcome.
>>
>> /Anders
>>
>>
>>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mail.kde.org/pipermail/digikam-users/attachments/20170417/778b6d21/attachment.html>
More information about the Digikam-users
mailing list