Version: (using Devel) Installed from: Compiled sources I loaded the kate session applet which could not be set up due to an invalid applet description. If I close this applet plasma crashs. Back tracke below: -------------------------------------------------------- Application: Plasma Workspace (plasma), signal SIGABRT [Thread debugging using libthread_db enabled] [New Thread 0xb55de720 (LWP 7115)] [New Thread 0xb1a8bb90 (LWP 7118)] [New Thread 0xb2f48b90 (LWP 7117)] [New Thread 0xb3b33b90 (LWP 7116)] [KCrash handler] #6 0xffffe410 in __kernel_vsyscall () #7 0xb7dfe005 in raise () from /lib/i686/cmov/libc.so.6 #8 0xb7dff981 in abort () from /lib/i686/cmov/libc.so.6 #9 0xb6a54818 in __gnu_cxx::__verbose_terminate_handler () from /usr/lib/libstdc++.so.6 #10 0xb6a526d5 in ?? () from /usr/lib/libstdc++.so.6 #11 0xb6a52712 in std::terminate () from /usr/lib/libstdc++.so.6 #12 0xb6a533b5 in __cxa_pure_virtual () from /usr/lib/libstdc++.so.6 #13 0xb712b339 in QGraphicsItem::sceneBoundingRect (this=0x83f7e88) at graphicsview/qgraphicsitem.cpp:2559 #14 0xb714eca0 in QGraphicsScenePrivate::estimateItemsInRect (this=0x810aff0, rect=@0xbfe68c48) at graphicsview/qgraphicsscene.cpp:351 #15 0xb715f7e1 in QGraphicsViewPrivate::itemsInArea (this=0x8138eb0, path=@0xbfe68d80, mode=Qt::IntersectsItemShape) at graphicsview/qgraphicsview.cpp:1696 #16 0xb715ffb7 in QGraphicsView::items (this=0x81ac078, pos=@0xbfe68ee4) at graphicsview/qgraphicsview.cpp:1755 #17 0xb71600f2 in QGraphicsView::itemAt (this=0x6, pos=@0xbfe68ee4) at graphicsview/qgraphicsview.cpp:1862 #18 0xb71288de in QGraphicsItem::unsetCursor (this=0x83f8390) at graphicsview/qgraphicsitem.cpp:1325 #19 0xb717bbd5 in QGraphicsProxyWidgetPrivate::setWidget_helper ( this=0x8346a70, newWidget=0x0, autoShow=true) at graphicsview/qgraphicsproxywidget.cpp:565 #20 0xb717c153 in QGraphicsProxyWidget::setWidget (this=0x83f8388, widget=0x0) at graphicsview/qgraphicsproxywidget.cpp:550 #21 0xb717c1d6 in ~QGraphicsProxyWidget (this=0x83f8388) at graphicsview/qgraphicsproxywidget.cpp:519 #22 0xb7131464 in ~QGraphicsItem (this=0x83f7e88) at graphicsview/qgraphicsitem.cpp:795 #23 0xb7169fff in ~QGraphicsWidget (this=0x83f7e80) at graphicsview/qgraphicswidget.cpp:219 #24 0xb7cdc7a0 in ~Applet (this=0x83f7e80) at /tmp/buildd/kdebase-workspace-4.0.72/libs/plasma/applet.cpp:408 #25 0xb74c199c in qDeleteInEventHandler (o=0x6) at kernel/qobject.cpp:3595 #26 0xb74c390c in QObject::event (this=0x83f7e80, e=0x83ae040) at kernel/qobject.cpp:1124 #27 0xb716c3bf in QGraphicsWidget::event (this=0x83f7e80, event=0x83ae040) at graphicsview/qgraphicswidget.cpp:1229 #28 0xb6bbfe6c in QApplicationPrivate::notify_helper (this=0x8077a00, receiver=0x83f7e80, e=0x83ae040) at kernel/qapplication.cpp:3766 #29 0xb6bc4a09 in QApplication::notify (this=0x805a670, receiver=0x83f7e80, e=0x83ae040) at kernel/qapplication.cpp:3360 #30 0xb7ae5a4d in KApplication::notify (this=0x805a670, receiver=0x83f7e80, event=0x83ae040) at /tmp/buildd/kde4libs-4.0.72/kdeui/kernel/kapplication.cpp:311 #31 0xb74b31e9 in QCoreApplication::notifyInternal (this=0x805a670, receiver=0x83f7e80, event=0x83ae040) at kernel/qcoreapplication.cpp:587 #32 0xb74b4599 in QCoreApplicationPrivate::sendPostedEvents (receiver=0x0, event_type=0, data=0x804b430) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:215 #33 0xb74b47bd in QCoreApplication::sendPostedEvents (receiver=0x0, event_type=0) at kernel/qcoreapplication.cpp:1091 #34 0xb74de5df in postEventSourceDispatch (s=0x8079ac8) at ../../include/QtCore/../../src/corelib/kernel/qcoreapplication.h:220 #35 0xb5a20978 in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0 #36 0xb5a23bce in ?? () from /usr/lib/libglib-2.0.so.0 #37 0x08079a40 in ?? () #38 0x00000000 in ?? () #0 0xffffe410 in __kernel_vsyscall () ------------------------------------------------------------------------
This looks like a dupe of http://bugs.kde.org/show_bug.cgi?id=161567 which I'm experiencing as well. Regards,
*** Bug 161757 has been marked as a duplicate of this bug. ***
*** Bug 161567 has been marked as a duplicate of this bug. ***
more generic summary + confirmed.
It may the case that this report is a duplicate of bug #163205 and therefore fixed with r816760 (aka after 4.1-beta1, will be part of 4.1-beta2). So, if someone using current trunk and/or 4.1-beta2 or later and is still able to reproduce this: *please* let us know. Thanks in advance :)
I cannot reproduce it using current trunk.