GNOME-system-monitor max's out the CPU, sometimes up to 100%

[LostOverThere]

Binary package hint: gnome-system-monitor

On some machines, the gnome-system-monitor max's out the system's CPU anywhere between 10-100% (it varies very rapidly). This problem is caused by the programme reacting to SELinux not being enabled. This can be identified but attempting to run the programme through the terminal. An error will be given like this:

** (gnome-system-monitor:10555): WARNING **: SELinux was found but is not enabled.

This is what I [strongly] believe is causing the problem here. I have encounted this problem ever since Ubuntu Feisty Fawn and am currently running 8.10.

Thank-you

ProblemType: Bug
Architecture: i386
DistroRelease: Ubuntu 8.10
ExecutablePath: /usr/bin/gnome-system-monitor
Package: gnome-system-monitor 2.24.1-0ubuntu1
ProcEnviron:
 SHELL=/bin/bash
 PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin:/usr/games
 LANG=en_AU.UTF-8
SourcePackage: gnome-system-monitor
Uname: Linux 2.6.27-7-generic i686

[olmec (olmecs)]

How to activate / enable SELinux to rectify the issue as you describe?

[LostOverThere (lostoverthere)]

I never activate SELinux at all. This problem occurs for me from the default, freshly installed system. Sorry I couldn't be more specific.

[ullix (ullix)]

I have a similar issue with a Ubuntu Intrepid install on an Acer Aspire One netbook, where gnome-system-monitor plus Xorg consume 60+% CPU, shown both by top and g-s-m.

Running top in maximized gnome-terminal after cold start. CPU usage from Xorg:1-3%, total: 3-5%
Starting g-s-m and hiding behind the maximized terminal window: CPU usage slowly creeps up, becoming stable at CPU usage as reported by top of Xorg:~35% and g-s-m:~35%. All other processes combined <3%. Load average by top after ~10min is 0.73/0.78/0.56. Switching to the g-s-m window shows CPU1 and CPU2 each at 30-40%.

uname -a: Linux aa1 2.6.27-7-generic #1 SMP Tue Nov 4 19:33:20 UTC 2008 i686 GNU/Linux

[Pedro Villavicencio (pedro)]

how could you know that SELinux is causing the issue if you never enabled it at all? this looks like bug 187383

[LostOverThere (lostoverthere)]

Sorry, just because gnome-system-monitor complains about it, I naturely assumed it had something to do with it. :\

[Pedro Villavicencio (pedro)]

ok no problem, marking this as dup then, thanks.