Version: (using KDE 4.2.0) OS: Linux Installed from: Ubuntu Packages After I logged in I opened GIMP and then tried to minimize it. It seemed to be unresponsive so I tried to minimize it again by clicking on it's taskbar entry and then on the minimize button in the top right corner of the window. I finally gave up and then tried to open Dolphin which instantly triggered a crash. Dolphin eventually opened successfully but the crash report was displayed before Dolphin was fully loaded. The following crash report was displayed. Application: Plasma Workspace (plasma), signal SIGSEGV 0x00007fb3b70566e1 in nanosleep () from /lib/libc.so.6 [Current thread is 0 (LWP 6097)] Thread 3 (Thread 0x4214e950 (LWP 6098)): #0 0x00007fb3b4d702d9 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib/libpthread.so.0 #1 0x00007fb3b7b37349 in QWaitCondition::wait () from /usr/lib/libQtCore.so.4 #2 0x00007fb3bb1d529c in ?? () from /usr/lib/libQtNetwork.so.4 #3 0x00007fb3b7b36362 in ?? () from /usr/lib/libQtCore.so.4 #4 0x00007fb3b4d6c3ea in start_thread () from /lib/libpthread.so.0 #5 0x00007fb3b7094cbd in clone () from /lib/libc.so.6 #6 0x0000000000000000 in ?? () Thread 2 (Thread 0x4294f950 (LWP 6099)): #0 0x00007fb3b4d702d9 in pthread_cond_wait@@GLIBC_2.3.2 () from /lib/libpthread.so.0 #1 0x00007fb3b7b37349 in QWaitCondition::wait () from /usr/lib/libQtCore.so.4 #2 0x00007fb39e787ef0 in ?? () from /usr/lib/kde4/plasma_wallpaper_image.so #3 0x00007fb3b7b36362 in ?? () from /usr/lib/libQtCore.so.4 #4 0x00007fb3b4d6c3ea in start_thread () from /lib/libpthread.so.0 #5 0x00007fb3b7094cbd in clone () from /lib/libc.so.6 #6 0x0000000000000000 in ?? () Thread 1 (Thread 0x7fb3b0cdb730 (LWP 6097)): [KCrash Handler] #5 0x00007fb39fbe1bf3 in TaskManager::GroupManager::add () from /usr/lib/libtaskmanager.so.4 #6 0x00007fb39fbe3adb in TaskManager::GroupManager::qt_metacall () from /usr/lib/libtaskmanager.so.4 #7 0x00007fb3b7c33134 in QMetaObject::activate () from /usr/lib/libQtCore.so.4 #8 0x00007fb39fbf9dc2 in TaskManager::TaskManager::taskAdded () from /usr/lib/libtaskmanager.so.4 #9 0x00007fb39fbfbe0f in TaskManager::TaskManager::windowAdded () from /usr/lib/libtaskmanager.so.4 #10 0x00007fb39fbfcdff in TaskManager::TaskManager::qt_metacall () from /usr/lib/libtaskmanager.so.4 #11 0x00007fb3b7c33134 in QMetaObject::activate () from /usr/lib/libQtCore.so.4 #12 0x00007fb3baa3fea2 in KWindowSystem::windowAdded () from /usr/lib/libkdeui.so.5 #13 0x00007fb3baa421fc in ?? () from /usr/lib/libkdeui.so.5 #14 0x00007fb3baa51208 in NETRootInfo::update () from /usr/lib/libkdeui.so.5 #15 0x00007fb3baa5157b in NETRootInfo::event () from /usr/lib/libkdeui.so.5 #16 0x00007fb3baa4267b in ?? () from /usr/lib/libkdeui.so.5 #17 0x00007fb3ba9159f3 in KApplication::x11EventFilter () from /usr/lib/libkdeui.so.5 #18 0x00007fb3bc250434 in ?? () from /usr/lib/libkdeinit4_plasma.so #19 0x00007fb3b839b7ef in ?? () from /usr/lib/libQtGui.so.4 #20 0x00007fb3b83ace26 in QApplication::x11ProcessEvent () from /usr/lib/libQtGui.so.4 #21 0x00007fb3b83d52c4 in ?? () from /usr/lib/libQtGui.so.4 #22 0x00007fb3b338ad3b in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0 #23 0x00007fb3b338e50d in ?? () from /usr/lib/libglib-2.0.so.0 #24 0x00007fb3b338e6cb in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0 #25 0x00007fb3b7c4715f in QEventDispatcherGlib::processEvents () from /usr/lib/libQtCore.so.4 #26 0x00007fb3b83d4a6f in ?? () from /usr/lib/libQtGui.so.4 #27 0x00007fb3b7c1d682 in QEventLoop::processEvents () from /usr/lib/libQtCore.so.4 #28 0x00007fb3b7c1d80d in QEventLoop::exec () from /usr/lib/libQtCore.so.4 #29 0x00007fb3b7c1fcbd in QCoreApplication::exec () from /usr/lib/libQtCore.so.4 #30 0x00007fb3bc23fd6b in kdemain () from /usr/lib/libkdeinit4_plasma.so #31 0x00007fb3b6fcc466 in __libc_start_main () from /lib/libc.so.6 #32 0x00000000004007c9 in _start ()
unfortunately the backtrace isn't overly helpful. it says that it ended up in one of the add methods in GroupManager, evidently while the window manager was not being responsive (from your description). can you follow these instructions: http://techbase.kde.org/Development/Tutorials/Debugging/How_to_create_useful_crash_reports try to reproduce and paste a full backtrace with line numbers? that'd be really helpul. thanks.
*** Bug 180601 has been marked as a duplicate of this bug. ***
*** This bug has been marked as a duplicate of bug 174787 ***