Application that crashed: kontact Version of the application: 4.4 pre KDE Version: 4.3.62 (KDE 4.3.62 (KDE 4.4 >= 20090728)) "release 2" Qt Version: 4.5.2 Operating System: Linux 2.6.27.4 i686 What I was doing when the application crashed: I open the site kde-look.org using a link inside the rss-news. Then I zoom into the preview. When I click on the loaded image (that calls "self.close()") kontact crashs. -- Backtrace: Application: Kontact (kontact), signal: Segmentation fault [Current thread is 0 (LWP 3537)] Thread 2 (Thread 0xb002eb90 (LWP 4551)): #0 0xffffe424 in __kernel_vsyscall () #1 0xb660ef42 in pthread_cond_timedwait@@GLIBC_2.3.2 () from /lib/libpthread.so.0 #2 0xb666c56c in QWaitCondition::wait (this=0x8c4ad00, mutex=0x8c4acfc, time=30000) at thread/qwaitcondition_unix.cpp:85 #3 0xb6661b7e in QThreadPoolThread::run (this=0x8c4b860) at concurrent/qthreadpool.cpp:140 #4 0xb666b582 in QThreadPrivate::start (arg=0x8c4b860) at thread/qthread_unix.cpp:188 #5 0xb660b175 in start_thread () from /lib/libpthread.so.0 #6 0xb598cdae in clone () from /lib/libc.so.6 Thread 1 (Thread 0xb48456d0 (LWP 3537)): [KCrash Handler] #6 0xb6770c2a in QObjectPrivate::cleanConnectionLists (this=0x972acd8) at kernel/qobject.cpp:306 #7 0xb6775a0d in QMetaObject::activate (sender=0x910fd70, from_signal_index=0, to_signal_index=1, argv=0xbfe1593c) at kernel/qobject.cpp:3148 #8 0xb6775b60 in QMetaObject::activate (sender=0x910fd70, m=0xb684f1a8, from_local_signal_index=0, to_local_signal_index=1, argv=0xbfe1593c) at kernel/qobject.cpp:3207 #9 0xb6775beb in QObject::destroyed (this=0x910fd70, _t1=0x910fd70) at .moc/release-shared/moc_qobject.cpp:143 #10 0xb6776a39 in ~QObject (this=0x910fd70) at kernel/qobject.cpp:757 #11 0xb716a2ee in KParts::Part::~Part () from /usr/lib/libkparts.so.4 #12 0xb716a61a in KParts::ReadOnlyPart::~ReadOnlyPart () from /usr/lib/libkparts.so.4 #13 0xb7aac697 in KHTMLPart::~KHTMLPart () from /usr/lib/libkhtml.so.5 #14 0xb676f015 in qDeleteInEventHandler (o=0x910fd70) at kernel/qobject.cpp:3815 #15 0xb6770933 in QObject::event (this=0x910fd70, e=0x8b55d68) at kernel/qobject.cpp:1094 #16 0xb5c476ac in QApplicationPrivate::notify_helper (this=0x80752c8, receiver=0x910fd70, e=0x8b55d68) at kernel/qapplication.cpp:4056 #17 0xb5c4f9ce in QApplication::notify (this=0xbfe16198, receiver=0x910fd70, e=0x8b55d68) at kernel/qapplication.cpp:3603 #18 0xb6d1c2fd in KApplication::notify () from /usr/lib/libkdeui.so.5 #19 0xb676005b in QCoreApplication::notifyInternal (this=0xbfe16198, receiver=0xbfe16198, event=0x8b55d68) at kernel/qcoreapplication.cpp:610 #20 0xb6760ca5 in QCoreApplicationPrivate::sendPostedEvents (receiver=0x0, event_type=0, data=0x8054878) at kernel/qcoreapplication.h:213 #21 0xb6760e9d in QCoreApplication::sendPostedEvents (receiver=0x0, event_type=0) at kernel/qcoreapplication.cpp:1140 #22 0xb678bcaf in postEventSourceDispatch (s=0x8076cc0) at kernel/qcoreapplication.h:218 #23 0xb4f942f9 in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0 #24 0xb4f9787b in ?? () from /usr/lib/libglib-2.0.so.0 #25 0xb4f979f8 in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0 #26 0xb678b8f8 in QEventDispatcherGlib::processEvents (this=0x8081980, flags={i = -1075748760}) at kernel/qeventdispatcher_glib.cpp:327 #27 0xb5ce7d45 in QGuiEventDispatcherGlib::processEvents (this=0x8081980, flags={i = -1075748712}) at kernel/qguieventdispatcher_glib.cpp:202 #28 0xb675e69a in QEventLoop::processEvents (this=0xbfe16110, flags={i = -1075748648}) at kernel/qeventloop.cpp:149 #29 0xb675eae2 in QEventLoop::exec (this=0xbfe16110, flags={i = -1075748584}) at kernel/qeventloop.cpp:201 #30 0xb6760f69 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:888 #31 0xb5c47527 in QApplication::exec () at kernel/qapplication.cpp:3525 #32 0x0804c04f in main () Reported using DrKonqi
possible dublicate: 202291
This seems to be a new case of bug 193146. @Frank: is this the same (and your patch isn't fully fixing the issue); or it is another bug ? Thanks
The fix is not in trunk. I stopped forwardporting fixes from 4.3 to trunk as the 4.4 akregator is in the akonadi-ports branch and its codebase is majorly changed since 4.3 already. It is easier to review the changes in 4.3 once we merge akonadi-ports back to trunk, instead of fighting conflicts in then-to-be dead/rewritten code. We could make exceptions for crashes like this (which is in code that won't change during the Akonadi port), to ease the pain for trunk users. OTOH, it's harder then to track which changes are already merged and which are not. *** This bug has been marked as a duplicate of bug 202291 ***