Bug 320953

Summary:	Crash on startup
Product:	[Applications] digikam	Reporter:	ducktayp
Component:	Database-Scan	Assignee:	Digikam Developers <digikam-bugs-null>
Status:	RESOLVED FIXED
Severity:	crash	CC:	caulier.gilles
Priority:	NOR
Version:	3.2.0
Target Milestone:	---
Platform:	Ubuntu
OS:	Linux
Latest Commit:		Version Fixed In:	5.0.0
Sentry Crash Report:

Description ducktayp 2013-06-09 11:46:56 UTC

Application: digikam (3.2.0)
KDE Platform Version: 4.10.4
Qt Version: 4.8.2
Operating System: Linux 3.2.0-45-generic x86_64
Distribution: Ubuntu 12.04.2 LTS

-- Information about the crash:
Started up the application. The splash screen comes up, gets to "Initializing Main View" and then consistently crashes.

Running kubuntu 12.04.2

The crash can be reproduced every time.

-- Backtrace:
Application: digiKam (digikam), signal: Segmentation fault
Using host libthread_db library "/lib/x86_64-linux-gnu/libthread_db.so.1".
[Current thread is 1 (Thread 0x7f3fb3378a00 (LWP 10413))]

Thread 5 (Thread 0x7f3f8e1ed700 (LWP 10414)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:162
#1  0x00007f3fadace5ab in wait (time=18446744073709551615, this=0x25d6380) at thread/qwaitcondition_unix.cpp:86
#2  QWaitCondition::wait (this=<optimized out>, mutex=0x25d6288, time=18446744073709551615) at thread/qwaitcondition_unix.cpp:158
#3  0x00000000005deb40 in Digikam::ScanController::run (this=0x252b270) at /build/buildd/digikam-3.2.0/core/digikam/database/scancontroller.cpp:713
#4  0x00007f3fadace09b in QThreadPrivate::start (arg=0x252b270) at thread/qthread_unix.cpp:307
#5  0x00007f3fa80c0e9a in start_thread (arg=0x7f3f8e1ed700) at pthread_create.c:308
#6  0x00007f3faccf7ccd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112
#7  0x0000000000000000 in ?? ()

Thread 4 (Thread 0x7f3f8d9ec700 (LWP 10415)):
#0  0x00007f3faccec313 in __GI___poll (fds=<optimized out>, nfds=<optimized out>, timeout=<optimized out>) at ../sysdeps/unix/sysv/linux/poll.c:87
#1  0x00007f3fa589e036 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x00007f3fa589e164 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x00007f3fadbfc926 in QEventDispatcherGlib::processEvents (this=0x7f3f800008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:426
#4  0x00007f3fadbcbe62 in QEventLoop::processEvents (this=<optimized out>, flags=...) at kernel/qeventloop.cpp:149
#5  0x00007f3fadbcc0b7 in QEventLoop::exec (this=0x7f3f8d9ebb50, flags=...) at kernel/qeventloop.cpp:204
#6  0x00007f3fadacb077 in QThread::exec (this=<optimized out>) at thread/qthread.cpp:501
#7  0x00007f3fadbabb6f in QInotifyFileSystemWatcherEngine::run (this=0x2578ee0) at io/qfilesystemwatcher_inotify.cpp:248
#8  0x00007f3fadace09b in QThreadPrivate::start (arg=0x2578ee0) at thread/qthread_unix.cpp:307
#9  0x00007f3fa80c0e9a in start_thread (arg=0x7f3f8d9ec700) at pthread_create.c:308
#10 0x00007f3faccf7ccd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112
#11 0x0000000000000000 in ?? ()

Thread 3 (Thread 0x7f3f8d1eb700 (LWP 10423)):
#0  pthread_cond_wait@@GLIBC_2.3.2 () at ../nptl/sysdeps/unix/sysv/linux/x86_64/pthread_cond_wait.S:162
#1  0x00007f3fadace5ab in wait (time=18446744073709551615, this=0x26d49d0) at thread/qwaitcondition_unix.cpp:86
#2  QWaitCondition::wait (this=<optimized out>, mutex=0x28e05b8, time=18446744073709551615) at thread/qwaitcondition_unix.cpp:158
#3  0x00007f3fb0bdc311 in Digikam::ParkingThread::run (this=0x28e05a0) at /build/buildd/digikam-3.2.0/core/libs/threads/threadmanager.cpp:119
#4  0x00007f3fadace09b in QThreadPrivate::start (arg=0x28e05a0) at thread/qthread_unix.cpp:307
#5  0x00007f3fa80c0e9a in start_thread (arg=0x7f3f8d1eb700) at pthread_create.c:308
#6  0x00007f3faccf7ccd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112
#7  0x0000000000000000 in ?? ()

Thread 2 (Thread 0x7f3f780a4700 (LWP 10424)):
#0  0x00007f3faccec313 in __GI___poll (fds=<optimized out>, nfds=<optimized out>, timeout=<optimized out>) at ../sysdeps/unix/sysv/linux/poll.c:87
#1  0x00007f3fa589e036 in ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#2  0x00007f3fa589e164 in g_main_context_iteration () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
#3  0x00007f3fadbfc926 in QEventDispatcherGlib::processEvents (this=0x7f3f700008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:426
#4  0x00007f3fadbcbe62 in QEventLoop::processEvents (this=<optimized out>, flags=...) at kernel/qeventloop.cpp:149
#5  0x00007f3fadbcc0b7 in QEventLoop::exec (this=0x7f3f780a3b50, flags=...) at kernel/qeventloop.cpp:204
#6  0x00007f3fadacb077 in QThread::exec (this=<optimized out>) at thread/qthread.cpp:501
#7  0x00007f3fadbabb6f in QInotifyFileSystemWatcherEngine::run (this=0x2ffccf0) at io/qfilesystemwatcher_inotify.cpp:248
#8  0x00007f3fadace09b in QThreadPrivate::start (arg=0x2ffccf0) at thread/qthread_unix.cpp:307
#9  0x00007f3fa80c0e9a in start_thread (arg=0x7f3f780a4700) at pthread_create.c:308
#10 0x00007f3faccf7ccd in clone () at ../sysdeps/unix/sysv/linux/x86_64/clone.S:112
#11 0x0000000000000000 in ?? ()

Thread 1 (Thread 0x7f3fb3378a00 (LWP 10413)):
[KCrash Handler]
#6  0x00007f3fb0c0ef9c in Digikam::ColorLabelSelector::slotColorLabelChanged (this=0x3963390, id=0) at /build/buildd/digikam-3.2.0/core/libs/widgets/common/colorlabelwidget.cpp:503
#7  0x00007f3fb0c101d7 in Digikam::ColorLabelSelector::ColorLabelSelector (this=0x3963390, parent=<optimized out>) at /build/buildd/digikam-3.2.0/core/libs/widgets/common/colorlabelwidget.cpp:468
#8  0x00000000004b57c1 in Digikam::ImageDescEditTab::ImageDescEditTab (this=0x38bd160, parent=<optimized out>) at /build/buildd/digikam-3.2.0/core/libs/imageproperties/imagedescedittab.cpp:221
#9  0x00000000004a4de1 in Digikam::ImagePropertiesSideBarDB::ImagePropertiesSideBarDB (this=0x3730f20, parent=0x2e205e0, splitter=<optimized out>, side=<optimized out>, mimimizedDefault=<optimized out>) at /build/buildd/digikam-3.2.0/core/libs/imageproperties/imagepropertiessidebardb.cpp:99
#10 0x000000000066cf65 in Digikam::DigikamView::DigikamView (this=0x2e205e0, parent=0x25bed80, modelCollection=0x2e163b0) at /build/buildd/digikam-3.2.0/core/digikam/views/digikamview.cpp:266
#11 0x0000000000587a2b in Digikam::DigikamApp::setupView (this=0x25bed80) at /build/buildd/digikam-3.2.0/core/digikam/main/digikamapp.cpp:528
#12 0x00000000005a1d20 in Digikam::DigikamApp::DigikamApp (this=0x25bed80, __in_chrg=<optimized out>, __vtt_parm=<optimized out>) at /build/buildd/digikam-3.2.0/core/digikam/main/digikamapp.cpp:262
#13 0x0000000000490c94 in main (argc=5, argv=<optimized out>) at /build/buildd/digikam-3.2.0/core/digikam/main/main.cpp:189

Reported using DrKonqi

Comment 1 ducktayp 2013-06-09 12:04:17 UTC

Removing the thumbnail database solved the problem.

Comment 2 ducktayp 2013-06-09 16:42:44 UTC

Why is this marked as resolved/invalid? The fact that there's an ugly workaround doesn't mean that it isn't a bug.  Even a completely borked database shouldn't cause the app to crash (especially when there's no indication about why it crashed).

Comment 3 caulier.gilles 2013-06-09 16:44:35 UTC

If you DB file is corrupted and if you delete it, how we can investiguate ?

Gilles Caulier

Comment 4 ducktayp 2013-06-09 16:52:40 UTC

I agree that it makes the bug hard to reproduce, but that's true of many bugs. 

There are the full stack traces, which could help a little. Leaving the bug open and seeing if other users encounter a similar problem could also help. 

Note that this problem was not caused by external corruption to the database, but by digikam itself (there were no disk errors). It could be that if digikam crashes for some other reason, it can leave the database in a bad state.



(In reply to comment #3)
> If you DB file is corrupted and if you delete it, how we can investiguate ?
> 
> Gilles Caulier

Comment 5 caulier.gilles 2013-10-31 07:52:19 UTC

digiKam 3.5.0 is out.

Can you give a fresh feedback about your report ? Crash still reproducible ?

Thanks in advance

Gilles Caulier

Comment 6 caulier.gilles 2014-05-16 07:28:59 UTC

digiKam 4.0.0 is out :

http://www.digikam.org/node/713

Please check if this entry still valid with this new version.

Thanks in advance

Gilles Caulier

Comment 7 caulier.gilles 2014-08-07 06:30:18 UTC

We need a fresh feedback using last digiKam 4.2.0

Gilles Caulier

Comment 8 caulier.gilles 2015-06-29 17:45:39 UTC

New digiKam 4.11.0 is available with official PKG installer for OSX.

https://www.digikam.org/node/740

Can you reproduce the problem with this release ?

Gilles Caulier

Comment 9 caulier.gilles 2015-08-20 06:51:43 UTC

digiKam 4.12.0 is out :

https://www.digikam.org/node/741

We need a fresh feedback using this release please...
Thanks in advance.

Gilles Caulier

Comment 10 caulier.gilles 2016-07-02 15:31:43 UTC

With 5.0.0, the crash is not reproducible anymore.

I close this file now. Don't hesitate to re-open if necessary.

Gilles Caulier