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-desktop x86_64 Distribution: "openSUSE 11.2 (x86_64)" What I was doing when the application crashed: i have installed a new plasmoid via yast and after i change the plasmoids settings plasma crashd -- Backtrace: Application: Plasma-Arbeitsfläche (kdeinit4), signal: Segmentation fault [Current thread is 1 (Thread 0x7f9bcd0c4750 (LWP 11941))] Thread 2 (Thread 0x7f9badec0910 (LWP 11944)): #0 0x00007f9bcc88f049 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib64/libpthread.so.0 #1 0x00007f9bccaff53b in QWaitCondition::wait(QMutex*, unsigned long) () from /usr/lib64/libQtCore.so.4 #2 0x00007f9bc8fd89ec in ?? () from /usr/lib64/libQtNetwork.so.4 #3 0x00007f9bccafe485 in ?? () from /usr/lib64/libQtCore.so.4 #4 0x00007f9bcc88a65d in start_thread () from /lib64/libpthread.so.0 #5 0x00007f9bca29e14d in clone () from /lib64/libc.so.6 #6 0x0000000000000000 in ?? () Thread 1 (Thread 0x7f9bcd0c4750 (LWP 11941)): [KCrash Handler] #5 0x00007f9bcaf4498a in QGraphicsItem::update(QRectF const&) () from /usr/lib64/libQtGui.so.4 #6 0x00007f9ba2094bce in ?? () from /usr/lib64/python2.6/site-packages/PyQt4/QtGui.so #7 0x00007f9ba2e6cbf9 in PyEval_EvalFrameEx () from /usr/lib64/libpython2.6.so.1.0 #8 0x00007f9ba2e7154e in PyEval_EvalCodeEx () from /usr/lib64/libpython2.6.so.1.0 #9 0x00007f9ba2e0f7f2 in ?? () from /usr/lib64/libpython2.6.so.1.0 #10 0x00007f9ba2defe32 in PyObject_Call () from /usr/lib64/libpython2.6.so.1.0 #11 0x00007f9ba2dfc010 in ?? () from /usr/lib64/libpython2.6.so.1.0 #12 0x00007f9ba2defe32 in PyObject_Call () from /usr/lib64/libpython2.6.so.1.0 #13 0x00007f9ba2e6aea6 in PyEval_CallObjectWithKeywords () from /usr/lib64/libpython2.6.so.1.0 #14 0x00007f9ba25c0560 in ?? () from /usr/lib64/python2.6/site-packages/sip.so #15 0x00007f9ba2924596 in ?? () from /usr/lib64/python2.6/site-packages/PyQt4/QtCore.so #16 0x00007f9ba29246ac in ?? () from /usr/lib64/python2.6/site-packages/PyQt4/QtCore.so #17 0x00007f9ba292476a in ?? () from /usr/lib64/python2.6/site-packages/PyQt4/QtCore.so #18 0x00007f9bccbf8fbc in QMetaObject::activate(QObject*, int, int, void**) () from /usr/lib64/libQtCore.so.4 #19 0x00007f9ba2861f53 in ?? () from /usr/lib64/python2.6/site-packages/PyQt4/QtCore.so #20 0x00007f9bccbf2f63 in QObject::event(QEvent*) () from /usr/lib64/libQtCore.so.4 #21 0x00007f9ba2861ee3 in ?? () from /usr/lib64/python2.6/site-packages/PyQt4/QtCore.so #22 0x00007f9bca9d42ac in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib64/libQtGui.so.4 #23 0x00007f9bca9db57e in QApplication::notify(QObject*, QEvent*) () from /usr/lib64/libQtGui.so.4 #24 0x00007f9bcb5ce8d6 in KApplication::notify(QObject*, QEvent*) () from /usr/lib64/libkdeui.so.5 #25 0x00007f9bccbe3ddc in QCoreApplication::notifyInternal(QObject*, QEvent*) () from /usr/lib64/libQtCore.so.4 #26 0x00007f9bccc0f71d in ?? () from /usr/lib64/libQtCore.so.4 #27 0x00007f9bccc0c678 in ?? () from /usr/lib64/libQtCore.so.4 #28 0x00007f9bc991ddde in g_main_context_dispatch () from /usr/lib64/libglib-2.0.so.0 #29 0x00007f9bc99217a8 in ?? () from /usr/lib64/libglib-2.0.so.0 #30 0x00007f9bc99218d0 in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #31 0x00007f9bccc0c3a3 in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/libQtCore.so.4 #32 0x00007f9bcaa6731e in ?? () from /usr/lib64/libQtGui.so.4 #33 0x00007f9bccbe2712 in QEventLoop::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/libQtCore.so.4 #34 0x00007f9bccbe2ae4 in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib64/libQtCore.so.4 #35 0x00007f9bccbe4c99 in QCoreApplication::exec() () from /usr/lib64/libQtCore.so.4 #36 0x00007f9bc1187d6f in kdemain () from /usr/lib64/libkdeinit4_plasma-desktop.so #37 0x0000000000406f88 in _start () Reported using DrKonqi
Crashes with similar reports are being tracked at bug 197608. Thanks *** This bug has been marked as a duplicate of bug 197608 ***