Application that crashed: plasma-desktop Version of the application: 0.3 KDE Version: 4.2.85 (KDE 4.2.85 (KDE 4.3 Beta1)) Qt Version: 4.5.1 Operating System: Linux 2.6.28-12-generic x86_64 Distribution: Ubuntu 9.04 What I was doing when the application crashed: I was opening Netbeans when plasma crash. Maybe it crashed by high memory consumption by Netbeans. -- Backtrace: Application: Plasma Workspace (plasma-desktop), signal: Segmentation fault [KCrash Handler] #5 0x00007f5c4ccc9b00 in TaskManager::Task::window () from /usr/lib/libtaskmanager.so.4 #6 0x00007f5c4cf07ade in ?? () from /usr/lib/kde4/plasma_applet_tasks.so #7 0x00007f5c64742bb3 in QObject::event () from /usr/lib/libQtCore.so.4 #8 0x00007f5c65457e7b in QGraphicsWidget::event () from /usr/lib/libQtGui.so.4 #9 0x00007f5c64e3cb9d in QApplicationPrivate::notify_helper () from /usr/lib/libQtGui.so.4 #10 0x00007f5c64e44dea in QApplication::notify () from /usr/lib/libQtGui.so.4 #11 0x00007f5c675011ab in KApplication::notify () from /usr/lib/libkdeui.so.5 #12 0x00007f5c64732dfc in QCoreApplication::notifyInternal () from /usr/lib/libQtCore.so.4 #13 0x00007f5c6475feb6 in ?? () from /usr/lib/libQtCore.so.4 #14 0x00007f5c6475c5cd in ?? () from /usr/lib/libQtCore.so.4 #15 0x00007f5c5f13020a in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0 #16 0x00007f5c5f1338e0 in ?? () from /usr/lib/libglib-2.0.so.0 #17 0x00007f5c5f133a7c in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0 #18 0x00007f5c6475c52f in QEventDispatcherGlib::processEvents () from /usr/lib/libQtCore.so.4 #19 0x00007f5c64ed570f in ?? () from /usr/lib/libQtGui.so.4 #20 0x00007f5c647316a2 in QEventLoop::processEvents () from /usr/lib/libQtCore.so.4 #21 0x00007f5c64731a6d in QEventLoop::exec () from /usr/lib/libQtCore.so.4 #22 0x00007f5c64733d34 in QCoreApplication::exec () from /usr/lib/libQtCore.so.4 #23 0x00007f5c68eab29b in kdemain () from /usr/lib/libkdeinit4_plasma-desktop.so #24 0x00007f5c63aed5a6 in __libc_start_main () from /lib/libc.so.6 #25 0x00000000004007c9 in _start ()
*** This bug has been marked as a duplicate of bug 191412 ***