242749 2010-06-25 07:31:58 +0000 Plasma crashed when adding a Task Manager to panel. It was vanished somehow already. 2010-06-30 00:05:51 +0000 1 1 10 Unmaintained plasma4 general unspecified Ubuntu Linux RESOLVED DUPLICATE 238537 NOR crash --- 0 yuribratanov plasma-bugs-null asraniel garystriplett 0 oldest_to_newest 982738 0 yuribratanov 2010-06-25 07:31:58 +0000 Application: plasma-desktop (0.3) KDE Platform Version: 4.4.2 (KDE 4.4.2) Qt Version: 4.6.2 Operating System: Linux 2.6.32-22-generic i686 Distribution: Ubuntu 10.04 LTS -- Information about the crash: I cannot add a Task Manager. It was vanished after OS startup. Plasma crashes when try to add a Task manager anywhere on the bottom panel either between App launcher or desktops navigator or system try etc. -- Backtrace: Application: Plasma Workspace (kdeinit4), signal: Segmentation fault [Current thread is 1 (Thread 0xb7787aa0 (LWP 1661))] Thread 2 (Thread 0xaac15b70 (LWP 1663)): #0 __pthread_mutex_unlock (mutex=0x9201aa4) at pthread_mutex_unlock.c:289 #1 0x0131fab8 in g_main_context_prepare () from /lib/libglib-2.0.so.0 #2 0x0131fee9 in ?? () from /lib/libglib-2.0.so.0 #3 0x013204b8 in g_main_context_iteration () from /lib/libglib-2.0.so.0 #4 0x051d060f in QEventDispatcherGlib::processEvents (this=0x92013d8, flags=...) at kernel/qeventdispatcher_glib.cpp:414 #5 0x051a3059 in QEventLoop::processEvents (this=0xaac15290, flags=) at kernel/qeventloop.cpp:149 #6 0x051a34aa in QEventLoop::exec (this=0xaac15290, flags=...) at kernel/qeventloop.cpp:201 #7 0x0509f5a8 in QThread::exec (this=0x91f7fe8) at thread/qthread.cpp:487 #8 0x05182c1b in QInotifyFileSystemWatcherEngine::run (this=0x91f7fe8) at io/qfilesystemwatcher_inotify.cpp:248 #9 0x050a232e in QThreadPrivate::start (arg=0x91f7fe8) at thread/qthread_unix.cpp:248 #10 0x00e9d96e in start_thread (arg=0xaac15b70) at pthread_create.c:300 #11 0x002d3a4e in clone () at ../sysdeps/unix/sysv/linux/i386/clone.S:130 Thread 1 (Thread 0xb7787aa0 (LWP 1661)): [KCrash Handler] #6 0x0509cf39 in QMutex::lock (this=0x8e10c78) at thread/qmutex.cpp:150 #7 0x051a4634 in QCoreApplication::postEvent (receiver=0x94f7e98, event=0x91f9a48, priority=0) at kernel/qcoreapplication.cpp:1113 #8 0x051a49ac in QCoreApplication::postEvent (receiver=0x94f7e98, event=0x91f9a48) at kernel/qcoreapplication.cpp:1066 #9 0x051b48a4 in QObject::deleteLater (this=0x94f7e98) at kernel/qobject.cpp:2158 #10 0x05d16a25 in QX11Data::xdndHandleFinished (this=0x8dda198, xe=0xbfa5ff3c, passive=false) at kernel/qdnd_x11.cpp:1239 #11 0x05cf6eb6 in QApplication::x11ClientMessage (this=0x8dd09b8, w=0x92ba748, event=0xbfa5ff3c, passive_only=false) at kernel/qapplication_x11.cpp:3090 #12 0x05d06879 in QApplication::x11ProcessEvent (this=0x8dd09b8, event=0xbfa5ff3c) at kernel/qapplication_x11.cpp:3633 #13 0x05d3660a in x11EventSourceDispatch (s=0x8dd9840, callback=0, user_data=0x0) at kernel/qguieventdispatcher_glib.cpp:146 #14 0x0131c5e5 in g_main_context_dispatch () from /lib/libglib-2.0.so.0 #15 0x013202d8 in ?? () from /lib/libglib-2.0.so.0 #16 0x013204b8 in g_main_context_iteration () from /lib/libglib-2.0.so.0 #17 0x051d05d5 in QEventDispatcherGlib::processEvents (this=0x8dd69b0, flags=...) at kernel/qeventdispatcher_glib.cpp:412 #18 0x05d36135 in QGuiEventDispatcherGlib::processEvents (this=0x8dd69b0, flags=...) at kernel/qguieventdispatcher_glib.cpp:204 #19 0x051a3059 in QEventLoop::processEvents (this=0xbfa60234, flags=) at kernel/qeventloop.cpp:149 #20 0x051a34aa in QEventLoop::exec (this=0xbfa60234, flags=...) at kernel/qeventloop.cpp:201 #21 0x051a769f in QCoreApplication::exec () at kernel/qcoreapplication.cpp:981 #22 0x05c76577 in QApplication::exec () at kernel/qapplication.cpp:3579 #23 0x0290805e in kdemain () from /usr/lib/libkdeinit4_plasma-desktop.so #24 0x0804e133 in _start () Possible duplicates by query: bug 242629, bug 242181, bug 238537, bug 236374, bug 235790. Reported using DrKonqi 982789 1 asraniel 2010-06-25 10:36:19 +0000 *** This bug has been marked as a duplicate of bug 238537 *** 984493 2 asraniel 2010-06-30 00:05:51 +0000 *** Bug 243188 has been marked as a duplicate of this bug. ***