Bug 194630

Summary: digiKam fails to start ? after Plasma update
Product: [Applications] digikam Reporter: Philip Timms <philip.timms>
Component: Database-ScanAssignee: Digikam Developers <digikam-bugs-null>
Status: RESOLVED FIXED    
Severity: crash CC: caulier.gilles, sarge
Priority: NOR    
Version: 0.10.0   
Target Milestone: ---   
Platform: Unlisted Binaries   
OS: Linux   
Latest Commit: Version Fixed In: 7.0.0
Sentry Crash Report:

Description Philip Timms 2009-05-30 09:30:31 UTC
Application that crashed: digikam
Version of the application: 0.10.0
KDE Version: 4.2.88 (KDE 4.2.88 (KDE 4.3 >= 20090527)) "release 1"
Qt Version: 4.5.1
Operating System: Linux 2.6.27.21-0.1-pae i686
Distribution: "openSUSE 11.1 (i586)"

What I was doing when the application crashed:
I'm using Digikam on KDE 4.28 on Opensuse 11.1.(not the KDE4 version - I did try to install that but was concerned about the number of dependencies that apparently needed to be downgraded).

When I try to open Digikam, I just get th error message that digikam "closed unexpectedly" - that's all.

Previously it has worked very well

 -- Backtrace:
Application: digiKam (digikam), signal: Aborted
[Current thread is 1 (Thread 0xb47a8700 (LWP 8407))]

Thread 2 (Thread 0xb2f99b90 (LWP 8408)):
[KCrash Handler]
#6  0xffffe430 in __kernel_vsyscall ()
#7  0xb5577990 in raise () from /lib/libc.so.6
#8  0xb55792c8 in abort () from /lib/libc.so.6
#9  0xb5836345 in qt_message_output(QtMsgType, char const*) () from /usr/lib/libQtCore.so.4
#10 0xb5836431 in qFatal(char const*, ...) () from /usr/lib/libQtCore.so.4
#11 0xb5946f34 in QObjectPrivate::QObjectPrivate(int) () from /usr/lib/libQtCore.so.4
#12 0xb77f6cb2 in QSqlDriver::QSqlDriver(QObject*) () from /usr/lib/libQtSql.so.4
#13 0xb77ef52a in ?? () from /usr/lib/libQtSql.so.4
#14 0xb77ef8cb in QSqlDatabase::QSqlDatabase() () from /usr/lib/libQtSql.so.4
#15 0xb70b0bf2 in Digikam::DatabaseBackendPriv::databaseForThread() () from /usr/lib/libdigikamdatabase.so.1
#16 0xb70abab1 in Digikam::DatabaseBackend::open (this=0x84d48c0, parameters=@0x84abf40) at /usr/src/debug/digikam-0.10.0/libs/database/databasebackend.cpp:293
#17 0xb70a6053 in Digikam::DatabaseAccess::checkReadyForUse (observer=0x84d4c40) at /usr/src/debug/digikam-0.10.0/libs/database/databaseaccess.cpp:231
#18 0x0828d82e in Digikam::ScanController::run (this=0x84d4c38) at /usr/src/debug/digikam-0.10.0/digikam/scancontroller.cpp:420
#19 0xb583e70e in ?? () from /usr/lib/libQtCore.so.4
#20 0xb57db1b5 in start_thread () from /lib/libpthread.so.0
#21 0xb561e3be in clone () from /lib/libc.so.6

Thread 1 (Thread 0xb47a8700 (LWP 8407)):
#0  0xffffe430 in __kernel_vsyscall ()
#1  0xb57dec35 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib/libpthread.so.0
#2  0xb583f722 in QWaitCondition::wait(QMutex*, unsigned long) () from /usr/lib/libQtCore.so.4
#3  0xb583e8b3 in QThread::wait(unsigned long) () from /usr/lib/libQtCore.so.4
#4  0x0828d5de in Digikam::ScanController::shutDown (this=0x84d4c38) at /usr/src/debug/digikam-0.10.0/digikam/scancontroller.cpp:264
#5  0x08290d11 in ~ScanController (this=0x84d4c38) at /usr/src/debug/digikam-0.10.0/digikam/scancontroller.cpp:247
#6  0x08290eba in destroy () at /usr/src/debug/digikam-0.10.0/digikam/scancontroller.cpp:188
#7  0xb557a9b1 in exit () from /lib/libc.so.6
#8  0xb5e8595b in ?? () from /usr/lib/libQtGui.so.4
#9  0xb6a3054a in KApplication::xioErrhandler(_XDisplay*) () from /usr/lib/libkdeui.so.5
#10 0xb6a30586 in ?? () from /usr/lib/libkdeui.so.5
#11 0xb53903c2 in _XIOError () from /usr/lib/libX11.so.6
#12 0xb5398ab0 in _XSend () from /usr/lib/libX11.so.6
#13 0xb5398c00 in _XEventsQueued () from /usr/lib/libX11.so.6
#14 0xb5380b3f in XEventsQueued () from /usr/lib/libX11.so.6
#15 0xb5ec219a in ?? () from /usr/lib/libQtGui.so.4
#16 0xb503c9c8 in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0
#17 0xb5040083 in ?? () from /usr/lib/libglib-2.0.so.0
#18 0xb5040241 in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0
#19 0xb595e558 in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQtCore.so.4
#20 0xb5ec1975 in ?? () from /usr/lib/libQtGui.so.4
#21 0xb59310fa in QEventLoop::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQtCore.so.4
#22 0xb593153a in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQtCore.so.4
#23 0x0828d524 in Digikam::ScanController::databaseInitialization (this=0x84d4c38) at /usr/src/debug/digikam-0.10.0/digikam/scancontroller.cpp:308
#24 0x08216ddc in Digikam::AlbumManager::setDatabase (this=0x8490778, dbPath=@0xbfbb93d0, priority=false) at /usr/src/debug/digikam-0.10.0/digikam/albummanager.cpp:506
#25 0x082b3240 in main (argc=5, argv=0xbfbb9504) at /usr/src/debug/digikam-0.10.0/digikam/main.cpp:158

Reported using DrKonqi
Comment 1 caulier.gilles 2009-05-30 09:42:30 UTC
Sound like a package problem with binary compatibility not respected...

Please report to Suse team...

Gilles Caulier
Comment 2 caulier.gilles 2009-06-03 16:00:50 UTC
Philip,

What's news here ? It still reproducible ? Give us a fresh feedback...

Thanks in advance 

Gilles Caulier
Comment 3 Dario Andres 2009-08-07 19:02:20 UTC
*** Bug 202956 has been marked as a duplicate of this bug. ***
Comment 4 caulier.gilles 2009-11-11 19:29:17 UTC

*** This bug has been marked as a duplicate of bug 213758 ***
Comment 5 caulier.gilles 2019-12-25 15:53:07 UTC
Not reproducible using digiKam 7.0.0 beta1.