Bug 272529 - digikam crashing on load
Summary: digikam crashing on load
Status: RESOLVED WORKSFORME
Alias: None
Product: digikam
Classification: Applications
Component: Plugin-DImg-RAW (show other bugs)
Version: 2.0.0
Platform: Ubuntu Linux
: NOR crash
Target Milestone: ---
Assignee: Digikam Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-05-05 13:43 UTC by 20120808_bugs.kde.org
Modified: 2012-06-27 10:27 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In: 2.0.0
Sentry Crash Report:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description 20120808_bugs.kde.org 2011-05-05 13:43:45 UTC
Application: digikam (2.0.0-beta4)
KDE Platform Version: 4.6.2 (4.6.2)
Qt Version: 4.7.2
Operating System: Linux 2.6.38-8-generic-tuxonice x86_64
Distribution: Ubuntu 11.04

-- Information about the crash:
- What I was doing when the application crashed:

just had finished downloading pictures from the camera. there was a problem with the filesystem on the sd card: some of the images were corrupt.

could very well be that some of the images are corrupt.


digikam 2.0 beta4, ppa from philip5 (kubuntu backports and extra)
kubuntu 10.04 natty
amd64


launching in konsole shows:
(digikam:2963): GStreamer-CRITICAL **: gst_debug_add_log_function: assertion `func != NULL' failed
KCrash: Application 'digikam' crashing...
KCrash: Attempting to start /usr/lib/kde4/libexec/drkonqi from kdeinit

The crash can be reproduced every time.

-- Backtrace:
Application: digiKam (digikam), signal: Segmentation fault
[Current thread is 1 (Thread 0x7f552a1eda20 (LWP 433))]

Thread 5 (Thread 0x7f550622e700 (LWP 512)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:162
#1  0x00007f55223ec82b in wait (this=<value optimized out>, mutex=0x2003518, time=18446744073709551615) at thread/qwaitcondition_unix.cpp:88
#2  QWaitCondition::wait (this=<value optimized out>, mutex=0x2003518, time=18446744073709551615) at thread/qwaitcondition_unix.cpp:160
#3  0x00000000005c34c8 in Digikam::ScanController::run (this=0x2001a80) at /build/buildd/digikam2-2.0.0~beta4/digikam/database/scancontroller.cpp:602
#4  0x00007f55223ec175 in QThreadPrivate::start (arg=0x2001a80) at thread/qthread_unix.cpp:320
#5  0x00007f551e031d8c in start_thread (arg=0x7f550622e700) at pthread_create.c:304
#6  0x00007f55213c104d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112
#7  0x0000000000000000 in ?? ()

Thread 4 (Thread 0x7f5505a2d700 (LWP 514)):
#0  0x00007f551e035d9d in __pthread_mutex_unlock_usercnt (mutex=0x7f55000009a8) at pthread_mutex_unlock.c:52
#1  __pthread_mutex_unlock (mutex=0x7f55000009a8) at pthread_mutex_unlock.c:290
#2  0x00007f551c9c984e in g_main_context_check () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x00007f551c9ca122 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#4  0x00007f551c9ca639 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#5  0x00007f55224fe446 in QEventDispatcherGlib::processEvents (this=0x7f55000008b0, flags=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:424
#6  0x00007f55224d2882 in QEventLoop::processEvents (this=<value optimized out>, flags=...) at kernel/qeventloop.cpp:149
#7  0x00007f55224d2abc in QEventLoop::exec (this=0x7f5505a2cb30, flags=...) at kernel/qeventloop.cpp:201
#8  0x00007f55223e9924 in QThread::exec (this=<value optimized out>) at thread/qthread.cpp:492
#9  0x00007f55224b4c2f in QInotifyFileSystemWatcherEngine::run (this=0x2013e60) at io/qfilesystemwatcher_inotify.cpp:248
#10 0x00007f55223ec175 in QThreadPrivate::start (arg=0x2013e60) at thread/qthread_unix.cpp:320
#11 0x00007f551e031d8c in start_thread (arg=0x7f5505a2d700) at pthread_create.c:304
#12 0x00007f55213c104d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112
#13 0x0000000000000000 in ?? ()

Thread 3 (Thread 0x7f550522c700 (LWP 618)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:162
#1  0x00007f55223ec82b in wait (this=<value optimized out>, mutex=0x24f9908, time=18446744073709551615) at thread/qwaitcondition_unix.cpp:88
#2  QWaitCondition::wait (this=<value optimized out>, mutex=0x24f9908, time=18446744073709551615) at thread/qwaitcondition_unix.cpp:160
#3  0x00007f5526cdbfe7 in Digikam::ParkingThread::run (this=0x24f98f0) at /build/buildd/digikam2-2.0.0~beta4/libs/threads/threadmanager.cpp:119
#4  0x00007f55223ec175 in QThreadPrivate::start (arg=0x24f98f0) at thread/qthread_unix.cpp:320
#5  0x00007f551e031d8c in start_thread (arg=0x7f550522c700) at pthread_create.c:304
#6  0x00007f55213c104d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112
#7  0x0000000000000000 in ?? ()

Thread 2 (Thread 0x7f54fd9e1700 (LWP 628)):
#0  0x00007f551c9ca0ac in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#1  0x00007f551c9ca639 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x00007f55224fe446 in QEventDispatcherGlib::processEvents (this=0x264d3b0, flags=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:424
#3  0x00007f55224d2882 in QEventLoop::processEvents (this=<value optimized out>, flags=...) at kernel/qeventloop.cpp:149
#4  0x00007f55224d2abc in QEventLoop::exec (this=0x7f54fd9e0b30, flags=...) at kernel/qeventloop.cpp:201
#5  0x00007f55223e9924 in QThread::exec (this=<value optimized out>) at thread/qthread.cpp:492
#6  0x00007f55224b4c2f in QInotifyFileSystemWatcherEngine::run (this=0x264c940) at io/qfilesystemwatcher_inotify.cpp:248
#7  0x00007f55223ec175 in QThreadPrivate::start (arg=0x264c940) at thread/qthread_unix.cpp:320
#8  0x00007f551e031d8c in start_thread (arg=0x7f54fd9e1700) at pthread_create.c:304
#9  0x00007f55213c104d in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112
#10 0x0000000000000000 in ?? ()

Thread 1 (Thread 0x7f552a1eda20 (LWP 433)):
[KCrash Handler]
#6  0xfffffffffffffff0 in ?? ()
#7  0x00007f5527f25769 in KDcrawIface::RExpanderBox::readSettings() () from /usr/lib/libkdcraw.so.20
#8  0x00000000004a7f68 in Digikam::ImageDescEditTab::ImageDescEditTab (this=0x2f61250, parent=<value optimized out>) at /build/buildd/digikam2-2.0.0~beta4/libs/imageproperties/imagedescedittab.cpp:394
#9  0x000000000049878b in Digikam::ImagePropertiesSideBarDB::ImagePropertiesSideBarDB (this=0x266d380, parent=0x24f23f0, splitter=<value optimized out>, side=<value optimized out>, mimimizedDefault=<value optimized out>) at /build/buildd/digikam2-2.0.0~beta4/libs/imageproperties/imagepropertiessidebardb.cpp:99
#10 0x000000000064313b in Digikam::DigikamView::DigikamView (this=0x24f23f0, parent=0x21f3660, modelCollection=0x2074990) at /build/buildd/digikam2-2.0.0~beta4/digikam/views/digikamview.cpp:198
#11 0x0000000000567baa in Digikam::DigikamApp::setupView (this=0x21f3660) at /build/buildd/digikam2-2.0.0~beta4/digikam/main/digikamapp.cpp:518
#12 0x0000000000585893 in Digikam::DigikamApp::DigikamApp (this=0x21f3660, __in_chrg=<value optimized out>, __vtt_parm=<value optimized out>) at /build/buildd/digikam2-2.0.0~beta4/digikam/main/digikamapp.cpp:243
#13 0x0000000000697b58 in main (argc=5, argv=0x7fffe58baee8) at /build/buildd/digikam2-2.0.0~beta4/digikam/main/main.cpp:188

Reported using DrKonqi
Comment 1 caulier.gilles 2011-05-05 13:50:19 UTC
Crash appears in libkdcraw. Sound like a binary compatibility issue. Check this lib on your system

Gilles Caulier
Comment 2 20120808_bugs.kde.org 2011-05-06 00:01:39 UTC
noticed available packages for the 2beta5, installed that. in doing so, noticed 

<i>
The following NEW packages will be installed:
  libcv2.2{a} libcvaux2.2{a} libcvaux2.2-data{a} libhighgui2.2{a} libtbb2{a} libunicap2{a} 
The following packages will be upgraded:
  digikam2 digikam2-data digikam2-dbg kipi-plugins2 kipi-plugins2-common libkface-1 showfoto2
</i>

libcv needed to be installed. 


with 2beta5, digikam works again
Comment 3 caulier.gilles 2011-05-06 06:57:53 UTC
So, it's fixed now ?

Gilles Caulier
Comment 4 20120808_bugs.kde.org 2011-05-07 23:57:08 UTC
Hello. 2beta5 is not crashing on load for me like 2beta4 was when I reported the issue. 

My guess is, as you pointed out, an incompatibility at the ABI level was the cause.