Bug 690696

Summary: Can't open gnome-system-monitor on quad core i7
Product: [Fedora] Fedora Reporter: Diego Fernandez <aiguo.fernandez>
Component: gnome-system-monitorAssignee: Søren Sandmann Pedersen <sandmann>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 15CC: kem, sandmann, stickster
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-03-26 21:48:02 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Diego Fernandez 2011-03-25 04:28:16 UTC 
Description of problem:
When I try to run gnome-system-monitor I get the 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)"

Version-Release number of selected component (if applicable):
2.99.2-1

How reproducible:
Every time

Steps to Reproduce:
1. try to run
  
Actual results:
Error and crash.

Expected results:
Open normally

Additional info:
"$ lscpu 
Architecture:          x86_64
CPU op-mode(s):        32-bit, 64-bit
Byte Order:            Little Endian
CPU(s):                8
On-line CPU(s) list:   0-7
Thread(s) per core:    2
Core(s) per socket:    4
CPU socket(s):         1
NUMA node(s):          1
Vendor ID:             GenuineIntel
CPU family:            6
Model:                 42
Stepping:              7
CPU MHz:               800.000
BogoMIPS:              4390.04
Virtualization:        VT-x
L1d cache:             32K
L1i cache:             32K
L2 cache:              256K
L3 cache:              6144K
NUMA node0 CPU(s):     0-7"
Comment 1 Paul W. Frields 2011-03-26 21:48:02 UTC 

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