Version: (using KDE 4.0.0) Installed from: SuSE RPMs Compiler: gcc OS: Linux When i close rapidly my plasma element on desktop the plasma go in crash log of error : SIGNAL 11 (SIGSEGV) Backtrace : [?1034h(no debugging symbols found) Using host libthread_db library "/lib64/libthread_db.so.1". (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) (no debugging symbols found) [Thread debugging using libthread_db enabled] [New Thread 0x2b813f975ac0 (LWP 3798)] [New Thread 0x43009950 (LWP 5212)] [New Thread 0x42808950 (LWP 5211)] [New Thread 0x42007950 (LWP 5210)] [New Thread 0x41806950 (LWP 5209)] [New Thread 0x41005950 (LWP 5207)] [New Thread 0x40804950 (LWP 3816)] [KCrash handler] #5 0x00002b813afdc9ba in QGraphicsScenePrivate::filterEvent () from /usr/lib64/libQtGui.so.4 #6 0x00002b813afdca39 in QGraphicsScenePrivate::sendEvent () from /usr/lib64/libQtGui.so.4 #7 0x00002b813afdd401 in QGraphicsScenePrivate::sendHoverEvent () from /usr/lib64/libQtGui.so.4 #8 0x00002b813afe47f1 in QGraphicsScenePrivate::dispatchHoverEvent () from /usr/lib64/libQtGui.so.4 #9 0x00002b813afe4b70 in QGraphicsScene::event () from /usr/lib64/libQtGui.so.4 #10 0x00002b813ab8eb1b in QApplicationPrivate::notify_helper () from /usr/lib64/libQtGui.so.4 #11 0x00002b813ab90115 in QApplication::notify () from /usr/lib64/libQtGui.so.4 #12 0x00002b81370c497b in KApplication::notify () from /usr/lib64/libkdeui.so.5 #13 0x00002b813a0276c0 in QCoreApplication::notifyInternal () from /usr/lib64/libQtCore.so.4 #14 0x00002b813aff37a8 in QGraphicsView::mouseMoveEvent () from /usr/lib64/libQtGui.so.4 #15 0x00002b813abce617 in QWidget::event () from /usr/lib64/libQtGui.so.4 #16 0x00002b813ae5a3b6 in QFrame::event () from /usr/lib64/libQtGui.so.4 #17 0x00002b813aecc759 in QAbstractScrollArea::viewportEvent () from /usr/lib64/libQtGui.so.4 #18 0x00002b813afeedb1 in QGraphicsView::viewportEvent () from /usr/lib64/libQtGui.so.4 #19 0x00002b813aecdf68 in ?? () from /usr/lib64/libQtGui.so.4 #20 0x00002b813ab8eacf in QApplicationPrivate::notify_helper () from /usr/lib64/libQtGui.so.4 #21 0x00002b813ab9032d in QApplication::notify () from /usr/lib64/libQtGui.so.4 #22 0x00002b81370c497b in KApplication::notify () from /usr/lib64/libkdeui.so.5 #23 0x00002b813a0276c0 in QCoreApplication::notifyInternal () from /usr/lib64/libQtCore.so.4 #24 0x00002b813abdedb3 in QETWidget::translateMouseEvent () from /usr/lib64/libQtGui.so.4 #25 0x00002b813abdde31 in QApplication::x11ProcessEvent () from /usr/lib64/libQtGui.so.4 #26 0x00002b813abff623 in ?? () from /usr/lib64/libQtGui.so.4 #27 0x00002b813da43204 in g_main_context_dispatch () from /usr/lib64/libglib-2.0.so.0 #28 0x00002b813da464fd in ?? () from /usr/lib64/libglib-2.0.so.0 #29 0x00002b813da469ce in g_main_context_iteration () from /usr/lib64/libglib-2.0.so.0 #30 0x00002b813a046b81 in QEventDispatcherGlib::processEvents () from /usr/lib64/libQtCore.so.4 #31 0x00002b813abff23f in QGuiEventDispatcherGlib::processEvents () from /usr/lib64/libQtGui.so.4 #32 0x00002b813a026e60 in QEventLoop::processEvents () from /usr/lib64/libQtCore.so.4 #33 0x00002b813a026f7d in QEventLoop::exec () from /usr/lib64/libQtCore.so.4 #34 0x00002b813a028e77 in QCoreApplication::exec () from /usr/lib64/libQtCore.so.4 #35 0x00002b8135edb8e1 in kdemain () from /usr/lib64/libkdeinit4_plasma.so #36 0x00002b813c369b54 in __libc_start_main () from /lib64/libc.so.6 #37 0x00000000004008a9 in _start () #0 0x00002b813c3e26a1 in nanosleep () from /lib64/libc.so.6
Thank you for your bug report. This bug can not be reproduced using the current development (SVN) version of KDE. This suggests that the bug has already been fixed. The bug report will be closed. Let us know if it happens again, check especially with 4.0.1. =)