This started recently - any idea what is causing this ? And how to fix it?
PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
2433 gene 20 0 1102m 74m 40m R 94.9 0.6 295:43.55 plasma-desktop
Thanks.
On 06/27/2011 07:51 AM, Genes MailLists wrote:
This started recently - any idea what is causing this ? And how to fix it?
PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
2433 gene 20 0 1102m 74m 40m R 94.9 0.6 295:43.55 plasma-desktop
logging off and back on seems to have fixed it for now ... not sure what I can do to track it down ?
Thanks - gene
On Mon, Jun 27, 2011 at 1:59 PM, Genes MailLists lists@sapience.com wrote:
On 06/27/2011 07:51 AM, Genes MailLists wrote:
This started recently - any idea what is causing this ? And how to fix it?
PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
2433 gene 20 0 1102m 74m 40m R 94.9 0.6 295:43.55 plasma-desktop
logging off and back on seems to have fixed it for now ... not sure what I can do to track it down ?
Same problem here, I've reported in BZ https://bugzilla.redhat.com/show_bug.cgi?id=710918
Instead of logging out and in, you can simply do "killall plasma-desktop;sleep 2;plasma-desktop&" in a terminal to temporarily fix the problem.
-MartinG
On 06/27/2011 11:30 AM, MartinG wrote:
killall plasma-desktop;sleep 2;plasma-desktop&
Good thank you - better than logging out - I added a me too to the bz.
Its still happening here - 100% CPU - and the above does not work for me. The plasma-desktop does not start up properly unfortunately and I'm left with no panels at all and no background menu .. and all I can do is shutdown -r now.
If I don't try restarting the plasma-desktop - then I can logoff and login again and things are normal - in my case for a couple of weeks before something triggered it ..
I have no widgets anywhere except a terminal icon on the panel - and the desktop folder on the background.
I see: https://bugzilla.redhat.com/show_bug.cgi?id=697350
except in my case I have no cpu monitor applet at all .. so similar symptoms but not casued by cpu monitor.
gene
On 07/05/2011 05:30 PM, Genes MailLists wrote:
This keeps happening - i am not running any monitor applets - in fact i have no applets at all.
PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
24175 gene 20 0 1007m 58m 32m R 91.6 0.5 47:47.62 plasma-desktop
The only cure is to logout and back in.
killing plasma-desktop and hand restarting does not work.
attaching debugger gives this info - hopefully its useful:
#0 0x00000039c90d2845 in _xstat () from /lib64/libc.so.6 #1 0x00000039c909d3fd in __tzfile_read () from /lib64/libc.so.6 #2 0x00000039c909cd57 in tzset_internal.part.0 () from /lib64/libc.so.6 #3 0x00000039c909cfeb in tzset () from /lib64/libc.so.6 #4 0x0000003b1ee82700 in QTime::currentTime() () from /usr/lib64/libQtCore.so.4 #5 0x0000003b1ee827e9 in QTime::start() () from /usr/lib64/libQtCore.so.4 #6 0x0000003b2d138782 in Plasma::DataContainer::setData(QString const&, QVariant const&) () from /usr/lib64/libplasma.so.3 #7 0x00007f02d261bc61 in ?? () from /usr/lib64/kde4/plasma_engine_systemmonitor.so #8 0x00007f02d2409148 in KSGRD::SensorAgent::processAnswer(char const*, int) () from /usr/lib64/libksgrd.so.4 #9 0x00007f02d2411c3e in ?? () from /usr/lib64/libksgrd.so.4 #10 0x00007f02d2412578 in ?? () from /usr/lib64/libksgrd.so.4 #11 0x0000003b1ef6ceba in QMetaObject::activate(QObject*, QMetaObject const*, int, void**) () from /usr/lib64/libQtCore.so.4 #12 0x0000003b1eefe4fb in ?? () from /usr/lib64/libQtCore.so.4 #13 0x0000003b1eeff8c9 in QProcess::qt_metacall(QMetaObject::Call, int, void**) () from /usr/lib64/libQtCore.so.4 #14 0x0000003b201218a8 in KProcess::qt_metacall(QMetaObject::Call, int, void**) () from /usr/lib64/libkdecore.so.5
#15 0x0000003b1ef6ceba in QMetaObject::activate(QObject*, QMetaObject const*, int, void**) () from /usr/lib64/libQtCore.so.4
#16 0x0000003b1efb5e4e in QSocketNotifier::activated(int) () from /usr/lib64/libQtCore.so.4 #17 0x0000003b1ef74c0b in QSocketNotifier::event(QEvent*) () from /usr/lib64/libQtCore.so.4 #18 0x0000003b207b7444 in QApplicationPrivate::notify_helper(QObject*, QEvent*) () from /usr/lib64/libQtGui.so.4 #19 0x0000003b207bc2d1 in QApplication::notify(QObject*, QEvent*) () from /usr/lib64/libQtGui.so.4 #20 0x0000003b22241806 in KApplication::notify(QObject*, QEvent*) () from /usr/lib64/libkdeui.so.5 #21 0x0000003b1ef5a1ac in QCoreApplication::notifyInternal(QObject*, QEvent*) () from /usr/lib64/libQtCore.so.4 #22 0x0000003b1ef84427 in ?? () from /usr/lib64/libQtCore.so.4
#23 0x00000039cc0427ed in g_main_context_dispatch () from /lib64/libglib-2.0.so.0 #24 0x00000039cc042fc8 in ?? () from /lib64/libglib-2.0.so.0
#25 0x00000039cc04325c in g_main_context_iteration () from /lib64/libglib-2.0.so.0 #26 0x0000003b1ef84d0f in QEventDispatcherGlib::processEvents(QFlagsQEventLoop::ProcessEventsFlag) () from /usr/lib64/libQtCore.so.4 #27 0x0000003b20859fde in ?? () from /usr/lib64/libQtGui.so.4 #28 0x0000003b1ef596c2 in QEventLoop::processEvents(QFlagsQEventLoop::ProcessEventsFlag) () from /usr/lib64/libQtCore.so.4 #29 0x0000003b1ef598bf in QEventLoop::exec(QFlagsQEventLoop::ProcessEventsFlag) () from /usr/lib64/libQtCore.so.4 #30 0x0000003b1ef5da07 in QCoreApplication::exec() () from /usr/lib64/libQtCore.so.4 #31 0x0000003b2863f1e3 in kdemain () from /usr/lib64/libkdeinit4_plasma-desktop.so #32 0x00000039c902139d in __libc_start_main () from /lib64/libc.so.6 #33 0x00000000004008c1 in _start () [gene@lap3 bugs]$
On 07/13/2011 10:44 AM, Genes MailLists wrote:
#7 0x00007f02d261bc61 in ?? () from /usr/lib64/kde4/plasma_engine_systemmonitor.so #8 0x00007f02d2409148 in KSGRD::SensorAgent::processAnswer(char const*, int) () from /usr/lib64/libksgrd.so.4
No widgets?
I wonder why plasma_engine_systemmonitor is spinning there then.
-- rex
On 07/13/2011 11:49 AM, Rex Dieter wrote:
On 07/13/2011 10:44 AM, Genes MailLists wrote:
#7 0x00007f02d261bc61 in ?? () from /usr/lib64/kde4/plasma_engine_systemmonitor.so #8 0x00007f02d2409148 in KSGRD::SensorAgent::processAnswer(char const*, int) () from /usr/lib64/libksgrd.so.4
No widgets?
I wonder why plasma_engine_systemmonitor is spinning there then.
Hi rex - thanks for followup.
Sorry if I was not precise - I meant I did not add any widgets beyond that provided in stock fresh user.
The desktop folder is there (is that a widget?). Also,
I have 2 panels - one is the default panel (menu, pager and the thing that shows programs that are running - forget the name, the system tray and clock).
The other panel has a few icons to launch common programs - these were dragged from the menu.
Perhaps the standard panel parts are considered widgets?
I meant I added no widgets other than the stock provided.
I don't know what triggers this ... seems just normal usage - which for me is a load of terminals - and thunderbird, google-chrome. I also sometimes run other programs - today (but not the last time it got 100% cpu) I am using mathematica.
gene
Genes MailLists wrote:
On 07/05/2011 05:30 PM, Genes MailLists wrote:
This keeps happening - i am not running any monitor applets - in fact i have no applets at all.
PID USER PR NI VIRT RES SHR S %CPU %MEM TIME+ COMMAND
24175 gene 20 0 1007m 58m 32m R 91.6 0.5 47:47.62 plasma-desktop
The only cure is to logout and back in.
killing plasma-desktop and hand restarting does not work.
attaching debugger gives this info - hopefully its useful:
#0 0x00000039c90d2845 in _xstat () from /lib64/libc.so.6 #1 0x00000039c909d3fd in __tzfile_read () from /lib64/libc.so.6 #2 0x00000039c909cd57 in tzset_internal.part.0 () from /lib64/libc.so.6 #3 0x00000039c909cfeb in tzset () from /lib64/libc.so.6 #4 0x0000003b1ee82700 in QTime::currentTime() () from /usr/lib64/libQtCore.so.4 #5 0x0000003b1ee827e9 in QTime::start() () from /usr/lib64/libQtCore.so.4 #6 0x0000003b2d138782 in Plasma::DataContainer::setData(QString const&, QVariant const&) () from /usr/lib64/libplasma.so.3 #7 0x00007f02d261bc61 in ?? () from /usr/lib64/kde4/plasma_engine_systemmonitor.so #8 0x00007f02d2409148 in KSGRD::SensorAgent::processAnswer(char const*, int) () from /usr/lib64/libksgrd.so.4 #9 0x00007f02d2411c3e in ?? () from /usr/lib64/libksgrd.so.4 #10 0x00007f02d2412578 in ?? () from /usr/lib64/libksgrd.so.4
OK, this could theoretically be useful, *if* we had some more -debuginfo, kdebase-workspace-debuginfo in particular.
-- rex
On 07/13/2011 12:27 PM, Rex Dieter wrote:
OK, this could theoretically be useful, *if* we had some more -debuginfo, kdebase-workspace-debuginfo in particular.
-- rex
Ok no problem - so if I install kdebase-workspace-debuginfo and run gdb next time it happens - it will be more useful right? Or is there something more I should do?
gene/
On 07/13/2011 12:35 PM, Genes MailLists wrote:
On 07/13/2011 12:27 PM, Rex Dieter wrote:
OK, this could theoretically be useful, *if* we had some more -debuginfo, kdebase-workspace-debuginfo in particular.
-- rex
Ok no problem - so if I install kdebase-workspace-debuginfo and run gdb next time it happens - it will be more useful right?
yes (hopefully).
-- rex
On 07/13/2011 02:19 PM, Rex Dieter wrote:
On 07/13/2011 12:35 PM, Genes MailLists wrote:
On 07/13/2011 12:27 PM, Rex Dieter wrote:
OK, this could theoretically be useful, *if* we had some more -debuginfo, kdebase-workspace-debuginfo in particular.
-- rex
Ok no problem - so if I install kdebase-workspace-debuginfo and run gdb next time it happens - it will be more useful right?
yes (hopefully).
installed - will report back next time plasma-desk gets upset ... she has a bit of a temper so should be less than a week before she has another tantrum .. :-)
On 07/13/2011 02:36 PM, Genes MailLists wrote:
Ok no problem - so if I install kdebase-workspace-debuginfo and run gdb next time it happens - it will be more useful right?
yes (hopefully).
installed - will report back next time plasma-desk gets upset ... she has a bit of a temper so should be less than a week before she has another tantrum .. :-)
Ok it happened again - brought into debugger - broke - got backtrace - continued and repeated - I get the following 2 (hope it means something to someone ...)
(gdb) bt #0 0x00000039c90d7293 in poll () from /lib64/libc.so.6 #1 0x00000039cc042d24 in ?? () from /lib64/libglib-2.0.so.0 #2 0x00000039cc04325c in g_main_context_iteration () from /lib64/libglib-2.0.so.0 #3 0x0000003b1ef84d0f in QEventDispatcherGlib::processEvents (this=0x13227e0, flags=<optimized out>) at kernel/qeventdispatcher_glib.cpp:422 #4 0x0000003157859fde in QGuiEventDispatcherGlib::processEvents (this=<optimized out>, flags=<optimized out>) at kernel/qguieventdispatcher_glib.cpp:207 #5 0x0000003b1ef596c2 in QEventLoop::processEvents (this=<optimized out>, flags=...) at kernel/qeventloop.cpp:149 #6 0x0000003b1ef598bf in QEventLoop::exec (this=0x7fff4baf5dc0, flags=...) at kernel/qeventloop.cpp:201 #7 0x0000003b1ef5da07 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1008 #8 0x000000315e83f203 in kdemain (argc=2, argv=0x7fff4baf61a8) at /usr/src/debug/kdebase-workspace-4.6.5/plasma/desktop/shell/main.cpp:120 #9 0x00000039c902139d in __libc_start_main () from /lib64/libc.so.6 #10 0x00000000004008c1 in _start () ------------------------------------------------------------------------------- (gdb) bt #0 0x00000039c90d2845 in _xstat () from /lib64/libc.so.6 #1 0x00000039c909d3fd in __tzfile_read () from /lib64/libc.so.6 #2 0x00000039c909cd57 in tzset_internal.part.0 () from /lib64/libc.so.6 #3 0x00000039c909cfeb in tzset () from /lib64/libc.so.6 #4 0x0000003b1ee82700 in QTime::currentTime () at tools/qdatetime.cpp:3094 #5 0x0000003b1ee827e9 in QTime::start (this=0x2202cd0) at tools/qdatetime.cpp:1951 #6 0x000000315f738782 in Plasma::DataContainer::setData(QString const&, QVariant const&) () from /usr/lib64/libplasma.so.3 #7 0x00007f0903385b8b in SystemMonitorEngine::answerReceived (this=0x1ca1b60, id=<optimized out>, answer=...) at /usr/src/debug/kdebase-workspace-4.6.5/plasma/generic/dataengines/systemmonitor/systemmonitor.cpp:133 #8 0x00007f0903173148 in KSGRD::SensorAgent::processAnswer (this=0x1c9dd50, buf=<optimized out>, buflen=<optimized out>) at /usr/src/debug/kdebase-workspace-4.6.5/ksysguard/gui/ksgrd/SensorAgent.cpp:184 #9 0x00007f090317bc3e in KSGRD::SensorShellAgent::msgRcvd (this=0x1c9dd50) at /usr/src/debug/kdebase-workspace-4.6.5/ksysguard/gui/ksgrd/SensorShellAgent.cpp:91 #10 0x00007f090317c578 in KSGRD::SensorShellAgent::qt_metacall (this=0x1c9dd50, _c= QMetaObject::InvokeMetaMethod, _id=<optimized out>, _a=0x7fff4baf5310) at /usr/src/debug/kdebase-workspace-4.6.5/x86_64-redhat-linux-gnu/ksysguard/gui/ksgrd/SensorShellAgent.moc:78 #11 0x0000003b1ef6ceba in QMetaObject::activate (sender=0x1c995f0, m=<optimized out>, local_signal_index=<optimized out>, argv=0x0) at kernel/qobject.cpp:3278 #12 0x0000003b1eefe4fb in QProcessPrivate::_q_canReadStandardOutput (this=0x1c97d50) at io/qprocess.cpp:897 #13 0x0000003b1eeff8c9 in QProcess::qt_metacall (this=0x1c995f0, _c=QMetaObject::InvokeMetaMethod, _id=9, _a= 0x7fff4baf5510) at .moc/release-shared/moc_qprocess.cpp:107 #14 0x00000031571218b8 in KProcess::qt_metacall(QMetaObject::Call, int, void**) () from /usr/lib64/libkdecore.so.5 #15 0x0000003b1ef6ceba in QMetaObject::activate (sender=0x1c97930, m=<optimized out>, local_signal_index=<optimized out>, argv=0x7fff4baf5510) at kernel/qobject.cpp:3278 #16 0x0000003b1efb5e4e in QSocketNotifier::activated (this=<optimized out>, _t1=17) at .moc/release-shared/moc_qsocketnotifier.cpp:89 #17 0x0000003b1ef74c0b in QSocketNotifier::event (this=0x1c97930, e=0x7fff4baf5b80) at kernel/qsocketnotifier.cpp:317 #18 0x00000031577b7444 in notify_helper (e=0x7fff4baf5b80, receiver=0x1c97930, this=0x138a100) at kernel/qapplication.cpp:4462 #19 QApplicationPrivate::notify_helper (this=0x138a100, receiver=0x1c97930, e=0x7fff4baf5b80) at kernel/qapplication.cpp:4434 #20 0x00000031577bc2d1 in QApplication::notify (this=0x136ac10, receiver=0x1c97930, e=0x7fff4baf5b80) at kernel/qapplication.cpp:4341 #21 0x0000003158e41d56 in KApplication::notify(QObject*, QEvent*) () from /usr/lib64/libkdeui.so.5 #22 0x0000003b1ef5a1ac in QCoreApplication::notifyInternal (this=0x136ac10, receiver=0x1c97930, event= 0x7fff4baf5b80) at kernel/qcoreapplication.cpp:731 #23 0x0000003b1ef84427 in sendEvent (event=0x7fff4baf5b80, receiver=<optimized out>) at kernel/qcoreapplication.h:215 #24 socketNotifierSourceDispatch (source=0x138c9d0) at kernel/qeventdispatcher_glib.cpp:110 #25 0x00000039cc0427ed in g_main_context_dispatch () from /lib64/libglib-2.0.so.0 #26 0x00000039cc042fc8 in ?? () from /lib64/libglib-2.0.so.0 #27 0x00000039cc04325c in g_main_context_iteration () from /lib64/libglib-2.0.so.0 #28 0x0000003b1ef84d0f in QEventDispatcherGlib::processEvents (this=0x13227e0, flags=<optimized out>) at kernel/qeventdispatcher_glib.cpp:422 #29 0x0000003157859fde in QGuiEventDispatcherGlib::processEvents (this=<optimized out>, flags=<optimized out>) at kernel/qguieventdispatcher_glib.cpp:207 #30 0x0000003b1ef596c2 in QEventLoop::processEvents (this=<optimized out>, flags=...) at kernel/qeventloop.cpp:149 #31 0x0000003b1ef598bf in QEventLoop::exec (this=0x7fff4baf5dc0, flags=...) at kernel/qeventloop.cpp:201 #32 0x0000003b1ef5da07 in QCoreApplication::exec () at kernel/qcoreapplication.cpp:1008 #33 0x000000315e83f203 in kdemain (argc=2, argv=0x7fff4baf61a8) at /usr/src/debug/kdebase-workspace-4.6.5/plasma/desktop/shell/main.cpp:120 #34 0x00000039c902139d in __libc_start_main () from /lib64/libc.so.6 #35 0x00000000004008c1 in _start () ------------------------------------------------------