Segmentation fault starting digiKam 5.5 and 5.6 appimage
Anders Stedtlund
falolaf at gmail.com
Mon Apr 17 09:40:43 BST 2017
I run X11, as far as I know...
Den mån 17 apr. 2017 10:36Gilles Caulier <caulier.gilles at gmail.com> skrev:
> It crash in XCB X11 module, called by Qt5::QWidget. It's an internal error.
>
> Do you run X11 or Wayland ? If it the last one, you must install the X11
> backend for Wayland. The AppImage is only compiled for pure X11. This is
> why the system based version do not crash,... certainly...
>
> Gilles Caulier
>
> 2017-04-17 10:17 GMT+02:00 Anders Stedtlund <falolaf at gmail.com>:
>
>> It was the output from when running appimage with debug. Didn't know that
>> I had to do bt though...
>>
>> Here it is:
>> (gdb) bt
>> #0 __GI___libc_free (mem=0xe) at malloc.c:2952
>> #1 0x00000033a90047f9 in udev_device_unref () from
>> /tmp/.mount_rlwkrf/usr/lib/libudev.so.0
>> #2 0x00000033a90047de in udev_device_unref () from
>> /tmp/.mount_rlwkrf/usr/lib/libudev.so.0
>> #3 0x00007fffe9832721 in udev_device_unref (udev_device=0x8815b0) at
>> src/libudev/libudev-device.c:553
>> #4 0x00007fffeed63f69 in libudev_get_pci_id_for_fd
>> (chip_id=0x7fffffffc7dc, vendor_id=<optimized out>, fd=<optimized out>) at
>> loader.c:248
>> #5 loader_get_pci_id_for_fd (fd=fd at entry=20, vendor_id=vendor_id at entry=0x7fffffffc7d8,
>> chip_id=chip_id at entry=0x7fffffffc7dc) at loader.c:584
>> #6 0x00007fffeed643aa in loader_get_driver_for_fd (fd=20,
>> driver_types=3, driver_types at entry=0) at loader.c:700
>> #7 0x00007fffeed5f0f4 in dri2CreateScreen (screen=0, priv=0x844db0) at
>> dri2_glx.c:1210
>> #8 0x00007fffeed3eb9c in AllocAndFetchScreenConfigs (priv=0x844db0,
>> dpy=0x68f490) at glxext.c:799
>> #9 __glXInitialize (dpy=dpy at entry=0x68f490) at glxext.c:910
>> #10 0x00007fffeed3a9f7 in glXGetFBConfigs (dpy=0x68f490, screen=0,
>> nelements=nelements at entry=0x7fffffffc91c) at glxcmds.c:1651
>> #11 0x00007fffeed3b703 in glXChooseFBConfig (dpy=<optimized out>,
>> screen=<optimized out>, attribList=0x7da0b8, nitems=0x7fffffffca9c) at
>> glxcmds.c:1611
>> #12 0x00007ffff7fdd3f7 in ?? () from
>> /tmp/.mount_rlwkrf/usr/plugins/xcbglintegrations/libqxcb-glx-integration.so
>> #13 0x00007ffff7fdd71d in ?? () from
>> /tmp/.mount_rlwkrf/usr/plugins/xcbglintegrations/libqxcb-glx-integration.so
>> #14 0x00007ffff7fda029 in ?? () from
>> /tmp/.mount_rlwkrf/usr/plugins/xcbglintegrations/libqxcb-glx-integration.so
>> #15 0x00007fffe8f8fe71 in QXcbWindow::create() () from
>> /tmp/.mount_rlwkrf/usr/lib/libQt5XcbQpa.so.5
>> #16 0x00007fffe8f7b130 in QXcbIntegration::createPlatformWindow(QWindow*)
>> const () from /tmp/.mount_rlwkrf/usr/lib/libQt5XcbQpa.so.5
>> #17 0x00007fffef3049db in QWindowPrivate::create(bool) () from
>> /tmp/.mount_rlwkrf/usr/lib/libQt5Gui.so.5
>> #18 0x00007fffef90a3cd in QWidgetPrivate::create_sys(unsigned long long,
>> bool, bool) () from /tmp/.mount_rlwkrf/usr/lib/libQt5Widgets.so.5
>> #19 0x00007fffef909b99 in QWidget::create(unsigned long long, bool, bool)
>> () from /tmp/.mount_rlwkrf/usr/lib/libQt5Widgets.so.5
>> #20 0x00007fffef9163c2 in QWidget::setVisible(bool) () from
>> /tmp/.mount_rlwkrf/usr/lib/libQt5Widgets.so.5
>> ---Type <return> to continue, or q <return> to quit---
>> #21 0x00007ffff754f8d7 in Digikam::DigikamApp::DigikamApp (this=0x8e1c00,
>> __in_chrg=<optimized out>, __vtt_parm=<optimized out>)
>> at /b/dktemp/digikam-master/core/app/main/digikamapp.cpp:181
>> #22 0x0000000000405888 in main (argc=1, argv=<optimized out>) at
>> /b/dktemp/digikam-master/core/app/main/main.cpp:236
>>
>>
>> /Anders
>>
>>
>> mån 17 apr. 2017 kl 10:03 skrev Gilles Caulier <caulier.gilles at gmail.com
>> >:
>>
>>> 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/c5020a69/attachment.html>
More information about the Digikam-users
mailing list