Summary: | Toggle "Tags already assigned" makes digikam crash | ||
---|---|---|---|
Product: | [Applications] digikam | Reporter: | Sebastian Schubert <schubert.seb> |
Component: | Tags-Engine | Assignee: | Digikam Developers <digikam-bugs-null> |
Status: | RESOLVED FIXED | ||
Severity: | crash | CC: | caulier.gilles, nico.kruber |
Priority: | NOR | ||
Version: | 1.9.0 | ||
Target Milestone: | --- | ||
Platform: | Compiled Sources | ||
OS: | Linux | ||
Latest Commit: | Version Fixed In: | 5.1.0 | |
Sentry Crash Report: | |||
Attachments: |
New crash information added by DrKonqi
image1 to reproduce the bug image2 to reproduce the bug crashlog with the two supplied images |
Description
Sebastian Schubert
2010-12-18 20:22:25 UTC
Hmm I can not confirm this, are you using any special images? Does it crash with every media type in your collection? Well, I just tried several other pictures, and you are right, I does not crash always. I even cannot determine the unique property of the pictures causing the crash. Nonetheless, the ones which make dk to crash, do it always. Do you want me to send you the pics per pm? If you create a test image with exactly the same tags as a picture causing the crash, does it crash then as well? Created attachment 57400 [details]
New crash information added by DrKonqi
digikam (1.8.0) on KDE Platform 4.6.00 (4.6.0) using Qt 4.7.1
bug is still present in 1.8.0...
(backtrace attached)
-- Backtrace (Reduced):
#6 QModelIndex (this=0x377df10, source_parent=<value optimized out>) at ../../src/corelib/kernel/qabstractitemmodel.h:65
#7 QSortFilterProxyModelPrivate::filter_changed (this=0x377df10, source_parent=<value optimized out>) at itemviews/qsortfilterproxymodel.cpp:1040
#8 0x00007f0ac9bf019d in QSortFilterProxyModelPrivate::filter_changed (this=0x377df10, source_parent=<value optimized out>) at itemviews/qsortfilterproxymodel.cpp:1045
#9 0x00007f0ac9bf019d in QSortFilterProxyModelPrivate::filter_changed (this=0x377df10, source_parent=<value optimized out>) at itemviews/qsortfilterproxymodel.cpp:1045
#10 0x00007f0ac9bf0271 in QSortFilterProxyModel::invalidateFilter (this=<value optimized out>) at itemviews/qsortfilterproxymodel.cpp:2357
Reproducable with a 2.0 version? I played around a bit with this button recently, fixing a bug, but never got a crash. Same for me. 2.0.0 do not crash with this function... Gilles Caulier I cannot reproduce it anymore with Version 1.9.0 Using KDE Development Platform 4.6.2 (4.6.2) so I'd tend to mark this resolved (maybe Nico should check). Nico, Can you check if problem is solved using 1.9.0 as Sebastian said in #7 Thanks in advance Gilles Caulier Created attachment 59674 [details]
image1 to reproduce the bug
the problem still persists - but tis time I got to experiment with it a bit more - I imported all my metadata onto the KDE logo - please use the attached image and the next one to reproduce the bug
it is important, that "foobar" (tagged in the 2nd image) is in the 2nd level, i.e. inside "Leute/Freunde" to trigger this bug - if it is just in "Leute", the bug does not appear.
Created attachment 59675 [details]
image2 to reproduce the bug
Created attachment 59677 [details]
crashlog with the two supplied images
PS: the bug is always reproducible for me with these two images
Thread 1 (Thread 0x7fb408d027c0 (LWP 14117)): [KCrash Handler] #6 QModelIndex (this=0x1958120, source_parent=<value optimized out>) at ../../src/corelib/kernel/qabstractitemmodel.h:65 #7 QSortFilterProxyModelPrivate::filter_changed (this=0x1958120, source_parent=<value optimized out>) at itemviews/qsortfilterproxymodel.cpp:1040 #8 0x00007fb40388ad3d in QSortFilterProxyModelPrivate::filter_changed (this=0x1958120, source_parent=<value optimized out>) at itemviews/qsortfilterproxymodel.cpp:1045 #9 0x00007fb40388ad3d in QSortFilterProxyModelPrivate::filter_changed (this=0x1958120, source_parent=<value optimized out>) at itemviews/qsortfilterproxymodel.cpp:1045 #10 0x00007fb40388ae11 in QSortFilterProxyModel::invalidateFilter (this=<value optimized out>) at itemviews/qsortfilterproxymodel.cpp:2357 #11 0x0000000000537c5d in Digikam::CheckableAlbumFilterModel::setFilterPartiallyChecked (this=0x19580e0, filter=<value optimized out>) at /usr/src/debug/digikam-1.9.0/libs/models/albumfiltermodel.cpp:308 #12 0x00000000004976fc in Digikam::ImageDescEditTab::slotAssignedTagsToggled (this=0x18d6b70, t=false) at /usr/src/debug/digikam-1.9.0/libs/imageproperties/imagedescedittab.cpp:1136 #13 0x000000000049bb0a in Digikam::ImageDescEditTab::qt_metacall (this=0x18d6b70, _c=QMetaObject::InvokeMetaMethod, _id=<value optimized out>, _a=0x7fff9384b400) at /usr/src/debug/digikam-1.9.0/build/digikam/imagedescedittab.moc:148 #14 0x00007fb4041bca5f in QMetaObject::activate (sender=0x1aceaf0, m=<value optimized out>, local_signal_index=<value optimized out>, argv=0x7fff9384b400) at kernel/qobject.cpp:3278 #15 0x00007fb4039655e2 in QAbstractButton::toggled (this=<value optimized out>, _t1=false) at .moc/release-shared/moc_qabstractbutton.cpp:213 #16 0x00007fb4036ad803 in QAbstractButton::setChecked (this=0x1aceaf0, checked=false) at widgets/qabstractbutton.cpp:766 #17 0x00007fb4036ad49a in QAbstractButtonPrivate::click (this=0x1aceb20) at widgets/qabstractbutton.cpp:528 #18 0x00007fb4036ad74c in QAbstractButton::mouseReleaseEvent (this=0x1aceaf0, e=0x7fff9384bda0) at widgets/qabstractbutton.cpp:1121 #19 0x00007fb403769c3a in QToolButton::mouseReleaseEvent (this=<value optimized out>, e=<value optimized out>) at widgets/qtoolbutton.cpp:721 #20 0x00007fb403349c5c in QWidget::event (this=0x1aceaf0, event=0x7fff9384bda0) at kernel/qwidget.cpp:8259 #21 0x00007fb4032f8144 in QApplicationPrivate::notify_helper (this=0xad15b0, receiver=0x1aceaf0, e=0x7fff9384bda0) at kernel/qapplication.cpp:4462 #22 0x00007fb403300f7c in QApplication::notify (this=<value optimized out>, receiver=0x1aceaf0, e=0x7fff9384bda0) at kernel/qapplication.cpp:4023 #23 0x00007fb404b0ad46 in KApplication::notify (this=0x7fff9384cbf0, receiver=0x1aceaf0, event=0x7fff9384bda0) at /usr/src/debug/kdelibs-4.6.2/kdeui/kernel/kapplication.cpp:311 #24 0x00007fb4041a847c in QCoreApplication::notifyInternal (this=0x7fff9384cbf0, receiver=0x1aceaf0, event=0x7fff9384bda0) at kernel/qcoreapplication.cpp:731 #25 0x00007fb4032f9155 in sendEvent (receiver=0x1aceaf0, event=0x7fff9384bda0, alienWidget=0x1aceaf0, nativeWidget=0x18d6b70, buttonDown=0x7fb403dca198, lastMouseReceiver=..., spontaneous=true) at ../../src/corelib/kernel/qcoreapplication.h:215 #26 QApplicationPrivate::sendMouseEvent (receiver=0x1aceaf0, event=0x7fff9384bda0, alienWidget=0x1aceaf0, nativeWidget=0x18d6b70, buttonDown=0x7fb403dca198, lastMouseReceiver=..., spontaneous=true) at kernel/qapplication.cpp:3122 #27 0x00007fb403377b48 in QETWidget::translateMouseEvent (this=0x18d6b70, event=<value optimized out>) at kernel/qapplication_x11.cpp:4461 #28 0x00007fb403376209 in QApplication::x11ProcessEvent (this=0x7fff9384cbf0, event=0x7fff9384c700) at kernel/qapplication_x11.cpp:3587 #29 0x00007fb40339df12 in x11EventSourceDispatch (s=0xad5270, callback=0, user_data=0x0) at kernel/qguieventdispatcher_glib.cpp:146 #30 0x00007fb3fa9ebbd3 in g_main_context_dispatch () from /lib64/libglib-2.0.so.0 #31 0x00007fb3fa9ec3b0 in ?? () from /lib64/libglib-2.0.so.0 #32 0x00007fb3fa9ec650 in g_main_context_iteration () from /lib64/libglib-2.0.so.0 #33 0x00007fb4041d322f in QEventDispatcherGlib::processEvents (this=0xa66150, flags=<value optimized out>) at kernel/qeventdispatcher_glib.cpp:422 #34 0x00007fb40339dbae in QGuiEventDispatcherGlib::processEvents (this=<value optimized out>, flags=<value optimized out>) at kernel/qguieventdispatcher_glib.cpp:204 #35 0x00007fb4041a78d2 in QEventLoop::processEvents (this=<value optimized out>, flags=...) at kernel/qeventloop.cpp:149 #36 0x00007fb4041a7ae5 in QEventLoop::exec (this=0x7fff9384ca20, flags=...) at kernel/qeventloop.cpp:201 #37 0x00007fb4041abf2b in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1008 #38 0x000000000062bf65 in main (argc=11326208, argv=0x7fff9384d300) at /usr/src/debug/digikam-1.9.0/digikam/main.cpp:216 I see this crash in another place... I think... Gilles Caulier Gilles, I see you have reproduced this with 1.9.0. What about 2.0? I didn't manage to crash it here. Marcel, I cannot reproduce the crash with 2.0.0... Gilles We need feedback using a recent version. 2.0.0 RC is out, please test... Thanks in advance Gilles Caulier Any news with a recent 2.x version? digiKam 2.2.0 is out since few weeks. Crash still valid with this version ? Gilles Caulier digiKam 4.11.0 is out. Problem still reproducible ? Gilles Caulier digiKam 4.12.0 is out : https://www.digikam.org/node/741 We need a fresh feedback using this release please... Thanks in advance. With digiKam 5.0.0, this problem is not reproducible. I close this file now. Don't hesitate to re-open if necessary. Gilles Caulier |