CPU usage instead of CPU time

Bug #58304 reported by saads
4
Affects Status Importance Assigned to Milestone
gnome-system-monitor (Ubuntu)
Fix Released
Low
Ubuntu Desktop Bugs

Bug Description

Binary package hint: gnome-system-monitor

In Dapper under the gnome-system-monitor's processes tab you could view the CPU usage of each process. This would allow you to sort the processes by most CPU-intensive. Very useful for when one process is consuming too much CPU or when a program crashes taking up 100% CPU and you want to kill it. Now (in Edgy), there is a column for CPU time which is not nearly as useful for this purpose. Would it be possible to have both?

Revision history for this message
Daniel Holbach (dholbach) wrote :

Thanks for your report. This should be the default. What does
 LC_ALL=C gconftool-2 -g /schemas/apps/procman/proctree/col_9_visible
say?

Changed in gnome-system-monitor:
assignee: nobody → desktop-bugs
importance: Untriaged → Low
status: Unconfirmed → Needs Info
Revision history for this message
saads (shakhshir) wrote : Re: [Bug 58304] Re: CPU usage instead of CPU time

It says:

Type: bool
List Type: *invalid*
Car Type: *invalid*
Cdr Type: *invalid*
Default Value: true
Owner: procman
Short Desc: Show process CPU time column on startup
Long Desc: Unset

On 8/31/06, Daniel Holbach <email address hidden> wrote:
>
> Thanks for your report. This should be the default. What does
> LC_ALL=C gconftool-2 -g /schemas/apps/procman/proctree/col_9_visible
> say?
>
> ** Changed in: gnome-system-monitor (Ubuntu)
> Importance: Untriaged => Low
> Assignee: (unassigned) => Ubuntu Desktop Bugs
> Status: Unconfirmed => Needs Info
>
> --
> CPU usage instead of CPU time
> https://launchpad.net/bugs/58304
>

Revision history for this message
Daniel Holbach (dholbach) wrote :

I reopened the upstream bug, where we requested the change earlier this year: http://bugzilla.gnome.org/show_bug.cgi?id=341026 - I'll make the necessary change soonish (once we got Edgy Knot-2 out the door).

Changed in gnome-system-monitor:
status: Needs Info → Fix Committed
Revision history for this message
saads (shakhshir) wrote :

Excellent. Thanks.

Revision history for this message
Sebastien Bacher (seb128) wrote :

This upload fixes the issue:

 gnome-system-monitor (2.16.0-0ubuntu1) edgy; urgency=low
 .
   * New upstream version:
     - Fixed a small memory leak.
     - Fixed schema. (Ubuntu: #58304)
   * debian/patches/03_autoconf.patch:
     - updated

Changed in gnome-system-monitor:
status: Fix Committed → Fix Released
Revision history for this message
saads (shakhshir) wrote :

Unfortunately this hasn't actually been fixed. I am running Edgy with everything up-to-date and specifically gnome-system-monitor (2.16.0-0ubuntu1). I've attached a screenshot.

'apt-cache show gnome-system-monitor' gives:

Package: gnome-system-monitor
Priority: optional
Section: gnome
Installed-Size: 3968
Maintainer: Sebastien Bacher <email address hidden>
Architecture: i386
Version: 2.16.0-0ubuntu1

Revision history for this message
saads (shakhshir) wrote :

Sebastien, can you please change back the status of this bug. It has not
been fixed.

Revision history for this message
Sebastien Bacher (seb128) wrote :

Does it happen with an another user too? That might an user configuration written for that application for your user

Revision history for this message
saads (shakhshir) wrote :

Yes, it is. I checked under gconf -> apps -> procman -> proctree. col9 was
set to visible instead of col8, which is the CPU %. I tested it by creating
a new user and the default is set correctly to col8. So the bug has been
fixed.

Thanks.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.