Version: 0.9.3 (using 3.5.10, Kubuntu (hardy) 4:3.5.10-0ubuntu1~hardy1) Compiler: Target: i486-linux-gnu OS: Linux (i686) release 2.6.24-19-generic digikam: Installiert:2:0.9.3-2ubuntu1 This is a crash that just occured in my KDE 3-version of digikam. Digikam just crashed after editing a photo (photo hasn't been saved). - I applied the red eye plugin on it. - In the report stands something about the lighttable. I had this open. I will include the bug-report-results for informations with the hope to help! Thanks! - And good luck to you! :) [Thread debugging using libthread_db enabled] [New Thread 0xb598a6c0 (LWP 7471)] [New Thread 0xaa8fbb90 (LWP 9649)] [New Thread 0xae691b90 (LWP 9648)] [New Thread 0xb2b8db90 (LWP 8937)] [New Thread 0xb5647b90 (LWP 8912)] [New Thread 0xb4e46b90 (LWP 8911)] [KCrash handler] #6 KURL::addPath (this=0xbfd7e930, _txt=@0x8b2c0c4) at /build/buildd/kdelibs-3.5.10/./kdecore/kurl.cpp:1746 #7 0xb7c99fd3 in Digikam::ImageInfo::kurl (this=0x8b2c0b8) at /build/buildd/digikam-0.9.3/./digikam/digikam/imageinfo.cpp:174 #8 0xb7eeccc1 in Digikam::LightTableWindow::slotItemsUpdated ( this=0xaef12520, urls=@0xbfd7eb68) at /build/buildd/digikam-0.9.3/./digikam/utilities/lighttable/lighttablewindow.cpp:595 #9 0xb7ef0d73 in Digikam::LightTableWindow::qt_invoke (this=0xaef12520, _id=73, _o=0xbfd7eab4) at ./lighttablewindow.moc:228 #10 0xb6da2831 in QObject::activate_signal (this=0x8228760, clist=0x83bdd28, o=0xbfd7eab4) at kernel/qobject.cpp:2383 #11 0xb7c4dfa1 in Digikam::AlbumIconView::signalItemsUpdated (this=0x8228760, t0=@0xbfd7eb68) at ./albumiconview.moc:345 #12 0xb7cd0762 in Digikam::AlbumIconView::refreshItems (this=0x8228760, urlList=@0xbfd7eb68) at /build/buildd/digikam-0.9.3/./digikam/digikam/albumiconview.cpp:1812 #13 0xb7c53aa4 in Digikam::AlbumIconView::slotFilesModified (this=0x8228760, url=@0x8ac8624) at /build/buildd/digikam-0.9.3/./digikam/digikam/albumiconview.cpp:1080 #14 0xb7cd7ce3 in Digikam::AlbumIconView::qt_invoke (this=0x8228760, _id=93, _o=0xbfd7ec14) at ./albumiconview.moc:410 #15 0xb6da2704 in QObject::activate_signal (this=0x8abd9c0, clist=0x8c9bdc0, o=0xbfd7ec14) at kernel/qobject.cpp:2359 #16 0xb7e94401 in Digikam::ImageWindow::signalFileModified (this=0x8abd9c0, t0=@0x8ac8624) at ./imagewindow.moc:193 #17 0xb7e988f6 in Digikam::ImageWindow::saveIsComplete (this=0x8abd9c0) at /build/buildd/digikam-0.9.3/./digikam/utilities/imageeditor/editor/imagewindow.cpp:767 #18 0xb7ea65a3 in Digikam::EditorWindow::slotSavingFinished (this=0x8abd9c0, filename=@0x8cc5388, success=true) at /build/buildd/digikam-0.9.3/./digikam/utilities/imageeditor/editor/editorwindow.cpp:1380 #19 0xb7ea674c in Digikam::EditorWindow::qt_invoke (this=0x8abd9c0, _id=104, _o=0xbfd7edc0) at ./editorwindow.moc:264 #20 0xb7ea6a92 in Digikam::ImageWindow::qt_invoke (this=0x8abd9c0, _id=104, _o=0xbfd7edc0) at ./imagewindow.moc:232 #21 0xb6da2704 in QObject::activate_signal (this=0x87624b0, clist=0x8c99750, o=0xbfd7edc0) at kernel/qobject.cpp:2359 #22 0xb7e829ca in Digikam::Canvas::signalSavingFinished (this=0x87624b0, t0=@0x8b39750, t1=<value optimized out>) at ./canvas.moc:343 #23 0xb7e82a1c in Digikam::Canvas::slotImageSaved (this=0x87624b0, filePath=@0x8b39750, success=<value optimized out>) at /build/buildd/digikam-0.9.3/./digikam/utilities/imageeditor/canvas/canvas.cpp:297 #24 0xb7e90d21 in Digikam::Canvas::qt_invoke (this=0x87624b0, _id=83, _o=0xbfd7eed0) at ./canvas.moc:401 #25 0xb6da2704 in QObject::activate_signal (this=0x8aae318, clist=0x8414a18, o=0xbfd7eed0) at kernel/qobject.cpp:2359 #26 0xb7e820ea in Digikam::DImgInterface::signalImageSaved (this=0x8aae318, t0=@0x8d08b50, t1=<value optimized out>) at ./dimginterface.moc:221 #27 0xb7e8b2de in Digikam::DImgInterface::slotImageSaved (this=0x8aae318, filePath=@0x8d08b50, success=<value optimized out>) at /build/buildd/digikam-0.9.3/./digikam/utilities/imageeditor/canvas/dimginterface.cpp:634 #28 0xb7e9253e in Digikam::DImgInterface::qt_invoke (this=0x8aae318, _id=3, _o=0xbfd7f010) at ./dimginterface.moc:228 #29 0xb6da2704 in QObject::activate_signal (this=0x8479670, clist=0x820afd8, o=0xbfd7f010) at kernel/qobject.cpp:2359 #30 0xb7df721a in Digikam::LoadSaveThread::signalImageSaved (this=0x8479670, t0=@0x8abf3a0, t1=<value optimized out>) at ./loadsavethread.moc:208 #31 0xb7df726f in Digikam::SavedEvent::notify (this=0x8abf390, thread=0x8479670) at /build/buildd/digikam-0.9.3/./digikam/libs/threadimageio/loadsavethread.h:155 #32 0xb7df5911 in Digikam::LoadSaveThread::customEvent (this=0xb68f716c, event=0x8b2c0c4) at /build/buildd/digikam-0.9.3/./digikam/libs/threadimageio/loadsavethread.cpp:150 #33 0xb6da05e7 in QObject::event (this=0x8479670, e=0x8abf390) at kernel/qobject.cpp:758 #34 0xb6d36c36 in QApplication::internalNotify (this=0xbfd7f6f8, receiver=0x8479670, e=0x8abf390) at kernel/qapplication.cpp:2638 #35 0xb6d38a5f in QApplication::notify (this=0xbfd7f6f8, receiver=0x8479670, e=0x8abf390) at kernel/qapplication.cpp:2361 #36 0xb743c9b2 in KApplication::notify (this=0xbfd7f6f8, receiver=0x8479670, event=0x8abf390) at /build/buildd/kdelibs-3.5.10/./kdecore/kapplication.cpp:550 #37 0xb6cc728d in QApplication::sendEvent (receiver=0x8479670, event=0x8abf390) at ../include/qapplication.h:523 #38 0xb6d37c6e in QApplication::sendPostedEvents (receiver=0x0, event_type=0) at kernel/qapplication.cpp:3302 #39 0xb6d37d76 in QApplication::sendPostedEvents () at kernel/qapplication.cpp:3213 #40 0xb6cdb8a3 in QEventLoop::processEvents (this=0x808b500, flags=4) at kernel/qeventloop_x11.cpp:147 #41 0xb6d51f90 in QEventLoop::enterLoop (this=0x808b500) at kernel/qeventloop.cpp:201 #42 0xb6d51c8e in QEventLoop::exec (this=0x808b500) at kernel/qeventloop.cpp:148 #43 0xb6d387df in QApplication::exec (this=0xbfd7f6f8) at kernel/qapplication.cpp:2761 #44 0x0804ae16 in main (argc=7, argv=0xbfd7f874) at /build/buildd/digikam-0.9.3/./digikam/digikam/main.cpp:332
I suspect this problem have been fixed with 0.9.4 release. Please update digiKam and try again. Gilles Caulier
Any news here? Kubuntu 8.10 provides digiKam 0.9.4, so you should be able to re-check this problem with the new version. Andi
Sputnik, Please give us a fresh feedback here, using 0.9.4 release, else we will close this file... Thanks in advance Gilles
Gilles, what about this one? No answers in 3 months. We should close it, right? Andi
We close this file now. no more feedback. Gilles Caulier
Hi! Sorry for late and unsuffisant feedback. I have been too busy with different things in the meatime, sorry. However: It is not possible for me any loger to ceck this as my computer crashed and I had to install a system on a new pc. I now use KDE4 with your nice new version. Thanks for caring! - I will continue to report problems - and I am really thankfull for your software!