Version: 0.9.3-2ubuntu1 (using KDE 3.5.10) OS: Linux Installed from: Ubuntu Packages Unfortunately digikam crashes every single time on ending a slideshow. Now matter what options I use. Even without GL effects. digikam 0.9.3-2ubuntu1, kipi-plugins 0.1.5-1. I'm running it in the KDE 4.1.2 environment, but I guess it shouldn't matter. And I use a dual head setup. I will attach some crash back traces.
Created attachment 27744 [details] Kcrash 1
Created attachment 27745 [details] Kcrash 2
Created attachment 27746 [details] Kcrash 3
Okay, sorry. The crash reports are the same. Btw. I use prelink. Don't know if that matters.
I've found a way it doesn't crash: If I only use the Ken Burns effect. Everything else does crash.
Dennis, This file still valid using kipi-plugins 0.1.6 ? Gilles Caulier
Pasted backtrace: [Thread debugging using libthread_db enabled] [New Thread 0x7f14337dd6f0 (LWP 7330)] [KCrash handler] #5 0x0000003e46fd16fc in QThread::wait (this=) at kernel/qthread_unix.cpp:440 #6 0x00007f1431093860 in KIPISlideShowPlugin::SlideShowLoader::~SlideShowLoader () from /usr/lib/kde3/kipiplugin_slideshow.so #7 0x00007f1431086576 in KIPISlideShowPlugin::SlideShow::~SlideShow () from /usr/lib/kde3/kipiplugin_slideshow.so #8 0x0000003e4703f085 in QObject::event (this=) at kernel/qobject.cpp:753 #9 0x0000003e470752bb in QWidget::event (this=) at kernel/qwidget.cpp:4681 #10 0x0000003e46fd933a in QApplication::internalNotify (this=) at kernel/qapplication.cpp:2638 #11 0x0000003e46fdbbe3 in QApplication::notify (this=) at kernel/qapplication.cpp:2526 #12 0x0000003e47bd96bd in KApplication::notify (this=<value optimized out>, receiver=<value optimized out>, event=<value optimized out>) at /build/buildd/kdelibs-3.5.10/./kdecore/kapplication.cpp:550 #13 0x0000003e46f6a20e in QApplication::sendEvent (receiver=) at ../include/qapplication.h:523 #14 0x0000003e46fda351 in QApplication::sendPostedEvents (receiver=) at kernel/qapplication.cpp:3302 #15 0x0000003e46fda449 in QApplication::sendPostedEvents () at kernel/qapplication.cpp:3213 #16 0x0000003e46f7e179 in QEventLoop::processEvents (this=) at kernel/qeventloop_x11.cpp:205 #17 0x0000003e46ff35bf in QEventLoop::enterLoop (this=) at kernel/qeventloop.cpp:201 #18 0x0000003e46ff32ab in QEventLoop::exec (this=) at kernel/qeventloop.cpp:148 #19 0x0000003e46fdae00 in QApplication::exec (this=) at kernel/qapplication.cpp:2761 #20 0x000000000040326f in main (argc=1, argv=0x7fff3b829b48) at /build/buildd/digikam-0.9.3/./digikam/digikam/main.cpp:332
Valerio, Sound like another invalid delete in plugin destructor ? Gilles Caulier
(In reply to comment #8) > Valerio, > > Sound like another invalid delete in plugin destructor ? > > Gilles Caulier > I don't think so... because that code (KDE3 branch) is the same from about 1 year or so, and I've introduced that kind of bugs you mean, only in the lasts 3 months (during SlideShow's kde4 restyle). This bug is, most probably, related to image caching system (used by SlideShow and SlideShowGL), which cause some issue with prelink. That's a guess... because I cannot reproduce this bug. :'( Valerio
is this still valid with the KDE4 version ?
I will be more precise (:=))) : it still valid with last kipi-plugins 0.4.0 ? Gilles Caulier
I patched a lot of stuff here. Dennis, could you please test with latest KIPI from SVN or kipi-plugins-0.5.0, which will be released this weekend?
Today I fixed a crash that should be related to this one. The problem was that a loadThread might have been ended just when we want to call QThread::wait(). Accessing a null pointer will crash the application. I added a check now and will close this bugreport.