Bug 199845 - Spontanuous crashes of task manager after some hours
Summary: Spontanuous crashes of task manager after some hours
Status: RESOLVED DUPLICATE of bug 197717
Alias: None
Product: plasma4
Classification: Plasma
Component: general (show other bugs)
Version: unspecified
Platform: Unlisted Binaries Linux
: NOR crash
Target Milestone: ---
Assignee: Plasma Bugs List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-07-12 11:40 UTC by Henk Dekker
Modified: 2009-07-12 11:44 UTC (History)
1 user (show)

See Also:
Latest Commit:
Version Fixed In:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Henk Dekker 2009-07-12 11:40:09 UTC
Application that crashed: plasma-desktop
Version of the application: 0.3
KDE Version: 4.2.95 (KDE 4.2.95 (KDE 4.3 RC1))
Qt Version: 4.5.1
Operating System: Linux 2.6.28-12-generic i686
Distribution: Ubuntu 9.04

What I was doing when the application crashed:
Sometimes KDE suddenly disappears, when working in one or another (not KDE) application, for example browsing with Firefox. I haven't found a way of reproducing this.

 -- Backtrace:
Application: Plasma Workspace (kdeinit4), signal: Segmentation fault
[KCrash Handler]
#6  0xa964d32a in TaskManager::GroupManager::manualSortingRequest () from /usr/lib/libtaskmanager.so.4
#7  0xa964b31b in TaskManager::AbstractGroupingStrategy::closeGroup () from /usr/lib/libtaskmanager.so.4
#8  0xa9652f27 in ?? () from /usr/lib/libtaskmanager.so.4
#9  0xa9653e5b in ?? () from /usr/lib/libtaskmanager.so.4
#10 0xb7f74a58 in QMetaObject::activate () from /usr/lib/libQtCore.so.4
#11 0xb7f756e2 in QMetaObject::activate () from /usr/lib/libQtCore.so.4
#12 0xa9666d83 in TaskManager::TaskGroup::itemRemoved () from /usr/lib/libtaskmanager.so.4
#13 0xa96677ab in TaskManager::TaskGroup::remove () from /usr/lib/libtaskmanager.so.4
#14 0xa964dba5 in ?? () from /usr/lib/libtaskmanager.so.4
#15 0xa965046a in TaskManager::GroupManager::qt_metacall () from /usr/lib/libtaskmanager.so.4
#16 0xb7f74a58 in QMetaObject::activate () from /usr/lib/libQtCore.so.4
#17 0xb7f756e2 in QMetaObject::activate () from /usr/lib/libQtCore.so.4
#18 0xa966a823 in TaskManager::TaskManager::taskRemoved () from /usr/lib/libtaskmanager.so.4
#19 0xa966c0cf in TaskManager::TaskManager::windowRemoved () from /usr/lib/libtaskmanager.so.4
#20 0xa966dfec in TaskManager::TaskManager::qt_metacall () from /usr/lib/libtaskmanager.so.4
#21 0xb7f74a58 in QMetaObject::activate () from /usr/lib/libQtCore.so.4
#22 0xb7f756e2 in QMetaObject::activate () from /usr/lib/libQtCore.so.4
#23 0xb767f853 in KWindowSystem::windowRemoved () from /usr/lib/libkdeui.so.5
#24 0xb76820d6 in ?? () from /usr/lib/libkdeui.so.5
#25 0xb7691753 in NETRootInfo::update () from /usr/lib/libkdeui.so.5
#26 0xb7691b3f in NETRootInfo::event () from /usr/lib/libkdeui.so.5
#27 0xb768236d in ?? () from /usr/lib/libkdeui.so.5
#28 0xb75326f9 in KApplication::x11EventFilter () from /usr/lib/libkdeui.so.5
#29 0xb4be0e37 in ?? () from /usr/lib/libkdeinit4_plasma-desktop.so
#30 0xb6a5cc5e in ?? () from /usr/lib/libQtGui.so.4
#31 0xb6a6f4ee in QApplication::x11ProcessEvent () from /usr/lib/libQtGui.so.4
#32 0xb6a9c06a in ?? () from /usr/lib/libQtGui.so.4
#33 0xb65acb88 in g_main_context_dispatch () from /usr/lib/libglib-2.0.so.0
#34 0xb65b00eb in ?? () from /usr/lib/libglib-2.0.so.0
#35 0xb65b0268 in g_main_context_iteration () from /usr/lib/libglib-2.0.so.0
#36 0xb7f8a1d8 in QEventDispatcherGlib::processEvents () from /usr/lib/libQtCore.so.4
#37 0xb6a9b765 in ?? () from /usr/lib/libQtGui.so.4
#38 0xb7f5cdda in QEventLoop::processEvents () from /usr/lib/libQtCore.so.4
#39 0xb7f5d21a in QEventLoop::exec () from /usr/lib/libQtCore.so.4
#40 0xb7f5f6c9 in QCoreApplication::exec () from /usr/lib/libQtCore.so.4
#41 0xb69f9a47 in QApplication::exec () from /usr/lib/libQtGui.so.4
#42 0xb4bcb510 in kdemain () from /usr/lib/libkdeinit4_plasma-desktop.so
#43 0x0804e1c0 in _start ()

This bug may be a duplicate of or related to bug 199552

Reported using DrKonqi
Comment 1 Anne-Marie Mahfouf 2009-07-12 11:44:58 UTC

*** This bug has been marked as a duplicate of bug 197717 ***