| Summary: | digiKam crash when browsing albums (qt-sqlite plugin broken due to BC issue with libsqlite) | ||
|---|---|---|---|
| Product: | [Applications] digikam | Reporter: | André Hübert Johansen <andrejoh> |
| Component: | Database-Sqlite | Assignee: | Digikam Developers <digikam-bugs-null> |
| Status: | RESOLVED UPSTREAM | ||
| Severity: | crash | CC: | adam, ahepas1999, aj.kaja, alexander.budde, amair.sob, amasadero597, atholm, axel.krebs, benedict.breuer, bnbphotofr, Bruce.Skinner, bugs, caulier.gilles, cdubet, cfeck, cogefip, daristia, drdrnewman, dreibh, erd_a, erwin.segerer, fam.neumueller, fishbay, giggi1999, hans-ph, hans.kristian.moen, Heiner.Feilke, hirengandhi0317, itbastian, j.dessecker, j.e.wagner, jabog6, jens-bugs.kde.org, jetrull, JimShip, jmi.eck, johannes.schwall, jon33040, jpnutty1, jwekell, kdebug, kenjarvis2, kubunta, linux.tmc, linuxman, lise.jungebloedt, lj_wilson, luc, lukas.kripner, mac, mailing, manolis.tzivakis, mark, matthias10218, mauromagnani80, meckis1st, mgpoolman, mihaela.jurkovic, mitchellogical, mitscha, mi_ch, mkkomarek, mkpaaa, mmrakk, msylwester, otto.daemon, paalok, paulo, philippe.quaglia, pierre.monlong, ponchorat1968, ppedrok, rbk1rbk, rcash65, rjvbertin, roger.foss, rosswalsh31, schroemmel, sellesf, shadow77tr, sronayette, stefan.grosse, stupor_scurvy343, theonlyjeffjordan, tpr, ttgraser, ulimoebius, umvmac, vit.baran, vpc.jort, vredny, wolfgang.walkowiak, wwdiver, wwoodhull, yourenigmaster, yuri |
| Priority: | NOR | Keywords: | drkonqi |
| Version: | 3.5.0 | ||
| Target Milestone: | --- | ||
| Platform: | Fedora RPMs | ||
| OS: | Linux | ||
| Latest Commit: | Version Fixed In: | 7.5.0 | |
| Sentry Crash Report: | |||
| Attachments: |
New crash information added by DrKonqi
New crash information added by DrKonqi New crash information added by DrKonqi New crash information added by DrKonqi New crash information added by DrKonqi |
||
|
Description
André Hübert Johansen
2014-01-07 21:07:28 UTC
It crash in Qt SQlite plugin. There is no reason for that typically... Gilles Caulier *** Bug 330104 has been marked as a duplicate of this bug. *** *** Bug 330155 has been marked as a duplicate of this bug. *** sorry I'm a new entry for bugtracking system, I would only help tio improve digikam i use dk with two distro mint16kde and fedora 20 kde, with only one database localized in a separated formatting disk I use sqlite not mysql on mint digikam 3.4 go correctly (its seem) but in fedora with the last version 3.5 sometime crash I have 100.000 photo, two dbase, one for work and one for hobby when i use the flag or label, when I use workflow, there is not an exact reason or exact moment. I note that the workflow, also in 3.4 and 3.5 is not perfect I noticed that the workflow (button B) does not store the actions previously saved, and I have to set it again every time you open the action (conversion to jpeg-resize-watermark ...) thanks that all do you think that is bettere to compile youself digikam? or is the same to download from the repo? *** Bug 330302 has been marked as a duplicate of this bug. *** *** Bug 330370 has been marked as a duplicate of this bug. *** *** Bug 330633 has been marked as a duplicate of this bug. *** *** Bug 330644 has been marked as a duplicate of this bug. *** *** Bug 330674 has been marked as a duplicate of this bug. *** Crashes here on current master, this happened while trying to open a file to editor window: Application: digiKam (digikam), signal: Segmentation fault Using host libthread_db library "/usr/lib/libthread_db.so.1". [Current thread is 1 (Thread 0x7f6e01e40980 (LWP 684))] Thread 9 (Thread 0x7f6dd9d2a700 (LWP 689)): #0 0x00007f6df47b387d in poll () from /usr/lib/libc.so.6 #1 0x00007f6decbe3908 in ?? () from /usr/lib/libusb-1.0.so.0 #2 0x00007f6df99730a2 in start_thread () from /usr/lib/libpthread.so.0 #3 0x00007f6df47bc32d in clone () from /usr/lib/libc.so.6 Thread 8 (Thread 0x7f6dd36ef700 (LWP 690)): #0 0x00007f6df997703f in pthread_cond_wait@@GLIBC_2.3.2 () from /usr/lib/libpthread.so.0 #1 0x00007f6df55b9aa8 in wait (time=18446744073709551615, this=0x1d4b030) at thread/qwaitcondition_unix.cpp:86 #2 QWaitCondition::wait (this=<optimized out>, mutex=0x1d4af68, time=18446744073709551615) at thread/qwaitcondition_unix.cpp:158 #3 0x0000000000696d41 in Digikam::ScanController::run (this=0x1cf1a50) at /home/tpr/storage/kde/digikam-sc/core/digikam/database/scancontroller.cpp:725 #4 0x00007f6df55b95b5 in QThreadPrivate::start (arg=0x1cf1a50) at thread/qthread_unix.cpp:338 #5 0x00007f6df99730a2 in start_thread () from /usr/lib/libpthread.so.0 #6 0x00007f6df47bc32d in clone () from /usr/lib/libc.so.6 Thread 7 (Thread 0x7f6dd2eee700 (LWP 691)): #0 0x00007f6df47b387d in poll () from /usr/lib/libc.so.6 #1 0x00007f6df115d584 in ?? () from /usr/lib/libglib-2.0.so.0 #2 0x00007f6df115d68c in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0 #3 0x00007f6df56f5286 in QEventDispatcherGlib::processEvents (this=0x7f6dc40008c0, flags=...) at kernel/qeventdispatcher_glib.cpp:427 #4 0x00007f6df56c3b5f in QEventLoop::processEvents (this=this@entry=0x7f6dd2eedc20, flags=...) at kernel/qeventloop.cpp:149 #5 0x00007f6df56c3e05 in QEventLoop::exec (this=this@entry=0x7f6dd2eedc20, flags=...) at kernel/qeventloop.cpp:204 #6 0x00007f6df55b706d in QThread::exec (this=this@entry=0x1b01060) at thread/qthread.cpp:536 #7 0x00007f6df56a3ce8 in QInotifyFileSystemWatcherEngine::run (this=0x1b01060) at io/qfilesystemwatcher_inotify.cpp:256 #8 0x00007f6df55b95b5 in QThreadPrivate::start (arg=0x1b01060) at thread/qthread_unix.cpp:338 #9 0x00007f6df99730a2 in start_thread () from /usr/lib/libpthread.so.0 #10 0x00007f6df47bc32d in clone () from /usr/lib/libc.so.6 Thread 6 (Thread 0x7f6dd26ed700 (LWP 693)): #0 0x00007f6df997703f in pthread_cond_wait@@GLIBC_2.3.2 () from /usr/lib/libpthread.so.0 #1 0x00007f6df55b9aa8 in wait (time=18446744073709551615, this=0x1e8d450) at thread/qwaitcondition_unix.cpp:86 #2 QWaitCondition::wait (this=<optimized out>, mutex=0x1e8dbd8, time=18446744073709551615) at thread/qwaitcondition_unix.cpp:158 #3 0x00007f6dfeecd9c0 in Digikam::ParkingThread::run (this=0x1e8dbc0) at /home/tpr/storage/kde/digikam-sc/core/libs/threads/threadmanager.cpp:119 #4 0x00007f6df55b95b5 in QThreadPrivate::start (arg=0x1e8dbc0) at thread/qthread_unix.cpp:338 #5 0x00007f6df99730a2 in start_thread () from /usr/lib/libpthread.so.0 #6 0x00007f6df47bc32d in clone () from /usr/lib/libc.so.6 Thread 5 (Thread 0x7f6dacff9700 (LWP 704)): #0 0x00007f6df99773e8 in pthread_cond_timedwait@@GLIBC_2.3.2 () from /usr/lib/libpthread.so.0 #1 0x00007f6df55b9a84 in wait (time=30000, this=0x1e2edd0) at thread/qwaitcondition_unix.cpp:84 #2 QWaitCondition::wait (this=<optimized out>, mutex=mutex@entry=0x1bda998, time=30000) at thread/qwaitcondition_unix.cpp:158 #3 0x00007f6df55acf05 in QThreadPoolThread::run (this=0x3c23080) at concurrent/qthreadpool.cpp:141 #4 0x00007f6df55b95b5 in QThreadPrivate::start (arg=0x3c23080) at thread/qthread_unix.cpp:338 #5 0x00007f6df99730a2 in start_thread () from /usr/lib/libpthread.so.0 #6 0x00007f6df47bc32d in clone () from /usr/lib/libc.so.6 Thread 4 (Thread 0x7f6d9f7fe700 (LWP 706)): #0 0x00007f6df99773e8 in pthread_cond_timedwait@@GLIBC_2.3.2 () from /usr/lib/libpthread.so.0 #1 0x00007f6df55b9a84 in wait (time=30000, this=0x1e2edd0) at thread/qwaitcondition_unix.cpp:84 #2 QWaitCondition::wait (this=<optimized out>, mutex=mutex@entry=0x1bda998, time=30000) at thread/qwaitcondition_unix.cpp:158 #3 0x00007f6df55acf05 in QThreadPoolThread::run (this=0x3c23940) at concurrent/qthreadpool.cpp:141 #4 0x00007f6df55b95b5 in QThreadPrivate::start (arg=0x3c23940) at thread/qthread_unix.cpp:338 #5 0x00007f6df99730a2 in start_thread () from /usr/lib/libpthread.so.0 #6 0x00007f6df47bc32d in clone () from /usr/lib/libc.so.6 Thread 3 (Thread 0x7f6d83fff700 (LWP 712)): #0 0x00007f6df99773e8 in pthread_cond_timedwait@@GLIBC_2.3.2 () from /usr/lib/libpthread.so.0 #1 0x00007f6df55b9a84 in wait (time=30000, this=0x1e2edd0) at thread/qwaitcondition_unix.cpp:84 #2 QWaitCondition::wait (this=<optimized out>, mutex=mutex@entry=0x1bda998, time=30000) at thread/qwaitcondition_unix.cpp:158 #3 0x00007f6df55acf05 in QThreadPoolThread::run (this=0x3c25380) at concurrent/qthreadpool.cpp:141 #4 0x00007f6df55b95b5 in QThreadPrivate::start (arg=0x3c25380) at thread/qthread_unix.cpp:338 #5 0x00007f6df99730a2 in start_thread () from /usr/lib/libpthread.so.0 #6 0x00007f6df47bc32d in clone () from /usr/lib/libc.so.6 Thread 2 (Thread 0x7f6d7bfef700 (LWP 728)): #0 0x00007f6df47b54f3 in select () from /usr/lib/libc.so.6 #1 0x00007f6df56a09d3 in QProcessManager::run (this=0x7f6df5a39520 <processManager()::processManager>) at io/qprocess_unix.cpp:247 #2 0x00007f6df55b95b5 in QThreadPrivate::start (arg=0x7f6df5a39520 <processManager()::processManager>) at thread/qthread_unix.cpp:338 #3 0x00007f6df99730a2 in start_thread () from /usr/lib/libpthread.so.0 #4 0x00007f6df47bc32d in clone () from /usr/lib/libc.so.6 Thread 1 (Thread 0x7f6e01e40980 (LWP 684)): [KCrash Handler] #5 0x00007f6ddd419419 in sqlite3MemCompare (pMem1=pMem1@entry=0x7fff04c04700, pMem2=<optimized out>, pColl=0x1c57810) at sqlite3.c:60482 #6 0x00007f6ddd4195d3 in sqlite3VdbeRecordCompare (nKey1=32, pKey1=0x7f6dcc02bddc, pPKey2=pPKey2@entry=0x7fff04c04a10) at sqlite3.c:64160 #7 0x00007f6ddd42da99 in sqlite3BtreeMovetoUnpacked (pCur=0x6513b90, pIdxKey=0x7fff04c04a10, intKey=0, biasRight=<optimized out>, pRes=0x7fff04c04a00) at sqlite3.c:55075 #8 0x00007f6ddd455d42 in sqlite3VdbeExec (p=p@entry=0x6513db8) at sqlite3.c:70166 #9 0x00007f6ddd45e267 in sqlite3Step (p=0x6513db8) at sqlite3.c:64826 #10 sqlite3_step (pStmt=<optimized out>) at sqlite3.c:64892 #11 0x00007f6dd1ce6f88 in QSQLiteResultPrivate::fetchNext (this=this@entry=0x65145f0, values=..., idx=idx@entry=0, initialFetch=initialFetch@entry=true) at ../../../sql/drivers/sqlite/qsql_sqlite.cpp:235 #12 0x00007f6dd1ce7e57 in QSQLiteResult::exec (this=0x64e2c00) at ../../../sql/drivers/sqlite/qsql_sqlite.cpp:447 #13 0x00007f6e01aa3ced in QSqlQuery::exec (this=0x7fff04c04ff0) at kernel/qsqlquery.cpp:949 #14 0x00007f6dfee65947 in Digikam::DatabaseCoreBackend::exec (this=0x1a81d10, query=...) at /home/tpr/storage/kde/digikam-sc/core/libs/database/core/databasecorebackend.cpp:1415 #15 0x00007f6dfee65a79 in Digikam::DatabaseCoreBackend::execQuery (this=0x1a81d10, query=..., boundValue1=...) at /home/tpr/storage/kde/digikam-sc/core/libs/database/core/databasecorebackend.cpp:1057 #16 0x00007f6dfee651e8 in Digikam::DatabaseCoreBackend::execQuery (this=0x1a81d10, sql=..., boundValue1=...) at /home/tpr/storage/kde/digikam-sc/core/libs/database/core/databasecorebackend.cpp:1006 #17 0x00007f6dfee6512a in Digikam::DatabaseCoreBackend::execSql (this=0x1a81d10, sql=..., boundValue1=..., values=0x7fff04c050b8, lastInsertId=0x0) at /home/tpr/storage/kde/digikam-sc/core/libs/database/core/databasecorebackend.cpp:903 #18 0x00007f6dfe815324 in Digikam::AlbumDB::getSetting (this=0x1a801a0, keyword=...) at /home/tpr/storage/kde/digikam-sc/core/libs/database/albumdb.cpp:970 #19 0x00007f6dfe8154fc in Digikam::AlbumDB::getFilterSettings (this=0x1a801a0, imageFilter=0x7fff04c05310, videoFilter=0x0, audioFilter=0x0) at /home/tpr/storage/kde/digikam-sc/core/libs/database/albumdb.cpp:1017 #20 0x000000000074c906 in Digikam::AlbumSettings::getImageFileFilter (this=0x1bfef50) at /home/tpr/storage/kde/digikam-sc/core/digikam/utils/albumsettings.cpp:919 #21 0x00000000006f2ad7 in Digikam::ImageViewUtilities::openInEditor (this=0x20dc960, info=..., allInfosToOpen=..., currentAlbum=0x4676e80) at /home/tpr/storage/kde/digikam-sc/core/digikam/items/imageviewutilities.cpp:267 #22 0x00000000007752ce in Digikam::DigikamView::slotEditor (this=0x1f85940) at /home/tpr/storage/kde/digikam-sc/core/digikam/views/digikamview.cpp:1666 #23 0x00000000007747a5 in Digikam::DigikamView::slotImageEdit (this=0x1f85940) at /home/tpr/storage/kde/digikam-sc/core/digikam/views/digikamview.cpp:1700 #24 0x000000000077123d in Digikam::DigikamView::qt_static_metacall (_o=0x1f85940, _c=QMetaObject::InvokeMetaMethod, _id=60, _a=0x7fff04c05750) at /home/tpr/storage/kde/digikam-sc/core/build/digikam/digikamview.moc:308 #25 0x00007f6df56dae48 in QMetaObject::activate (sender=sender@entry=0x2f59030, m=m@entry=0x7f6df6eab1a0 <QAction::staticMetaObject>, local_signal_index=local_signal_index@entry=1, argv=argv@entry=0x7fff04c05750) at kernel/qobject.cpp:3547 #26 0x00007f6df633ecc2 in QAction::triggered (this=this@entry=0x2f59030, _t1=false) at .moc/debug-shared/moc_qaction.cpp:276 #27 0x00007f6df6340813 in QAction::activate (this=this@entry=0x2f59030, event=event@entry=QAction::Trigger) at kernel/qaction.cpp:1257 #28 0x00007f6df67c26c9 in QMenuPrivate::activateCausedStack (this=this@entry=0x5eb0ad0, causedStack=..., action=action@entry=0x2f59030, action_e=action_e@entry=QAction::Trigger, self=self@entry=true) at widgets/qmenu.cpp:1038 #29 0x00007f6df67c7149 in QMenuPrivate::activateAction (this=0x5eb0ad0, action=0x2f59030, action_e=QAction::Trigger, self=<optimized out>) at widgets/qmenu.cpp:1130 #30 0x00007f6df71df355 in KMenu::mouseReleaseEvent(QMouseEvent*) () from /usr/lib/libkdeui.so.5 #31 0x00007f6df639dab8 in QWidget::event (this=this@entry=0x7fff04c068a0, event=event@entry=0x7fff04c05e80) at kernel/qwidget.cpp:8376 #32 0x00007f6df67cb75b in QMenu::event (this=0x7fff04c068a0, e=0x7fff04c05e80) at widgets/qmenu.cpp:2481 #33 0x00007f6df63454a1 in QApplicationPrivate::notify_helper (this=this@entry=0x19c06c0, receiver=receiver@entry=0x7fff04c068a0, e=e@entry=0x7fff04c05e80) at kernel/qapplication.cpp:4562 #34 0x00007f6df634dd10 in QApplication::notify (this=<optimized out>, receiver=0x7fff04c068a0, e=0x7fff04c05e80) at kernel/qapplication.cpp:4105 #35 0x00007f6df712877a in KApplication::notify(QObject*, QEvent*) () from /usr/lib/libkdeui.so.5 #36 0x00007f6df56c572d in QCoreApplication::notifyInternal (this=0x7fff04c080a8, receiver=receiver@entry=0x7fff04c068a0, event=event@entry=0x7fff04c05e80) at kernel/qcoreapplication.cpp:949 #37 0x00007f6df634bb82 in sendEvent (event=<optimized out>, receiver=<optimized out>) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:231 #38 QApplicationPrivate::sendMouseEvent (receiver=receiver@entry=0x7fff04c068a0, event=event@entry=0x7fff04c05e80, alienWidget=alienWidget@entry=0x0, nativeWidget=nativeWidget@entry=0x7fff04c068a0, buttonDown=buttonDown@entry=0x7f6df6ee6358 <qt_button_down>, lastMouseReceiver=..., spontaneous=spontaneous@entry=true) at kernel/qapplication.cpp:3173 #39 0x00007f6df63c8bfc in QETWidget::translateMouseEvent (this=this@entry=0x7fff04c068a0, event=event@entry=0x7fff04c061c0) at kernel/qapplication_x11.cpp:4451 #40 0x00007f6df63c72a1 in QApplication::x11ProcessEvent (this=0x7fff04c080a8, event=event@entry=0x7fff04c061c0) at kernel/qapplication_x11.cpp:3640 #41 0x00007f6df63ef2f2 in x11EventSourceDispatch (s=0x19bf050, callback=0x0, user_data=0x0) at kernel/qguieventdispatcher_glib.cpp:146 #42 0x00007f6df115d296 in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0 #43 0x00007f6df115d5e8 in ?? () from /usr/lib/libglib-2.0.so.0 #44 0x00007f6df115d68c in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0 #45 0x00007f6df56f5265 in QEventDispatcherGlib::processEvents (this=0x18b92f0, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #46 0x00007f6df63ef3e6 in QGuiEventDispatcherGlib::processEvents (this=<optimized out>, flags=...) at kernel/qguieventdispatcher_glib.cpp:204 #47 0x00007f6df56c3b5f in QEventLoop::processEvents (this=this@entry=0x7fff04c065c0, flags=...) at kernel/qeventloop.cpp:149 #48 0x00007f6df56c3e05 in QEventLoop::exec (this=this@entry=0x7fff04c065c0, flags=...) at kernel/qeventloop.cpp:204 #49 0x00007f6df67ca507 in QMenu::exec (this=0x7fff04c068a0, p=..., action=0x0) at widgets/qmenu.cpp:2125 #50 0x000000000075ac14 in Digikam::ContextMenuHelper::exec (this=0x7fff04c06888, pos=..., at=0x0) at /home/tpr/storage/kde/digikam-sc/core/digikam/utils/contextmenuhelper.cpp:1132 #51 0x0000000000780462 in Digikam::ImagePreviewView::slotShowContextMenu (this=0x20b32f0, event=0x7fff04c06ec0) at /home/tpr/storage/kde/digikam-sc/core/digikam/views/imagepreviewview.cpp:418 #52 0x000000000077ec3c in Digikam::ImagePreviewView::qt_static_metacall (_o=0x20b32f0, _c=QMetaObject::InvokeMetaMethod, _id=28, _a=0x7fff04c06a70) at /home/tpr/storage/kde/digikam-sc/core/build/digikam/imagepreviewview.moc:126 #53 0x00007f6df56dae48 in QMetaObject::activate (sender=0x207d0c0, m=<optimized out>, local_signal_index=<optimized out>, argv=0x7fff04c06a70) at kernel/qobject.cpp:3547 #54 0x00007f6dfefc074f in Digikam::GraphicsDImgItem::showContextMenu (this=0x207d0c0, _t1=0x7fff04c06ec0) at /home/tpr/storage/kde/digikam-sc/core/build/digikam/graphicsdimgitem.moc:103 #55 0x00007f6dfefc1a6d in Digikam::GraphicsDImgItem::contextMenuEvent (this=0x207d0c0, e=0x7fff04c06ec0) at /home/tpr/storage/kde/digikam-sc/core/libs/widgets/graphicsview/graphicsdimgitem.cpp:236 #56 0x00007f6dfefc1aaf in non-virtual thunk to Digikam::GraphicsDImgItem::contextMenuEvent(QGraphicsSceneContextMenuEvent*) () at /home/tpr/storage/kde/digikam-sc/core/libs/widgets/graphicsview/graphicsdimgitem.cpp:237 #57 0x00007f6df6968f97 in QGraphicsItem::sceneEvent (this=0x207d0d0, event=0x7fff04c06ec0) at graphicsview/qgraphicsitem.cpp:6720 #58 0x00007f6df69948af in QGraphicsScene::contextMenuEvent (this=<optimized out>, contextMenuEvent=0x7fff04c06ec0) at graphicsview/qgraphicsscene.cpp:3617 #59 0x00007f6df69ab8e5 in QGraphicsScene::event (this=0x20cfdc0, event=0x7fff04c06ec0) at graphicsview/qgraphicsscene.cpp:3412 #60 0x00007f6df63454a1 in QApplicationPrivate::notify_helper (this=this@entry=0x19c06c0, receiver=receiver@entry=0x20cfdc0, e=e@entry=0x7fff04c06ec0) at kernel/qapplication.cpp:4562 #61 0x00007f6df634c33d in QApplication::notify (this=0x7fff04c080a8, receiver=0x20cfdc0, e=0x7fff04c06ec0) at kernel/qapplication.cpp:4348 #62 0x00007f6df712877a in KApplication::notify(QObject*, QEvent*) () from /usr/lib/libkdeui.so.5 #63 0x00007f6df56c572d in QCoreApplication::notifyInternal (this=0x7fff04c080a8, receiver=0x20cfdc0, event=event@entry=0x7fff04c06ec0) at kernel/qcoreapplication.cpp:949 #64 0x00007f6df69c6117 in sendEvent (event=0x7fff04c06ec0, receiver=<optimized out>) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:231 #65 QGraphicsView::contextMenuEvent (this=0x20b32f0, event=0x7fff04c073a0) at graphicsview/qgraphicsview.cpp:2892 #66 0x00007f6df639de3a in QWidget::event (this=this@entry=0x20b32f0, event=event@entry=0x7fff04c073a0) at kernel/qwidget.cpp:8554 #67 0x00007f6df678592e in QFrame::event (this=0x20b32f0, e=0x7fff04c073a0) at widgets/qframe.cpp:557 #68 0x00007f6df69c5bb8 in QGraphicsView::viewportEvent (this=0x20b32f0, event=0x7fff04c073a0) at graphicsview/qgraphicsview.cpp:2866 #69 0x00007f6df56c5907 in QCoreApplicationPrivate::sendThroughObjectEventFilters (this=this@entry=0x19c06c0, receiver=receiver@entry=0x20d1c90, event=event@entry=0x7fff04c073a0) at kernel/qcoreapplication.cpp:1059 #70 0x00007f6df6345491 in QApplicationPrivate::notify_helper (this=this@entry=0x19c06c0, receiver=receiver@entry=0x20d1c90, e=e@entry=0x7fff04c073a0) at kernel/qapplication.cpp:4558 #71 0x00007f6df634da3f in QApplication::notify (this=<optimized out>, receiver=0x20d1c90, e=0x7fff04c073a0) at kernel/qapplication.cpp:4184 #72 0x00007f6df712877a in KApplication::notify(QObject*, QEvent*) () from /usr/lib/libkdeui.so.5 #73 0x00007f6df56c572d in QCoreApplication::notifyInternal (this=0x7fff04c080a8, receiver=receiver@entry=0x20d1c90, event=event@entry=0x7fff04c073a0) at kernel/qcoreapplication.cpp:949 #74 0x00007f6df63c88f0 in sendSpontaneousEvent (event=0x7fff04c073a0, receiver=0x20d1c90) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:234 #75 QETWidget::translateMouseEvent (this=this@entry=0x20b32f0, event=event@entry=0x7fff04c076e0) at kernel/qapplication_x11.cpp:4522 #76 0x00007f6df63c72a1 in QApplication::x11ProcessEvent (this=0x7fff04c080a8, event=event@entry=0x7fff04c076e0) at kernel/qapplication_x11.cpp:3640 #77 0x00007f6df63ef2f2 in x11EventSourceDispatch (s=0x19bf050, callback=0x0, user_data=0x0) at kernel/qguieventdispatcher_glib.cpp:146 #78 0x00007f6df115d296 in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0 #79 0x00007f6df115d5e8 in ?? () from /usr/lib/libglib-2.0.so.0 #80 0x00007f6df115d68c in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0 #81 0x00007f6df56f5265 in QEventDispatcherGlib::processEvents (this=0x18b92f0, flags=...) at kernel/qeventdispatcher_glib.cpp:425 #82 0x00007f6df63ef3e6 in QGuiEventDispatcherGlib::processEvents (this=<optimized out>, flags=...) at kernel/qguieventdispatcher_glib.cpp:204 #83 0x00007f6df56c3b5f in QEventLoop::processEvents (this=this@entry=0x7fff04c07ad0, flags=...) at kernel/qeventloop.cpp:149 #84 0x00007f6df56c3e05 in QEventLoop::exec (this=this@entry=0x7fff04c07ad0, flags=...) at kernel/qeventloop.cpp:204 #85 0x00007f6df56c9c89 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1221 #86 0x000000000082248b in main (argc=1, argv=0x7fff04c082c8) at /home/tpr/storage/kde/digikam-sc/core/digikam/main/main.cpp:236 It's not reproducible here... digiKam version 4.0.0-beta3 Demosaic GPL2 pack support: No Demosaic GPL3 pack support: No Exiv2 can write to Jp2: Yes Exiv2 can write to Jpeg: Yes Exiv2 can write to Pgf: Yes Exiv2 can write to Png: Yes Exiv2 can write to Tiff: Yes Exiv2 supports XMP metadata: Yes LibCImg: 130 LibEigen: 3.1.2 LibExiv2: 0.23 LibJPEG: 80 LibJasper: 1.900.1 LibKDE: 4.10.5 LibKExiv2: 2.3.1 LibKGeoMap: 2.0.0 LibKdcraw: 2.4.2 LibLCMS: 2050 LibLensFun: 0.2.6-0 LibPGF: 6.13.45 - internal library LibPNG: 1.5.13 LibQt: 4.8.5 LibRaw: 0.16.0-Alpha2 LibTIFF: LIBTIFF, Version 4.0.3 Copyright (c) 1988-1996 Sam Leffler Copyright (c) 1991-1996 Silicon Graphics, Inc. Marble Widget: 0.15.1 (stable version) Parallelized PGF codec: No Parallelized demosaicing: Yes RawSpeed codec support: No Database backend: QSQLITE Kipi-Plugins: 4.0.0-beta3 LibGphoto2: 2.5.2 LibKface: 3.0.0 LibKipi: 2.1.0 LibOpenCV: 2.4.3 *** Bug 331220 has been marked as a duplicate of this bug. *** After a recent Gentoo Linux update I also had lots of those crashes. It really drove me nuts because they all happened by simply selecting an image of a folder and it didn't take many clicks (sometimes 2-3 were enough). Searching the Internet soon showed the right direction: sqlite 3.8 After downgrading sqlite 3.8.2 to 3.7.17 everything is fine again. No more crashes! So I wonder what sqlite the OP uses. Best regards, Andreas sqlite-3.8.2-1.fc20.x86_64 @André Johansen: Already tried to downgrade sqlite to 3.7.17? *** Bug 332100 has been marked as a duplicate of this bug. *** *** Bug 333243 has been marked as a duplicate of this bug. *** I can confirm experiences of Andreas Mair in comment #13: I also use Gentoo Linux. Since a few weeks, digikam crashes at all kinds of actions: Editing photos, assigning tags, ... KDE crash handler always lists sqlite: Thread 1 (Thread 0x7f6245ec5800 (LWP 1870)): [KCrash Handler] #6 0x00000000036ed770 in ?? () #7 0x00007f62310d0dae in sqlite3MemCompare (pMem1=<optimized out>, pMem2=0x3ea0728, pColl=0x4a647b8) at sqlite3.c:60468 #8 0x00007f62310d10dd in sqlite3VdbeRecordCompare (nKey1=18, pKey1=0x7f62242528e9, pPKey2=0x7ffff2e9cbe0) at sqlite3.c:64160 #9 0x00007f62310f277b in sqlite3BtreeMovetoUnpacked (pRes=<optimized out>, biasRight=<optimized out>, intKey=<optimized out>, pIdxKey=<optimized out>, pCur=<optimized out>) at sqlite3.c:55075 #10 sqlite3BtreeMovetoUnpacked (pCur=0x42fc920, pIdxKey=0x7ffff2e9cbe0, intKey=0, biasRight=<optimized out>, pRes=0x7ffff2e9cbd0) at sqlite3.c:54960 #11 0x00007f62310fde0e in sqlite3VdbeExec (p=0xaf72d78) at sqlite3.c:70166 #12 0x00007f623110645f in sqlite3Step (p=0xaf72d78) at sqlite3.c:64826 ... Looking at my emerge.log, I did an update of "dev-db/sqlite-3.7.17" to "dev-db/sqlite-3.8.2" 8 weeks ago. > After downgrading sqlite 3.8.2 to 3.7.17 everything is fine again. No more crashes! Thanks for the tip! By today, there is no more "sqlite-3.7.x" in portage tree. So I will try the current top up-to-date version "dev-db/sqlite-3.8.4.3". I filed a bug report at gentoo's bugtracker, too: https://bugs.gentoo.org/show_bug.cgi?id=507394 *** Bug 333389 has been marked as a duplicate of this bug. *** *** Bug 333642 has been marked as a duplicate of this bug. *** *** Bug 333671 has been marked as a duplicate of this bug. *** *** Bug 333660 has been marked as a duplicate of this bug. *** *** Bug 333741 has been marked as a duplicate of this bug. *** *** Bug 333700 has been marked as a duplicate of this bug. *** *** Bug 333791 has been marked as a duplicate of this bug. *** *** Bug 333792 has been marked as a duplicate of this bug. *** *** Bug 333790 has been marked as a duplicate of this bug. *** Created attachment 86274 [details]
New crash information added by DrKonqi
digikam (3.5.0) on KDE Platform 4.13.0 using Qt 4.8.6
- What I was doing when the application crashed:
I add Tags to potos. But digicam crashes als in other situations. I have this problem after the update to Kubuntu 14.04.
-- Backtrace (Reduced):
#6 0x00007fbcf3bc3da9 in sqlite3MemCompare (pMem1=pMem1@entry=0x7fffecb86cf0, pMem2=<optimized out>, pColl=0x8695a98) at sqlite3.c:60484
#7 0x00007fbcf3bc3f63 in sqlite3VdbeRecordCompare (nKey1=17, pKey1=0x7fbcdc342557, pPKey2=pPKey2@entry=0x7fffecb87008) at sqlite3.c:64162
#8 0x00007fbcf3bd8579 in sqlite3BtreeMovetoUnpacked (pCur=0xb3d6418, pIdxKey=0x7fffecb87008, intKey=0, biasRight=<optimized out>, pRes=0x7fffecb86ff0) at sqlite3.c:55077
#9 0x00007fbcf3c00848 in sqlite3VdbeExec (p=p@entry=0xa9dda78) at sqlite3.c:70345
#10 0x00007fbcf3c08ed7 in sqlite3Step (p=0xa9dda78) at sqlite3.c:64828
It sound like a binary compatibility issue with sqlite package against digiKam (through Qt4 Sqlite plugin). digiKam is not linked to Sqlite directly. A lots of people report the same problem at the same time. Nothing has changed in digiKam DB interface since a long time. So for me, it's a side effect in packaging, perhaps in Qt4, perhaps in Sqlite, i don't know. Crash is not reproducible here under Mageia 3 and OSX (through updated macport) Which Sqlite version is used ? Which distro is used ? Which Qt4 version is used ? Gilles Caulier Dear Gilles Caulier, thanks for the answer. I belive it's a problem with the database. When I make changes in the tags, a process starts and after a while DigiKam crashes. I have installed: sqlite3 --> 3.8.2 2013-12-06 14:53:30 qt --> 4.8.5 distro --> Kubuntu 14.04 Pierre Metzner Some users have clearly pointed the problem to an update SQLite 3.7 -> 3.8. There could be incompatibilities with the Qt SQLite driver, I would not assume that the problem can be in any digikam code - multiple code paths from within digikam lead through the Qt SQL driver to a crash in a common location. valgrind may or may not give some further information. (In reply to comment #30) Same problem here with versions $ sqlite3 -version 3.8.2 2013-12-06 14:53:30 Ubuntu 14.04 LTS libqtcore4 has version 4.8.5 *** Bug 333952 has been marked as a duplicate of this bug. *** *** Bug 333953 has been marked as a duplicate of this bug. *** *** Bug 333976 has been marked as a duplicate of this bug. *** (In reply to comment #31) Hello, I confirm the issue in kubuntu 14.04 + sqlite + qt4. Digikam often crashes, mostly when working with tags. Best regards Frantisek *** Bug 334017 has been marked as a duplicate of this bug. *** *** Bug 334042 has been marked as a duplicate of this bug. *** *** Bug 333787 has been marked as a duplicate of this bug. *** *** Bug 334105 has been marked as a duplicate of this bug. *** Has this been reported to an upstream (Qt/Sqlite?), perhaps they could have an idea what'd be the problem? Hi Teemu, No i think it don't have been yet reported as upstream. Gilles Created attachment 86363 [details]
New crash information added by DrKonqi
digikam (3.5.0) on KDE Platform 4.11.5 using Qt 4.8.5
- What I was doing when the application crashed:
Browsing albums. I confirm this started to frequently happen after upgrading sqlite from 3.7 to 3.8.
-- Backtrace (Reduced):
#7 0x00007fd62f57a566 in sqlite3MemCompare (pMem1=pMem1@entry=0x7fff88c12e30, pMem2=<optimized out>, pColl=0xef7948) at sqlite3.c:60482
#8 0x00007fd62f57a968 in sqlite3VdbeRecordCompare (nKey1=19, pKey1=0x7fd62417a018, pPKey2=pPKey2@entry=0x7fff88c13290) at sqlite3.c:64160
#9 0x00007fd62f59eeb7 in sqlite3BtreeMovetoUnpacked (pRes=<optimized out>, biasRight=<optimized out>, intKey=<optimized out>, pIdxKey=<optimized out>, pCur=<optimized out>) at sqlite3.c:55075
#10 sqlite3BtreeMovetoUnpacked (pCur=0x32880e0, pIdxKey=0x7fff88c13290, intKey=0, biasRight=<optimized out>, pRes=0x7fff88c13280) at sqlite3.c:54960
#11 0x00007fd62f5a777e in sqlite3VdbeExec (p=p@entry=0x114ebd8) at sqlite3.c:70166
*** Bug 334186 has been marked as a duplicate of this bug. *** *** Bug 334189 has been marked as a duplicate of this bug. *** Since an auto-update to sqlite 3.8.3, this bug seems to have stopped occurring, in my Fedora 20 system. Hi Malcolm, This what i suspected a lot... Gilles Caulier I have similar results as Malcolm in comment #47: Since I am using "dev-db/sqlite-3.8.4.3" (see comment #18), I been working several hours with digikam 3.5.0 by now and processing more than 640 picture without one single sqlite-crash as mentioned above. :) So this problem seems to be limited to sqlite version 3.8.2.x. *** Bug 334310 has been marked as a duplicate of this bug. *** *** Bug 334344 has been marked as a duplicate of this bug. *** *** Bug 334350 has been marked as a duplicate of this bug. *** *** Bug 334443 has been marked as a duplicate of this bug. *** Looks like dev-db/sqlite-3.8.4.3 fixed issues for me too. Ok thanks I close this file as UPSTREAM Gilles Caulier Any recommendation? -> migrate to mysql -> downgrade sqlite, e.g.? Axel It's a Sqlite bug. You must upgrate to new sqlite release, including an upgrate of QtSlqite plugin, else plroblem will not resolved for digiKam. This a weird side-effect of downstream bug which downgrade stability of client application. As Sqlite is used in a lots of appplication, i'm sure that digiKam is not the only one affected by this problem. Sqlite package will be certainly updated in your distro quickly... No need to use Mysql here. Mysql interface in digiKam as old dysfunctions not yet fixed. Gilles Caulier FYI, I reported this issue for ubuntu at https://bugs.launchpad.net/ubuntu/+source/digikam/+bug/1315932 and asked for updating sqlite3 at https://bugs.launchpad.net/ubuntu/+source/sqlite3/+bug/1317449 . As a temporary workaround I use the sqlite3 (3.8.4) packages from debian testing, which solves this issue for me. *** Bug 334712 has been marked as a duplicate of this bug. *** *** Bug 334718 has been marked as a duplicate of this bug. *** *** Bug 334852 has been marked as a duplicate of this bug. *** *** Bug 334853 has been marked as a duplicate of this bug. *** *** Bug 334986 has been marked as a duplicate of this bug. *** *** Bug 335020 has been marked as a duplicate of this bug. *** Hi all, If you use Ubuntu, or any derivative such as Kububtu, please mark "This bug affects me" by clicking on "Does this bug affect you?" on the following page: https://bugs.launchpad.net/ubuntu/+source/sqlite3/+bug/1317449 Done. Thanks, Brylie. By the way, the Ubuntu bug is marked as a Wishlist bug since the fix seems to be upgrading the minor version of SQLite. However, since it's causing crashes, I believe it should be classified as a bug, not a wishlist item. Please also encourage Ubuntu to step up and fix this. Wishlist items in released distros tend to get ignored. *** Bug 335052 has been marked as a duplicate of this bug. *** *** Bug 335055 has been marked as a duplicate of this bug. *** *** Bug 335059 has been marked as a duplicate of this bug. *** *** Bug 335136 has been marked as a duplicate of this bug. *** *** Bug 335226 has been marked as a duplicate of this bug. *** *** Bug 335234 has been marked as a duplicate of this bug. *** *** Bug 335260 has been marked as a duplicate of this bug. *** *** Bug 335297 has been marked as a duplicate of this bug. *** The same problem here. A similar extract: Thread 1 (Thread 0x7f47e1b86840 (LWP 18412)): [KCrash Handler] #5 0x0000000000000052 in ?? () #6 0x00007f47c5eccdac in sqlite3MemCompare (pMem1=pMem1@entry=0x7fffb076d470, pMem2=<optimized out>, pColl=0x569c298) at sqlite3.c:60484 #7 0x00007f47c5eccf63 in sqlite3VdbeRecordCompare (nKey1=18, pKey1=0x7f47ac07489a, pPKey2=pPKey2@entry=0x7fffb076d770) at sqlite3.c:64162 #8 0x00007f47c5ee1579 in sqlite3BtreeMovetoUnpacked (pCur=0x54f45c0, pIdxKey=0x7fffb076d770, intKey=0, biasRight=<optimized out>, pRes=0x7fffb076d760) at sqlite3.c:55077 #9 0x00007f47c5f099c5 in sqlite3VdbeExec (p=p@entry=0x5dbce58) at sqlite3.c:70168 #10 0x00007f47c5f11ed7 in sqlite3Step (p=0x5dbce58) at sqlite3.c:64828 #11 sqlite3_step (pStmt=<optimized out>) at sqlite3.c:64894 #12 0x00007f47b28d211c in QSQLiteResultPrivate::fetchNext (this=this@entry=0x65e1ea0, values=..., idx=idx@entry=0, initialFetch=initialFetch@entry=true) at ../../../sql/drivers/sqlite/qsql_sqlite.cpp:235 I compiled digikam 4.0.0 from source. It was fine under ubuntu (12.10) but after upgrading to ubuntu 14.04 (sqlite 3.8.2) and recompiling, random crashes appeared. Since almost the same code base is used to compile in both cases, it could be confirmed that this is not an issue of digikam. (I have since made patches to other areas but should not be relevant to db access). Will try upgrading sqlite. *** Bug 335526 has been marked as a duplicate of this bug. *** *** Bug 335529 has been marked as a duplicate of this bug. *** *** Bug 335574 has been marked as a duplicate of this bug. *** *** Bug 335622 has been marked as a duplicate of this bug. *** *** Bug 335630 has been marked as a duplicate of this bug. *** *** Bug 335667 has been marked as a duplicate of this bug. *** *** Bug 335684 has been marked as a duplicate of this bug. *** *** Bug 335685 has been marked as a duplicate of this bug. *** *** Bug 335847 has been marked as a duplicate of this bug. *** *** Bug 335978 has been marked as a duplicate of this bug. *** *** Bug 336005 has been marked as a duplicate of this bug. *** *** Bug 336208 has been marked as a duplicate of this bug. *** *** Bug 336261 has been marked as a duplicate of this bug. *** *** Bug 336260 has been marked as a duplicate of this bug. *** *** Bug 336259 has been marked as a duplicate of this bug. *** Created attachment 87235 [details]
New crash information added by DrKonqi
digikam (4.0.0) on KDE Platform 4.13.1 using Qt 4.8.6
- What I was doing when the application crashed:
Another sample of the sql-related crash-when-opening-an-image-for-editing issue, on a freshly updated Kubuntu 14.04/KDE 4.13.1 system (Digikam was installed after said update).
-- Backtrace (Reduced):
#7 0x00007f1181b96dac in sqlite3MemCompare (pMem1=pMem1@entry=0x7fffe1e68ce0, pMem2=<optimized out>, pColl=0xa4ee338) at sqlite3.c:60484
#8 0x00007f1181b96f63 in sqlite3VdbeRecordCompare (nKey1=24, pKey1=0x7f11600979ae, pPKey2=pPKey2@entry=0x7fffe1e68fe0) at sqlite3.c:64162
#9 0x00007f1181bab579 in sqlite3BtreeMovetoUnpacked (pCur=0xadd9a50, pIdxKey=0x7fffe1e68fe0, intKey=0, biasRight=<optimized out>, pRes=0x7fffe1e68fd0) at sqlite3.c:55077
#10 0x00007f1181bd39c5 in sqlite3VdbeExec (p=p@entry=0x6b3e418) at sqlite3.c:70168
#11 0x00007f1181bdbed7 in sqlite3Step (p=0x6b3e418) at sqlite3.c:64828
Qt SQL driver need to be updated and also libsqlite. Updating digiKAm is not enough especially if packager don't take a care about this UPSTREAM problem.. As it have already said in this file, problem is located into sqlite implementation. Gilles Caulier Anyone managed to find updated (4.8.6) Qt packages for (K)Ubuntu? *** Bug 336514 has been marked as a duplicate of this bug. *** *** Bug 336869 has been marked as a duplicate of this bug. *** *** Bug 337018 has been marked as a duplicate of this bug. *** *** Bug 337146 has been marked as a duplicate of this bug. *** *** Bug 337258 has been marked as a duplicate of this bug. *** *** Bug 337278 has been marked as a duplicate of this bug. *** - What I was doing when the application crashed: I was adding a new tag to a picture. For some time I ran digikam against mysql, then I migrated back to sqlite. Since then digikam is crashing frequently. Also I enabled face detection. After migration from mysql to sqlite I hit an issue where tags were missing and digikam ran from a console reported, that there is no parent tag (-1). I changed parent tag from -1 to 0 (zero) in sqlite database, now tags are back. *** Bug 337607 has been marked as a duplicate of this bug. *** *** Bug 337839 has been marked as a duplicate of this bug. *** *** Bug 338164 has been marked as a duplicate of this bug. *** *** Bug 338144 has been marked as a duplicate of this bug. *** *** Bug 338358 has been marked as a duplicate of this bug. *** *** Bug 338448 has been marked as a duplicate of this bug. *** *** Bug 338600 has been marked as a duplicate of this bug. *** *** Bug 339068 has been marked as a duplicate of this bug. *** *** Bug 339070 has been marked as a duplicate of this bug. *** *** Bug 339263 has been marked as a duplicate of this bug. *** *** Bug 339650 has been marked as a duplicate of this bug. *** *** Bug 340792 has been marked as a duplicate of this bug. *** *** Bug 341529 has been marked as a duplicate of this bug. *** *** Bug 341929 has been marked as a duplicate of this bug. *** *** Bug 342050 has been marked as a duplicate of this bug. *** *** Bug 342143 has been marked as a duplicate of this bug. *** *** Bug 342433 has been marked as a duplicate of this bug. *** (In reply to b3nmore from comment #58) > FYI, I reported this issue for ubuntu at > https://bugs.launchpad.net/ubuntu/+source/digikam/+bug/1315932 and asked for > updating sqlite3 at > https://bugs.launchpad.net/ubuntu/+source/sqlite3/+bug/1317449 . As a > temporary workaround I use the sqlite3 (3.8.4) packages from debian testing, > which solves this issue for me. I set up a PPA for Ubuntu 14.04 LTS that has a newer sqlite3 build. I made my life easy and just rebuilt the utopic unicorn src dpkg, and I do not intend to support this; it's a makeshift arrangement. https://launchpad.net/~matthias-andree/+archive/ubuntu/trusty-fixes Ubuntu packagers aren't helpful and are asking that someone isolates the fix from the upgraded sqlite3 package. *** Bug 342750 has been marked as a duplicate of this bug. *** *** Bug 342802 has been marked as a duplicate of this bug. *** *** Bug 343014 has been marked as a duplicate of this bug. *** *** Bug 343243 has been marked as a duplicate of this bug. *** *** Bug 344216 has been marked as a duplicate of this bug. *** *** Bug 344299 has been marked as a duplicate of this bug. *** *** Bug 344587 has been marked as a duplicate of this bug. *** *** Bug 345044 has been marked as a duplicate of this bug. *** *** Bug 345402 has been marked as a duplicate of this bug. *** *** Bug 345907 has been marked as a duplicate of this bug. *** *** Bug 347054 has been marked as a duplicate of this bug. *** *** Bug 347107 has been marked as a duplicate of this bug. *** *** Bug 347340 has been marked as a duplicate of this bug. *** Created attachment 92487 [details]
New crash information added by DrKonqi
digikam (4.0.0) on KDE Platform 4.14.2 using Qt 4.8.6
- What I was doing when the application crashed:
Upon selecting a new album digiKam crashes 5 times out of 10. This happens especially when the album I just selected is stil generating thumbnails.
-- Backtrace (Reduced):
#6 0x00007f9ac91d0da9 in sqlite3MemCompare (pMem1=pMem1@entry=0x7fff2e5c2b90, pMem2=<optimized out>, pColl=0x137c098) at sqlite3.c:60484
#7 0x00007f9ac91d0f63 in sqlite3VdbeRecordCompare (nKey1=18, pKey1=0x7f9ab411c1af, pPKey2=pPKey2@entry=0x7fff2e5c2e90) at sqlite3.c:64162
#8 0x00007f9ac91e5579 in sqlite3BtreeMovetoUnpacked (pCur=0x430c220, pIdxKey=0x7fff2e5c2e90, intKey=0, biasRight=<optimized out>, pRes=0x7fff2e5c2e80) at sqlite3.c:55077
#9 0x00007f9ac920d9c5 in sqlite3VdbeExec (p=p@entry=0x500ebe8) at sqlite3.c:70168
#10 0x00007f9ac9215ed7 in sqlite3Step (p=0x500ebe8) at sqlite3.c:64828
Ben, and you also get these crashes if you upgrade sqlite3 package to version 3.8.4 or newer, as is suggested in the comments of this bug report? *** Bug 347450 has been marked as a duplicate of this bug. *** (In reply to Christoph Feck from comment #134) > Ben, and you also get these crashes if you upgrade sqlite3 package to > version 3.8.4 or newer, as is suggested in the comments of this bug report? I did update sqlite3 to the latest version available on my distro. The crash still happens, on a less regular bases though. It happens mainly when am switching albums while the album I am in still loads thumbnails. This is not enough to update sqlite. The qt-sqlite plugin must be updated too. Gilles Caulier *** Bug 341424 has been marked as a duplicate of this bug. *** *** Bug 347786 has been marked as a duplicate of this bug. *** First I tried to update some single packages in synaptic as also described in some comments. In the end I made a mistake and practically my complete GUI was deinstalled. At best I am a script kid... After a new install of ubuntu 14.04, the problem was still comparable. Now I tried the ppa made by Matthias Andree (Comment 119). This worked very well for me too. Digikam is now stable! Thanks a lot to Matthias! Am Sonntag, den 10.05.2015, 08:28 +0000 schrieb Gilles Caulier: > https://bugs.kde.org/show_bug.cgi?id=329697 > > Gilles Caulier <caulier.gilles@gmail.com> changed: > > What |Removed |Added > ---------------------------------------------------------------------------- > CC| |jabog6@yahoo.com > > --- Comment #138 from Gilles Caulier <caulier.gilles@gmail.com> --- > *** Bug 341424 has been marked as a duplicate of this bug. *** > Created attachment 93046 [details]
New crash information added by DrKonqi
digikam (4.0.0) on KDE Platform 4.14.2 using Qt 4.8.6
Selecting a picture in an album
It reproduces sometimes and is not related to any specific album.
-- Backtrace (Reduced):
#7 0x00007fe71a6d7dac in sqlite3MemCompare (pMem1=pMem1@entry=0x7fffc4a3c1f0, pMem2=<optimized out>, pColl=0x10d01118) at sqlite3.c:60484
#8 0x00007fe71a6d7f63 in sqlite3VdbeRecordCompare (nKey1=18, pKey1=0x7fe7041e026f, pPKey2=pPKey2@entry=0x7fffc4a3c4f0) at sqlite3.c:64162
#9 0x00007fe71a6ec579 in sqlite3BtreeMovetoUnpacked (pCur=0x110cfed0, pIdxKey=0x7fffc4a3c4f0, intKey=0, biasRight=<optimized out>, pRes=0x7fffc4a3c4e0) at sqlite3.c:55077
#10 0x00007fe71a7149c5 in sqlite3VdbeExec (p=p@entry=0x1226c408) at sqlite3.c:70168
#11 0x00007fe71a71ced7 in sqlite3Step (p=0x1226c408) at sqlite3.c:64828
*** Bug 350130 has been marked as a duplicate of this bug. *** *** Bug 351374 has been marked as a duplicate of this bug. *** *** Bug 351521 has been marked as a duplicate of this bug. *** *** Bug 352174 has been marked as a duplicate of this bug. *** *** Bug 352313 has been marked as a duplicate of this bug. *** *** Bug 355903 has been marked as a duplicate of this bug. *** *** Bug 355950 has been marked as a duplicate of this bug. *** *** Bug 356282 has been marked as a duplicate of this bug. *** *** Bug 356598 has been marked as a duplicate of this bug. *** *** Bug 357421 has been marked as a duplicate of this bug. *** *** Bug 358337 has been marked as a duplicate of this bug. *** *** Bug 358356 has been marked as a duplicate of this bug. *** *** Bug 358488 has been marked as a duplicate of this bug. *** *** Bug 358829 has been marked as a duplicate of this bug. *** *** Bug 358832 has been marked as a duplicate of this bug. *** *** Bug 359540 has been marked as a duplicate of this bug. *** *** Bug 359977 has been marked as a duplicate of this bug. *** *** Bug 360665 has been marked as a duplicate of this bug. *** *** Bug 363736 has been marked as a duplicate of this bug. *** *** Bug 364153 has been marked as a duplicate of this bug. *** *** Bug 374472 has been marked as a duplicate of this bug. *** |