| Summary: | sudden crash of digiKam during work | ||
|---|---|---|---|
| Product: | [Applications] digikam | Reporter: | Sebastian <bacchus> |
| Component: | Thumbs-Engine | Assignee: | Digikam Developers <digikam-bugs-null> |
| Status: | RESOLVED FIXED | ||
| Severity: | crash | ||
| Priority: | NOR | ||
| Version First Reported In: | 0.10.0 | ||
| Target Milestone: | --- | ||
| Platform: | Ubuntu | ||
| OS: | Unspecified | ||
| Latest Commit: | Version Fixed/Implemented In: | 1.0.0 | |
| Sentry Crash Report: | |||
| Attachments: | Kcrash report | ||
|
Description
Sebastian
2009-07-05 23:02:22 UTC
Created attachment 35071 [details]
Kcrash report
Which version you use exactly ? Go to Help/About for details Gilles Caulier Thread 1 (Thread 0xb45ec920 (LWP 4857)):
[KCrash Handler]
#6 0xb7190499 in Digikam::ThumbBarItem::repaint (this=0x0) at /build/buildd/digikam-0.10.0/libs/widgets/common/thumbbar.cpp:1179
#7 0x0827a757 in Digikam::ImagePreviewBar::rearrangeItems (this=0x8e09f30) at /build/buildd/digikam-0.10.0/digikam/imagepreviewbar.cpp:200
#8 0xb7190395 in Digikam::ThumbBarView::slotUpdate (this=0x8e09f30) at /build/buildd/digikam-0.10.0/libs/widgets/common/thumbbar.cpp:1031
#9 0xb7191363 in Digikam::ThumbBarView::qt_metacall (this=0x8e09f30, _c=QMetaObject::InvokeMetaMethod, _id=3, _a=0xbfa13ac8)
at /build/buildd/digikam-0.10.0/obj-i486-linux-gnu/digikam/thumbbar.moc:85
#10 0x0827d7bf in Digikam::ImagePreviewBar::qt_metacall (this=0x8e09f30, _c=QMetaObject::InvokeMetaMethod, _id=53, _a=0xbfa13ac8)
at /build/buildd/digikam-0.10.0/obj-i486-linux-gnu/digikam/imagepreviewbar.moc:66
#11 0xb573aca8 in QMetaObject::activate (sender=0x8f0a820, from_signal_index=4, to_signal_index=4, argv=0x0) at kernel/qobject.cpp:3069
#12 0xb573b932 in QMetaObject::activate (sender=0x8f0a820, m=0xb5817904, local_signal_index=0, argv=0x0) at kernel/qobject.cpp:3143
#13 0xb5776717 in QTimer::timeout (this=0x8f0a820) at .moc/release-shared/moc_qtimer.cpp:128
#14 0xb57406fe in QTimer::timerEvent (this=0x8f0a820, e=0xbfa13f4c) at kernel/qtimer.cpp:261
#15 0xb573515f in QObject::event (this=0x8f0a820, e=0xbfa13f4c) at kernel/qobject.cpp:1082
#16 0xb5bf5e9c in QApplicationPrivate::notify_helper (this=0x8b907a8, receiver=0x8f0a820, e=0xbfa13f4c) at kernel/qapplication.cpp:4084
#17 0xb5bfe19e in QApplication::notify (this=0xbfa14214, receiver=0x8f0a820, e=0xbfa13f4c) at kernel/qapplication.cpp:3631
#18 0xb681994d in KApplication::notify (this=0xbfa14214, receiver=0x8f0a820, event=0xbfa13f4c) at /build/buildd/kde4libs-4.2.2/kdeui/kernel/kapplication.cpp:307
#19 0xb5724a3b in QCoreApplication::notifyInternal (this=0xbfa14214, receiver=0x8f0a820, event=0xbfa13f4c) at kernel/qcoreapplication.cpp:602
#20 0xb5753d71 in QTimerInfoList::activateTimers (this=0x8b93934) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:213
#21 0xb57504e0 in timerSourceDispatch (source=0x8b93900) at kernel/qeventdispatcher_glib.cpp:164
#22 0xb49fab88 in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0
#23 0xb49fe0eb in ?? () from /usr/lib/libglib-2.0.so.0
#24 0xb49fe268 in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0
#25 0xb5750438 in QEventDispatcherGlib::processEvents (this=0x8b7c5c0, flags={i = -1079951160}) at kernel/qeventdispatcher_glib.cpp:323
#26 0xb5c97365 in QGuiEventDispatcherGlib::processEvents (this=0x8b7c5c0, flags={i = -1079951112}) at kernel/qguieventdispatcher_glib.cpp:202
#27 0xb572306a in QEventLoop::processEvents (this=0xbfa14170, flags={i = -1079951048}) at kernel/qeventloop.cpp:149
#28 0xb57234aa in QEventLoop::exec (this=0xbfa14170, flags={i = -1079950984}) at kernel/qeventloop.cpp:200
#29 0xb5725959 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:880
#30 0xb5bf5d17 in QApplication::exec () at kernel/qapplication.cpp:3553
#31 0x082b4e3b in main (argc=5, argv=0xbfa14474) at /build/buildd/digikam-0.10.0/digikam/main.cpp:190
You use 0.10.0. Crash appears in thumbbar. This problem have been already fixed with 1.0.0-beta1.
Gilles Caulier
Dear Gilles,
> You use 0.10.0. Crash appears in thumbbar. This problem have been already fixed
> with 1.0.0-beta1.
thanks a lot for your super-fast respond.
However, I do not change the Bug's status to 'resolved' as it is not resolved in 0.10.0, right? I'm still a beginner in bug reporting ;-)
0.10.0 is not maintened anymore. try 1.0.0-beta1 or beta2 which will be out tomorow. Gilles (In reply to comment #4) > However, I do not change the Bug's status to 'resolved' as it is not resolved > in 0.10.0, right? I'm still a beginner in bug reporting ;-) Well it is solved in digiKam, so setting it to "resolved" is ok :) Andi |