[Digikam-devel] [Bug 204071] New: just started digikam and it crashed

thomas dendraya at gmx.net
Sun Aug 16 19:15:23 BST 2009


https://bugs.kde.org/show_bug.cgi?id=204071

           Summary: just started digikam and it crashed
           Product: digikam
           Version: unspecified
          Platform: Unlisted Binaries
        OS/Version: Linux
            Status: UNCONFIRMED
          Severity: crash
          Priority: NOR
         Component: general
        AssignedTo: digikam-devel at kde.org
        ReportedBy: dendraya at gmx.net


Application that crashed: digikam
Version of the application: 0.10.0
KDE Version: 4.3.00 (KDE 4.3.0)
Qt Version: 4.5.2
Operating System: Linux 2.6.28-14-generic i686
Distribution: Ubuntu 9.04

What I was doing when the application crashed:
well, i just started digikam and it crashed... didn't even see the splash
screen - the bug report comes straight away.

 -- Backtrace:
Application: digiKam (digikam), signal: Segmentation fault
[Current thread is 0 (LWP 10045)]

Thread 2 (Thread 0xb1e56b90 (LWP 10046)):
[KCrash Handler]
#6  0xb6e9d9c6 in Digikam::CollectionScanner::setSignalsEnabled (this=0x0,
on=true) at
/home/whatever/downloads/digikam-1.0.0-beta3/libs/database/collectionscanner.cpp:137
#7  0x0828e5fe in Digikam::ScanController::connectCollectionScanner
(this=0x8725130, scanner=0x0) at
/home/whatever/downloads/digikam-0.10.0/digikam/scancontroller.cpp:449
#8  0xb6f06e88 in Digikam::SchemaUpdater::update (this=0xb1e56254) at
/home/whatever/downloads/digikam-1.0.0-beta3/libs/database/schemaupdater.cpp:97
#9  0xb6eb8a6b in Digikam::DatabaseBackend::initSchema (this=0x872c100,
updater=0xb1e56254) at
/home/whatever/downloads/digikam-1.0.0-beta3/libs/database/databasebackend.cpp:72
#10 0xb6eb3f16 in Digikam::DatabaseAccess::checkReadyForUse
(observer=0x8725138) at
/home/whatever/downloads/digikam-1.0.0-beta3/libs/database/databaseaccess.cpp:246
#11 0x0828f1fe in Digikam::ScanController::run (this=0x8725130) at
/home/whatever/downloads/digikam-0.10.0/digikam/scancontroller.cpp:420
#12 0xb559f132 in QThreadPrivate::start (arg=0x8725130) at
thread/qthread_unix.cpp:188
#13 0xb52b54ff in start_thread () from /lib/tls/i686/cmov/libpthread.so.0
#14 0xb53ac49e in clone () from /lib/tls/i686/cmov/libc.so.6

Thread 1 (Thread 0xb365d700 (LWP 10045)):
#0  0xb7f34430 in __kernel_vsyscall ()
#1  0xb52b90e5 in pthread_cond_wait@@GLIBC_2.3.2 () from
/lib/tls/i686/cmov/libpthread.so.0
#2  0xb53bb2ed in pthread_cond_wait () from /lib/tls/i686/cmov/libc.so.6
#3  0xb55a0172 in QWaitCondition::wait (this=0x872dfc8, mutex=0x872dfb4,
time=4294967295) at thread/qwaitcondition_unix.cpp:87
#4  0xb559f2d3 in QThread::wait (this=0x8725130, time=4294967295) at
thread/qthread_unix.cpp:484
#5  0x0828efae in Digikam::ScanController::shutDown (this=0x8725130) at
/home/whatever/downloads/digikam-0.10.0/digikam/scancontroller.cpp:264
#6  0x08292701 in ~ScanController (this=0x8725130) at
/home/whatever/downloads/digikam-0.10.0/digikam/scancontroller.cpp:247
#7  0x082928aa in destroy () at
/home/whatever/downloads/digikam-0.10.0/digikam/scancontroller.cpp:188
#8  0xb52f6bb9 in exit () from /lib/tls/i686/cmov/libc.so.6
#9  0xb5bb813b in qt_xio_errhandler () at kernel/qapplication_x11.cpp:707
#10 0xb674cf7a in KApplication::xioErrhandler (this=0xbfe4fdf4, dpy=0x866e068)
at /build/buildd/kde4libs-4.3.0/kdeui/kernel/kapplication.cpp:408
#11 0xb674cfb6 in kde_xio_errhandler (dpy=0x866e068) at
/build/buildd/kde4libs-4.3.0/kdeui/kernel/kapplication.cpp:125
#12 0xb5143f22 in _XIOError () from /usr/lib/libX11.so.6
#13 0xb514b743 in ?? () from /usr/lib/libX11.so.6
#14 0xb514c0e5 in _XEventsQueued () from /usr/lib/libX11.so.6
#15 0xb51347af in XEventsQueued () from /usr/lib/libX11.so.6
#16 0xb5bf5c3d in x11EventSourceCheck (s=0x865a8a0) at
kernel/qguieventdispatcher_glib.cpp:87
#17 0xb3aee6f6 in g_main_context_check () from /usr/lib/libglib-2.0.so.0
#18 0xb3aeefdd in ?? () from /usr/lib/libglib-2.0.so.0
#19 0xb3aef268 in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0
#20 0xb56bf317 in QEventDispatcherGlib::processEvents (this=0x8632f58, flags={i
= -1075512536}) at kernel/qeventdispatcher_glib.cpp:329
#21 0xb5bf5a75 in QGuiEventDispatcherGlib::processEvents (this=0x8632f58,
flags={i = -1075512488}) at kernel/qguieventdispatcher_glib.cpp:202
#22 0xb56921fa in QEventLoop::processEvents (this=0x872cf28, flags={i =
-1075512424}) at kernel/qeventloop.cpp:149
#23 0xb5692642 in QEventLoop::exec (this=0x872cf28, flags={i = -1075512372}) at
kernel/qeventloop.cpp:201
#24 0x0828eef4 in Digikam::ScanController::databaseInitialization
(this=0x8725130) at
/home/whatever/downloads/digikam-0.10.0/digikam/scancontroller.cpp:308
#25 0x082187ac in Digikam::AlbumManager::setDatabase (this=0x874df08,
dbPath=@0xbfe4ff20, priority=false) at
/home/whatever/downloads/digikam-0.10.0/digikam/albummanager.cpp:506
#26 0x082b4c00 in main (argc=5, argv=0xbfe50054) at
/home/whatever/downloads/digikam-0.10.0/digikam/main.cpp:158

This bug may be a duplicate of or related to bug 203083

Reported using DrKonqi

-- 
Configure bugmail: https://bugs.kde.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.



More information about the Digikam-devel mailing list