Bug 202956 - Crashing on start up
Summary: Crashing on start up
Status: RESOLVED FIXED
Alias: None
Product: digikam
Classification: Applications
Component: Database-Scan (show other bugs)
Version: 0.10.0
Platform: openSUSE Linux
: NOR crash
Target Milestone: ---
Assignee: Digikam Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-08-07 15:02 UTC by sarge
Modified: 2019-12-25 15:53 UTC (History)
2 users (show)

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


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description sarge 2009-08-07 15:02:14 UTC
Version:           0.10.0 (using KDE 4.3.0)
OS:                Linux
Installed from:    SuSE RPMs

When trying to start Digikam I get the bouncing icon and then the KDE crash handler.  If I move my photos to another folder and try starting it again I get the first run wizard.  Just after it creates the new folder it will crash again.
I have tried deleting the digikam4.db file.. no change.
This is the crash handler says...

Executable: digikam PID: 6995 Signal: 6 (Aborted)

Application: digiKam (digikam), signal: Aborted
[Current thread is 1 (Thread 0x7fcc2004b750 (LWP 6995))]

Thread 2 (Thread 0x7fcc0dcd9950 (LWP 6996)):
[KCrash Handler]
#5  0x00007fcc18dc5645 in raise () from /lib64/libc.so.6
#6  0x00007fcc18dc6c33 in abort () from /lib64/libc.so.6
#7  0x00007fcc19ad8f15 in qt_message_output(QtMsgType, char const*) () from /usr/lib64/libQtCore.so.4
#8  0x00007fcc19ad905b in qFatal(char const*, ...) () from /usr/lib64/libQtCore.so.4
#9  0x00007fcc19bde24d in QObjectPrivate::QObjectPrivate(int) () from /usr/lib64/libQtCore.so.4
#10 0x00007fcc1e2f9bad in QSqlDriver::QSqlDriver(QObject*) () from /usr/lib64/libQtSql.so.4
#11 0x00007fcc1e2f28c2 in ?? () from /usr/lib64/libQtSql.so.4
#12 0x00007fcc1e2f2c29 in QSqlDatabase::QSqlDatabase() () from /usr/lib64/libQtSql.so.4
#13 0x00007fcc1cf8aea6 in Digikam::DatabaseBackendPriv::databaseForThread() () from /usr/lib64/libdigikamdatabase.so.1
#14 0x00007fcc1cf8633d in Digikam::DatabaseBackend::open (this=0xafaac0, parameters=<value optimized out>) at /usr/src/debug/digikam-0.10.0/libs/database/databasebackend.cpp:293
#15 0x00007fcc1cf81920 in Digikam::DatabaseAccess::checkReadyForUse (observer=0xafaea0) at /usr/src/debug/digikam-0.10.0/libs/database/databaseaccess.cpp:231
#16 0x000000000064ba5d in Digikam::ScanController::run (this=0xafae90) at /usr/src/debug/digikam-0.10.0/digikam/scancontroller.cpp:420
#17 0x00007fcc19ae0e65 in ?? () from /usr/lib64/libQtCore.so.4
#18 0x00007fcc1986d070 in start_thread () from /lib64/libpthread.so.0
#19 0x00007fcc18e6610d in clone () from /lib64/libc.so.6
#20 0x0000000000000000 in ?? ()

Thread 1 (Thread 0x7fcc2004b750 (LWP 6995)):
#0  0x00007fcc19870d59 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0
#1  0x00007fcc19ae1e19 in QWaitCondition::wait(QMutex*, unsigned long) () from /usr/lib64/libQtCore.so.4
#2  0x00007fcc19ae100c in QThread::wait(unsigned long) () from /usr/lib64/libQtCore.so.4
#3  0x000000000064b8dc in Digikam::ScanController::shutDown (this=0xafae90) at /usr/src/debug/digikam-0.10.0/digikam/scancontroller.cpp:264
#4  0x000000000064f37b in ~ScanController (this=0xafb12c) at /usr/src/debug/digikam-0.10.0/digikam/scancontroller.cpp:247
#5  0x000000000064f517 in destroy () at /usr/src/debug/digikam-0.10.0/digikam/scancontroller.cpp:188
#6  0x00007fcc18dc82ed in exit () from /lib64/libc.so.6
#7  0x00007fcc1a7a2098 in ?? () from /usr/lib64/libQtGui.so.4
#8  0x00007fcc1bb24138 in KApplication::xioErrhandler(_XDisplay*) () from /usr/lib64/libkdeui.so.5
#9  0x00007fcc17bd1e54 in _XIOError () from /usr/lib64/libX11.so.6
#10 0x00007fcc17bd9f48 in _XSend () from /usr/lib64/libX11.so.6
#11 0x00007fcc17bda014 in _XEventsQueued () from /usr/lib64/libX11.so.6
#12 0x00007fcc17bc2593 in XEventsQueued () from /usr/lib64/libX11.so.6
#13 0x00007fcc1a7dc79b in ?? () from /usr/lib64/libQtGui.so.4
#14 0x00007fcc164570fb in g_main_context_dispatch () from /usr/lib64/libglib-2.0.so.0
#15 0x00007fcc1645a8cd in ?? () from /usr/lib64/libglib-2.0.so.0
#16 0x00007fcc1645aa8b in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0
#17 0x00007fcc19bf3d3f in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/libQtCore.so.4
#18 0x00007fcc1a7dbfff in ?? () from /usr/lib64/libQtGui.so.4
#19 0x00007fcc19bc91d2 in QEventLoop::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/libQtCore.so.4
#20 0x00007fcc19bc95a4 in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/libQtCore.so.4
#21 0x000000000064b606 in Digikam::ScanController::databaseInitialization (this=0xafae90) at /usr/src/debug/digikam-0.10.0/digikam/scancontroller.cpp:308
#22 0x00000000005d80e2 in Digikam::AlbumManager::setDatabase (this=0xab3ff0, dbPath=<value optimized out>, priority=<value optimized out>)
    at /usr/src/debug/digikam-0.10.0/digikam/albummanager.cpp:506
#23 0x00000000006717f9 in main (argc=5, argv=0x7fff2809ff38) at /usr/src/debug/digikam-0.10.0/digikam/main.cpp:158
Comment 1 Marcel Wiesweg 2009-08-07 17:42:00 UTC
Your Qt Sql library (/usr/lib64/libQtSql.so.4) is somehow binary incompatible to your main Qt version. You will get an error message on the console when Qt detects a problem and aborts.
Comment 2 Dario Andres 2009-08-07 19:02:20 UTC
Same backtrace as bug 194630. Merging. Thanks

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