Bug 150792 - sigsegv when applying tags
Summary: sigsegv when applying tags
Status: RESOLVED WORKSFORME
Alias: None
Product: digikam
Classification: Applications
Component: Tags-Engine (show other bugs)
Version: unspecified
Platform: Debian testing Linux
: NOR crash
Target Milestone: ---
Assignee: Digikam Developers
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-10-13 17:31 UTC by CSights
Modified: 2022-01-22 14:02 UTC (History)
0 users

See Also:
Latest Commit:
Version Fixed In: 7.6.0


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description CSights 2007-10-13 17:31:56 UTC
Version:           0.9.2 (using KDE KDE 3.5.7)
Installed from:    Debian testing/unstable Packages
OS:                Linux

Hi,
   At the end of applying tags to images in an album, digikam "crashed".
   This is for version 0.9.2-final.  Let me know if there is anything else I can provide!

Here is the backtrace.

(no debugging symbols found)
Using host libthread_db library "/lib/i686/cmov/libthread_db.so.1".
(no debugging symbols found)
(no debugging symbols found)
[Thread debugging using libthread_db enabled]
[New Thread 0xb5a446c0 (LWP 15209)]
[KCrash handler]
#6  0xb7cb720d in Digikam::IconItem::prevItem () from /usr/lib/libdigikam.so.0
#7  0xb7d01e91 in Digikam::DigikamView::slotDispatchImageSelected ()
   from /usr/lib/libdigikam.so.0
#8  0xb7d40720 in Digikam::DigikamView::qt_invoke ()
   from /usr/lib/libdigikam.so.0
#9  0xb639ab10 in QObject::activate_signal (this=0x82fd520, clist=0x82fe7a8, 
    o=0xbfb860dc) at kernel/qobject.cpp:2356
#10 0xb639b5f5 in QObject::activate_signal (this=0x82fd520, signal=2)
    at kernel/qobject.cpp:2325
#11 0xb672cb94 in QTimer::timeout (this=0x82fd520)
    at .moc/debug-shared-mt/moc_qtimer.cpp:82
#12 0xb63c2282 in QTimer::event (this=0x82fd520, e=0xbfb863f8)
    at kernel/qtimer.cpp:219
#13 0xb632f36a in QApplication::internalNotify (this=0xbfb86ffc, 
    receiver=0x82fd520, e=0xbfb863f8) at kernel/qapplication.cpp:2635
#14 0xb6331193 in QApplication::notify (this=0xbfb86ffc, receiver=0x82fd520, 
    e=0xbfb863f8) at kernel/qapplication.cpp:2358
#15 0xb6afbff2 in KApplication::notify (this=0xbfb86ffc, receiver=0x82fd520, 
    event=0xbfb863f8)
    at /build/buildd/kdelibs-3.5.7.dfsg.1/./kdecore/kapplication.cpp:550
#16 0xb62c06c9 in QApplication::sendEvent (receiver=0x82fd520, 
    event=0xbfb863f8) at ../include/qapplication.h:520
#17 0xb63221b1 in QEventLoop::activateTimers (this=0x8080dd8)
    at kernel/qeventloop_unix.cpp:556
#18 0xb62d519a in QEventLoop::processEvents (this=0x8080dd8, flags=0)
    at kernel/qeventloop_x11.cpp:389
#19 0xb634a656 in QEventLoop::processEvents (this=0x8080dd8, flags=0, 
    maxTime=3000) at kernel/qeventloop.cpp:258
#20 0xb6330f7e in QApplication::processEvents (this=0xbfb86ffc, maxtime=3000)
    at kernel/qapplication.cpp:2693
#21 0xb6330fa9 in QApplication::processEvents (this=0xbfb86ffc)
    at kernel/qapplication.cpp:2677
#22 0xb7e5e6df in Digikam::ImageDescEditTab::slotApplyAllChanges ()
   from /usr/lib/libdigikam.so.0
#23 0xb7e5eb21 in Digikam::ImageDescEditTab::slotChangingItems ()
   from /usr/lib/libdigikam.so.0
#24 0xb7e5ee1b in Digikam::ImageDescEditTab::setItem ()
   from /usr/lib/libdigikam.so.0
#25 0xb7e5f3a8 in Digikam::ImagePropertiesSideBarDB::slotNoCurrentItem ()
   from /usr/lib/libdigikam.so.0
#26 0xb7e5da84 in Digikam::ImagePropertiesSideBarDB::qt_invoke ()
   from /usr/lib/libdigikam.so.0
#27 0xb639ab10 in QObject::activate_signal (this=0x812a5e8, clist=0x82fe0e8, 
    o=0xbfb868cc) at kernel/qobject.cpp:2356
#28 0xb639b5f5 in QObject::activate_signal (this=0x812a5e8, signal=5)
    at kernel/qobject.cpp:2325
#29 0xb7cdb121 in Digikam::DigikamView::signalNoCurrentItem ()
   from /usr/lib/libdigikam.so.0
#30 0xb7d01e0d in Digikam::DigikamView::slotDispatchImageSelected ()
   from /usr/lib/libdigikam.so.0
#31 0xb7d40720 in Digikam::DigikamView::qt_invoke ()
   from /usr/lib/libdigikam.so.0
#32 0xb639ab10 in QObject::activate_signal (this=0x82fd520, clist=0x82fe7a8, 
    o=0xbfb86a4c) at kernel/qobject.cpp:2356
#33 0xb639b5f5 in QObject::activate_signal (this=0x82fd520, signal=2)
    at kernel/qobject.cpp:2325
#34 0xb672cb94 in QTimer::timeout (this=0x82fd520)
    at .moc/debug-shared-mt/moc_qtimer.cpp:82
#35 0xb63c2282 in QTimer::event (this=0x82fd520, e=0xbfb86d68)
    at kernel/qtimer.cpp:219
#36 0xb632f36a in QApplication::internalNotify (this=0xbfb86ffc, 
    receiver=0x82fd520, e=0xbfb86d68) at kernel/qapplication.cpp:2635
#37 0xb6331193 in QApplication::notify (this=0xbfb86ffc, receiver=0x82fd520, 
    e=0xbfb86d68) at kernel/qapplication.cpp:2358
#38 0xb6afbff2 in KApplication::notify (this=0xbfb86ffc, receiver=0x82fd520, 
    event=0xbfb86d68)
    at /build/buildd/kdelibs-3.5.7.dfsg.1/./kdecore/kapplication.cpp:550
#39 0xb62c06c9 in QApplication::sendEvent (receiver=0x82fd520, 
    event=0xbfb86d68) at ../include/qapplication.h:520
#40 0xb63221b1 in QEventLoop::activateTimers (this=0x8080dd8)
    at kernel/qeventloop_unix.cpp:556
#41 0xb62d519a in QEventLoop::processEvents (this=0x8080dd8, flags=4)
    at kernel/qeventloop_x11.cpp:389
#42 0xb634a6e4 in QEventLoop::enterLoop (this=0x8080dd8)
    at kernel/qeventloop.cpp:198
#43 0xb634a3e2 in QEventLoop::exec (this=0x8080dd8)
    at kernel/qeventloop.cpp:145
#44 0xb6330f13 in QApplication::exec (this=0xbfb86ffc)
    at kernel/qapplication.cpp:2758
#45 0x0804b148 in main ()
Comment 1 caulier.gilles 2007-11-28 16:31:35 UTC
CSights,

What news about this crash. it still reproductible ? Can you chack with new digiKam 0.9.3-beta3 ?

Gilles Caulier
Comment 2 CSights 2007-11-28 19:20:39 UTC
I have only had this problem once, but I thought the backtrace might help you.
Sorry. :)

Please close and I will reopen for 0.9.3 if needed.  Thanks!
Comment 3 Arnd Baecker 2007-11-28 20:17:33 UTC
Thanks a lot for the feedback.
Such bugs which only occur very rarely, are hard to track down.
In principle one would have to use a debug build of digikam
all the time...
(see http://www.digikam.org/?q=contrib under "If you are experiencing crashes with digiKam")
So don't hesitate to re-open this bug if the crash occurs again!

Best, Arnd