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 605711 - Bug with changing priority.
Bug with changing priority.
Status: RESOLVED DUPLICATE of bug 491462
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: 2009-12-30 02:56 UTC by gamingtechnology
Modified: 2012-12-06 22:35 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description gamingtechnology 2009-12-30 02:56:08 UTC 
System monitor does not allow the user to increase the priority of a process.This issue still exists after so long. If you run gnome-system-monitor as root, there will be no issues but running it as root only sees root applications and even if it does see the user processed, this is a bug and gnome-system-monitor should allow regular users to increase the process priority (decrease in the numerical value). This is probably not given importance because CPUs today are more powerful but when you're running an application such as a game that uses up all of your system ressources and you want to get the most out of your CPU, this proves to be very useful. This is just one example.

http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=515567
Comment 1 André Klapper 2012-02-26 10:45:40 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 2 Robert Roth 2012-12-06 22:35:49 UTC 
Bug #491462 discusses using PolicyKit for executing actions (kill/renice) on processes not started by the current user, therefor I am marking this as a duplicate of that ticket.

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