Application that crashed: plasma-desktop Version of the application: 0.3 KDE Version: 4.3.4 (KDE 4.3.4) Qt Version: 4.5.2 Operating System: Linux 2.6.31-16-generic i686 Distribution: Ubuntu 9.10 What I was doing when the application crashed: i have configured 2 multiple desktops with diferent plasmoids -- Backtrace: Application: Área de Trabalho do Plasma (kdeinit4), signal: Segmentation fault [Current thread is 1 (Thread 0xb7769700 (LWP 2384))] Thread 2 (Thread 0xaa73bb70 (LWP 2475)): #0 0x00355422 in __kernel_vsyscall () #1 0x00ca5e15 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib/tls/i686/cmov/libpthread.so.0 #2 0x00c3178d in pthread_cond_wait () from /lib/tls/i686/cmov/libc.so.6 #3 0x004a4e67 in QWaitCondition::wait(QMutex*, unsigned long) () from /usr/lib/libQtCore.so.4 #4 0x07cb0922 in ?? () from /usr/lib/libQtNetwork.so.4 #5 0x004a3e32 in ?? () from /usr/lib/libQtCore.so.4 #6 0x00ca180e in start_thread () from /lib/tls/i686/cmov/libpthread.so.0 #7 0x00c247ee in clone () from /lib/tls/i686/cmov/libc.so.6 Thread 1 (Thread 0xb7769700 (LWP 2384)): [KCrash Handler] #6 0x0751218a in QGraphicsItem::isWidget() const () from /usr/lib/libQtGui.so.4 #7 0x0754b527 in QGraphicsScene::event(QEvent*) () from /usr/lib/libQtGui.so.4 #8 0x06f0ef54 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib/libQtGui.so.4 #9 0x06f1667c in QApplication::notify(QObject*, QEvent*) () from /usr/lib/libQtGui.so.4 #10 0x00fca1aa in KApplication::notify(QObject*, QEvent*) () from /usr/lib/libkdeui.so.5 #11 0x005946cb in QCoreApplication::notifyInternal(QObject*, QEvent*) () from /usr/lib/libQtCore.so.4 #12 0x0755c5e7 in QGraphicsView::viewportEvent(QEvent*) () from /usr/lib/libQtGui.so.4 #13 0x073b4a95 in ?? () from /usr/lib/libQtGui.so.4 #14 0x0059383a in QCoreApplicationPrivate::sendThroughObjectEventFilters(QObject*, QEvent*) () from /usr/lib/libQtCore.so.4 #15 0x06f0ef2c in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib/libQtGui.so.4 #16 0x06f165ca in QApplication::notify(QObject*, QEvent*) () from /usr/lib/libQtGui.so.4 #17 0x00fca1aa in KApplication::notify(QObject*, QEvent*) () from /usr/lib/libkdeui.so.5 #18 0x005946cb in QCoreApplication::notifyInternal(QObject*, QEvent*) () from /usr/lib/libQtCore.so.4 #19 0x06f63ad5 in QWidget::event(QEvent*) () from /usr/lib/libQtGui.so.4 #20 0x07313633 in QFrame::event(QEvent*) () from /usr/lib/libQtGui.so.4 #21 0x073b2faa in QAbstractScrollArea::event(QEvent*) () from /usr/lib/libQtGui.so.4 #22 0x0755c406 in QGraphicsView::event(QEvent*) () from /usr/lib/libQtGui.so.4 #23 0x06f0ef54 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib/libQtGui.so.4 #24 0x06f165ca in QApplication::notify(QObject*, QEvent*) () from /usr/lib/libQtGui.so.4 #25 0x00fca1aa in KApplication::notify(QObject*, QEvent*) () from /usr/lib/libkdeui.so.5 #26 0x005946cb in QCoreApplication::notifyInternal(QObject*, QEvent*) () from /usr/lib/libQtCore.so.4 #27 0x06f19df6 in QApplication::setActiveWindow(QWidget*) () from /usr/lib/libQtGui.so.4 #28 0x06f8321f in QApplication::x11ProcessEvent(_XEvent*) () from /usr/lib/libQtGui.so.4 #29 0x06fb0502 in ?? () from /usr/lib/libQtGui.so.4 #30 0x002cfe78 in g_main_context_dispatch () from /lib/libglib-2.0.so.0 #31 0x002d3720 in ?? () from /lib/libglib-2.0.so.0 #32 0x002d3853 in g_main_context_iteration () from /lib/libglib-2.0.so.0 #33 0x005bf02c in QEventDispatcherGlib::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQtCore.so.4 #34 0x06fafbe5 in ?? () from /usr/lib/libQtGui.so.4 #35 0x00592c79 in QEventLoop::processEvents(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQtCore.so.4 #36 0x005930ca in QEventLoop::exec(QFlags<QEventLoop::ProcessEventsFlag>) () from /usr/lib/libQtCore.so.4 #37 0x0059553f in QCoreApplication::exec() () from /usr/lib/libQtCore.so.4 #38 0x06f0edd7 in QApplication::exec() () from /usr/lib/libQtGui.so.4 #39 0x019e380d in kdemain () from /usr/lib/libkdeinit4_plasma-desktop.so #40 0x0804dde1 in _start () Reported using DrKonqi
This appears to be related to bug 203296, thanks. *** This bug has been marked as a duplicate of bug 203296 ***