Application that crashed: plasma-desktop Version of the application: 0.3 KDE Version: 4.3.1 (KDE 4.3.1) "release 6" Qt Version: 4.5.3 Operating System: Linux 2.6.31.5-0.1-default i686 Distribution: "openSUSE 11.2 (i586)" What I was doing when the application crashed: In KDE 4.4, removing Plasma PyWeather widget the plasma desktop crashed -- Backtrace: Application: Spazio di lavoro di Plasma (kdeinit4), signal: Segmentation fault [Current thread is 1 (Thread 0xb55ea700 (LWP 3436))] Thread 2 (Thread 0xa702eb70 (LWP 3439)): #0 0xffffe430 in __kernel_vsyscall () #1 0xb7489d95 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib/libpthread.so.0 #2 0xb74e9750 in QWaitCondition::wait(QMutex*, unsigned long) () from /usr/lib/libQtCore.so.4 #3 0xb5c38a04 in ?? () from /usr/lib/libQtNetwork.so.4 #4 0xb74e8623 in ?? () from /usr/lib/libQtCore.so.4 #5 0xb74856e5 in start_thread () from /lib/libpthread.so.0 #6 0xb7485600 in ?? () from /lib/libpthread.so.0 Thread 1 (Thread 0xb55ea700 (LWP 3436)): [KCrash Handler] #6 0xb67987fd in QGraphicsItem::update(QRectF const&) () from /usr/lib/libQtGui.so.4 #7 0xa82723f9 in ?? () from /usr/lib/python2.6/site-packages/PyQt4/QtGui.so #8 0xa87bd651 in PyCFunction_Call () from /usr/lib/libpython2.6.so.1.0 #9 0xa880b27d in PyEval_EvalFrameEx () from /usr/lib/libpython2.6.so.1.0 #10 0xa8810be9 in PyEval_EvalCodeEx () from /usr/lib/libpython2.6.so.1.0 #11 0xa87ab617 in ?? () from /usr/lib/libpython2.6.so.1.0 #12 0xa8788c70 in PyObject_Call () from /usr/lib/libpython2.6.so.1.0 #13 0xa8795f61 in ?? () from /usr/lib/libpython2.6.so.1.0 #14 0xa8788c70 in PyObject_Call () from /usr/lib/libpython2.6.so.1.0 #15 0xa88093b6 in PyEval_CallObjectWithKeywords () from /usr/lib/libpython2.6.so.1.0 #16 0xa85a07af in ?? () from /usr/lib/python2.6/site-packages/sip.so #17 0xa86f0ae5 in ?? () from /usr/lib/python2.6/site-packages/PyQt4/QtCore.so #18 0xa86f0beb in ?? () from /usr/lib/python2.6/site-packages/PyQt4/QtCore.so #19 0xa86f0ccb in ?? () from /usr/lib/python2.6/site-packages/PyQt4/QtCore.so #20 0xb75f5864 in QMetaObject::activate(QObject*, int, int, void**) () from /usr/lib/libQtCore.so.4 #21 0xb75f6585 in QMetaObject::activate(QObject*, QMetaObject const*, int, void**) () from /usr/lib/libQtCore.so.4 #22 0xb7631715 in QTimer::timeout() () from /usr/lib/libQtCore.so.4 #23 0xb75fb196 in QTimer::timerEvent(QTimerEvent*) () from /usr/lib/libQtCore.so.4 #24 0xa8612e24 in ?? () from /usr/lib/python2.6/site-packages/PyQt4/QtCore.so #25 0xb75ef51b in QObject::event(QEvent*) () from /usr/lib/libQtCore.so.4 #26 0xa8612d74 in ?? () from /usr/lib/python2.6/site-packages/PyQt4/QtCore.so #27 0xb61838fc in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib/libQtGui.so.4 #28 0xb618b34e in QApplication::notify(QObject*, QEvent*) () from /usr/lib/libQtGui.so.4 #29 0xb6bc1ce1 in KApplication::notify(QObject*, QEvent*) () from /usr/lib/libkdeui.so.5 #30 0xb75df32e in QCoreApplication::notifyInternal(QObject*, QEvent*) () from /usr/lib/libQtCore.so.4 #31 0xb760e356 in ?? () from /usr/lib/libQtCore.so.4 #32 0xb760b325 in ?? () from /usr/lib/libQtCore.so.4 #33 0xb5d5e4c2 in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0 #34 0xb5d61d98 in ?? () from /usr/lib/libglib-2.0.so.0 #35 0xb5d61ebe in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0 #36 0xb760b011 in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQtCore.so.4 #37 0xb622529a in ?? () from /usr/lib/libQtGui.so.4 #38 0xb75dd98d in QEventLoop::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQtCore.so.4 #39 0xb75dddd9 in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQtCore.so.4 #40 0xb75e0270 in QCoreApplication::exec() () from /usr/lib/libQtCore.so.4 #41 0xb6183774 in QApplication::exec() () from /usr/lib/libQtGui.so.4 #42 0xb40d5b49 in kdemain () from /usr/lib/libkdeinit4_plasma-desktop.so #43 0x0804e147 in _start () This bug may be a duplicate of or related to bug 210473 Reported using DrKonqi
This is related to bug 197608 / bug 207221 Thanks *** This bug has been marked as a duplicate of bug 197608 ***