After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 606579 - system monitor reports active programs as sleeping
system monitor reports active programs as sleeping
Status: RESOLVED FIXED
Product: system-monitor
Classification: Core
Component: process list
2.28.x
Other Linux
: Normal normal
: ---
Assigned To: System-monitor maintainers
System-monitor maintainers
Depends on:
Blocks:
 
 
Reported: 2010-01-10 19:30 UTC by Teej
Modified: 2012-12-11 01:18 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Teej 2010-01-10 19:30:11 UTC 
Originally reported to Launchpad at https://bugs.launchpad.net/ubuntu/+source/gnome-system-monitor/+bug/174164

"System Monitor reports processes are sleeping when they obviously are not. Try inserting an audio CD and playing it with Sound Juicer. Then check system monitor. The %CPU for Juicer is >0 but the status is still shown as "sleeping" This happens on many programs."

This is current in Ubuntu Karmic Koala 9.10 with gnome-system-monitor version 2.28.0-0ubuntu1
Comment 1 Benoît Dejean 2011-11-10 17:35:25 UTC 
Well, reading a CD is not CPU intensive and Sound Juicer is statically spending most of this time sleeping.

On every refresh:
 - to get the cpu usage, we compute the difference between the cpu usage before and now and turn it into a %
 - the State column is the raw information given by the kernel.

I don't know, may be could override the State to "Running" if the cpu time has increased since the last refresh ?
Comment 2 André Klapper 2012-02-26 10:46:24 UTC 
[Adding missing "QA Contact" entry so system monitor bug report changes can still be watched via the "Users to watch" list on https://bugzilla.gnome.org/userprefs.cgi?tab=email when the assignee is changed to an individual.]
Comment 3 Robert Roth 2012-12-11 01:18:32 UTC 
This problem has been fixed in the development version. The fix will be available in the next major software release. Thank you for your bug report.