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 645662 - gnome-system-monitor crashes on machines with more than 4 CPUs.
gnome-system-monitor crashes on machines with more than 4 CPUs.
Status: RESOLVED FIXED
Product: system-monitor
Classification: Core
Component: general
git master
Other Linux
: Normal critical
: ---
Assigned To: System-monitor maintainers
System-monitor maintainers
Depends on:
Blocks:
 
 
Reported: 2011-03-25 20:22 UTC by Diego
Modified: 2011-11-11 10:03 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Diego 2011-03-25 20:22:09 UTC 
When I try to run gnome-system-monitor (version 2.99.2-1) on Fedora 15 with Gnome 3 I get the following error:

"Gtk-Message: Failed to load module "pk-gtk-module"

GLib-GIO-ERROR **: Settings schema 'org.gnome.gnome-system-monitor' does not contain a key named 'cpu-color4'
aborting...
Aborted (core dumped)"

I'm running an intel quad core i7 with hyperthreading, which I imagine is the reason for the error.
Comment 1 André Klapper 2011-03-25 22:10:13 UTC 
Thanks for the bug report. This particular bug has already been reported into our bug tracking system, but please feel free to report any further bugs you find.

*** This bug has been marked as a duplicate of bug 635939 ***
Comment 2 André Klapper 2011-03-25 22:55:11 UTC 
Reopening as per
<borschty> andre_, why are these reports duplicates? one is about a problem with the visual appearance and the other one is about missing schemas entries
Comment 3 Matthias Clasen 2011-03-26 21:07:29 UTC 
Works fine here with 
gnome-system-monitor-2.99.3-1.fc15.x86_64
Comment 4 Chris Kühl 2011-03-27 11:06:12 UTC 
(In reply to comment #3)
> Works fine here with 
> gnome-system-monitor-2.99.3-1.fc15.x86_64

Matthias, how many CPUs do you have? I'm pretty sure this is a valid bug when more than 4 logical CPUs are detected. Unfortunately, I only have 4 CPUs (2 cores  w/ hyperthreading) to test with.
Comment 5 Matthias Clasen 2011-03-28 01:05:12 UTC 
Yes, you are correct.
Comment 6 Chris Kühl 2011-04-04 08:22:52 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.