Version: (using Devel) Installed from: Compiled sources Crashes just after displaying the album contents on startup. 1.2.0 on KDE 4.4.2. Backtrace follows ==2493== Thread 1: ==2493== Invalid read of size 8 ==2493== at 0xA2D9401: QTimeLine::stop() (qtimeline.h:139) ==2493== by 0x6DD13B: Digikam::RatingWidget::setFadingValue(int) (ratingwidget.cpp:170) ==2493== by 0x6BB034: Digikam::ImageRatingOverlay::slotEntered(QModelIndex const&) (imageratingoverlay.cpp:126) ==2493== by 0x76255F5: Digikam::AbstractWidgetDelegateOverlay::qt_metacall(QMetaObject::Call, int, void**) (imagedelegateoverlay.moc:151) ==2493== by 0x6BB66F: Digikam::ImageRatingOverlay::qt_metacall(QMetaObject::Call, int, void**) (imageratingoverlay.moc:74) ==2493== by 0xA38D78E: QMetaObject::activate(QObject*, QMetaObject const*, int, void**) (qobject.cpp:3293) ==2493== by 0x9581A74: QAbstractItemView::entered(QModelIndex const&) (in /usr/lib64/libQtGui.so.4.6.2) ==2493== by 0x6A851A: Digikam::ImageCategorizedView::slotDelayedEnter() (imagecategorizedview.cpp:408) ==2493== by 0x6AA28B: Digikam::ImageCategorizedView::qt_metacall(QMetaObject::Call, int, void**) (imagecategorizedview.moc:107) ==2493== by 0x692E8F: Digikam::DigikamImageView::qt_metacall(QMetaObject::Call, int, void**) (digikamimageview.moc:113) ==2493== by 0xA38D78E: QMetaObject::activate(QObject*, QMetaObject const*, int, void**) (qobject.cpp:3293) ==2493== by 0xA38A3E2: QObject::event(QEvent*) (qobject.cpp:1212) ==2493== Address 0x8 is not stack'd, malloc'd or (recently) free'd ==2493== KCrash: Application 'digikam' crashing... Thread 1 (Thread 0x7f9e61f4c860 (LWP 1373)): [KCrash Handler] #5 d_func (this=<value optimized out>) at tools/qtimeline.h:139 #6 QTimeLine::stop (this=<value optimized out>) at tools/qtimeline.cpp:723 #7 0x00000000006dd13c in Digikam::RatingWidget::setFadingValue (this=0xe3fc30, value=255) at /usr/src/debug/digikam-1.2.0/digikam/ratingwidget.cpp:170 #8 0x00000000006bb035 in Digikam::ImageRatingOverlay::slotEntered (this=0xe3f320, index=...) at /usr/src/debug/digikam-1.2.0/digikam/imageratingoverlay.cpp:126 #9 0x00007f9e5f4a15f6 in Digikam::AbstractWidgetDelegateOverlay::qt_metacall (this=0xe3f320, _c=InvokeMetaMethod, _id=<value optimized out>, _a=0x7fffd3407730) at /usr/src/debug/digikam-1.2.0/build/digikam/imagedelegateoverlay.moc:151 #10 0x00000000006bb670 in Digikam::ImageRatingOverlay::qt_metacall (this=0x0, _c=255, _id=14764688, _a=0xfffffffffff6938a) at /usr/src/debug/digikam-1.2.0/build/digikam/imageratingoverlay.moc:74 #11 0x00007f9e5c6c678f in QMetaObject::activate (sender=0xd32470, m=<value optimized out>, local_signal_index=<value optimized out>, argv=0xfffffffffff6938a) at kernel/qobject.cpp:3293 #12 0x00007f9e5d773a75 in QAbstractItemView::entered(QModelIndex const&) () from /usr/lib64/libQtGui.so.4 #13 0x00007f9e5d777f28 in ?? () from /usr/lib64/libQtGui.so.4 #14 0x00007f9e5d77f158 in QAbstractItemView::mouseMoveEvent(QMouseEvent*) () from /usr/lib64/libQtGui.so.4 #15 0x00007f9e5d796ce1 in QListView::mouseMoveEvent(QMouseEvent*) () from /usr/lib64/libQtGui.so.4 #16 0x00007f9e5f4ac73c in KCategorizedView::mouseMoveEvent (this=0x0, event=0xff) at /usr/src/debug/digikam-1.2.0/libs/widgets/common/kcategorizedview.cpp:1121 #17 0x00007f9e5f480098 in Digikam::DCategorizedView::mouseMoveEvent (this=0xd32470, event=0x7fffd3408970) at /usr/src/debug/digikam-1.2.0/libs/widgets/common/dcategorizedview.cpp:597 #18 0x00007f9e5d2afdcf in QWidget::event(QEvent*) () from /usr/lib64/libQtGui.so.4 #19 0x00007f9e5d6545b6 in QFrame::event(QEvent*) () from /usr/lib64/libQtGui.so.4 #20 0x00007f9e5d783a6b in QAbstractItemView::viewportEvent(QEvent*) () from /usr/lib64/libQtGui.so.4 #21 0x00007f9e5f482d0f in Digikam::DCategorizedView::viewportEvent (this=0xd32470, event=0x7fffd3408970) at /usr/src/debug/digikam-1.2.0/libs/widgets/common/dcategorizedview.cpp:704 #22 0x00007f9e5c6b2d97 in QCoreApplicationPrivate::sendThroughObjectEventFilters (this=<value optimized out>, receiver=0xdd6af0, event=0x7fffd3408970) at kernel/qcoreapplication.cpp:819 #23 0x00007f9e5d259dec in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib64/libQtGui.so.4 #24 0x00007f9e5d260bdb in QApplication::notify(QObject*, QEvent*) () from /usr/lib64/libQtGui.so.4 #25 0x00007f9e5deed456 in KApplication::notify(QObject*, QEvent*) () from /usr/lib64/libkdeui.so.5 #26 0x00007f9e5c6b398c in QCoreApplication::notifyInternal (this=0x7fffd3409690, receiver=0xdd6af0, event=0x7fffd3408970) at kernel/qcoreapplication.cpp:704 #27 0x00007f9e5d25fdb6 in QApplicationPrivate::sendMouseEvent(QWidget*, QMouseEvent*, QWidget*, QWidget*, QWidget**, QPointer<QWidget>&, bool) () from /usr/lib64/libQtGui.so.4 #28 0x00007f9e5d2df765 in ?? () from /usr/lib64/libQtGui.so.4 #29 0x00007f9e5d2de47a in QApplication::x11ProcessEvent(_XEvent*) () from /usr/lib64/libQtGui.so.4 #30 0x00007f9e5d308932 in ?? () from /usr/lib64/libQtGui.so.4 #31 0x00007f9e5576adee in g_main_context_dispatch () from /usr/lib64/libglib-2.0.so.0 #32 0x00007f9e5576e7b8 in ?? () from /usr/lib64/libglib-2.0.so.0 #33 0x00007f9e5576e8e0 in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #34 0x00007f9e5c6dceb3 in QEventDispatcherGlib::processEvents (this=0xab6500, flags=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:412 #35 0x00007f9e5d30851e in ?? () from /usr/lib64/libQtGui.so.4 #36 0x00007f9e5c6b22a2 in QEventLoop::processEvents (this=<value optimized out>, flags=) at kernel/qeventloop.cpp:149 #37 0x00007f9e5c6b267c in QEventLoop::exec (this=0x7fffd34095c0, flags=) at kernel/qeventloop.cpp:201 #38 0x00007f9e5c6b63cb in QCoreApplication::exec () at kernel/qcoreapplication.cpp:981 #39 0x000000000077d34b in main (argc=<value optimized out>, argv=<value optimized out>) at /usr/src/debug/digikam-1.2.0/digikam/main.cpp:193
Marcel, Johannes, Sound like a problem from model view port. Right? Gilles Caulier
Hm I don't think so. This looks like a crash directly in the rating widget in setFadingValue. Can anything strange happen there if value is 255?
Last night it just looked like the fading animation had not yet been instantiated when setFadingValue was called from that code path.
Changing the if (d->fadingValue >= 255) at digikam/ratingwidget.cpp:168 to if (d->fadingValue >= 255 && d->fadingTimeLine) should fix this crash.
*** Bug 232734 has been marked as a duplicate of this bug. ***
SVN commit 1109177 by jwienke: Fix crash in rating widget. Thanks for the hint. BUG: 232628 M +2 -2 NEWS M +1 -1 digikam/ratingwidget.cpp WebSVN link: http://websvn.kde.org/?view=rev&revision=1109177
What is the impact of this bug ? maybe a 1.2.1 would be nice to have ? because it may take time before the new database features in 1.3.0 branch are stable.
(In reply to comment #7) > What is the impact of this bug ? maybe a 1.2.1 would be nice to have ? because > it may take time before the new database features in 1.3.0 branch are stable. I vote for a 1.2.1! Right now I can't use digikam (without downgrading, that is) and it's one of the my favourite applications - and one of the best features of kde!
Just apply this patch: http://cvs.fedoraproject.org/viewvc/rpms/digikam/devel/digikam-1.2.0-kde232628.patch?revision=1.1&view=markup or nag your distributor to apply it if you're using binary packages.
*** Bug 234469 has been marked as a duplicate of this bug. ***
*** Bug 234516 has been marked as a duplicate of this bug. ***
*** Bug 234586 has been marked as a duplicate of this bug. ***
Created attachment 43277 [details] New crash information added by DrKonqi Crash. Just open, select an album and open preview or simply wait a few seconds.
Fenix, This file is fixed in current code from svn trunk (next digiKam 1.3.0) Gilles Caulier
*** Bug 236930 has been marked as a duplicate of this bug. ***
*** Bug 236989 has been marked as a duplicate of this bug. ***
*** Bug 236621 has been marked as a duplicate of this bug. ***
*** Bug 237161 has been marked as a duplicate of this bug. ***
*** Bug 237979 has been marked as a duplicate of this bug. ***
*** Bug 237981 has been marked as a duplicate of this bug. ***
*** Bug 238605 has been marked as a duplicate of this bug. ***
*** Bug 238962 has been marked as a duplicate of this bug. ***
*** Bug 240436 has been marked as a duplicate of this bug. ***
*** Bug 247413 has been marked as a duplicate of this bug. ***
*** Bug 246369 has been marked as a duplicate of this bug. ***
*** Bug 246534 has been marked as a duplicate of this bug. ***
*** Bug 246846 has been marked as a duplicate of this bug. ***
*** Bug 246899 has been marked as a duplicate of this bug. ***