Bug 690696 - Can't open gnome-system-monitor on quad core i7
Summary: Can't open gnome-system-monitor on quad core i7
Keywords:
Status: CLOSED DUPLICATE of bug 684806
Alias: None
Product: Fedora
Classification: Fedora
Component: gnome-system-monitor
Version: 15
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Søren Sandmann Pedersen
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-03-25 04:28 UTC by Diego Fernandez
Modified: 2014-06-18 09:14 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2011-03-26 21:48:02 UTC
Type: ---
Embargoed:


Attachments (Terms of Use)

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 ***


Note You need to log in before you can comment on or make changes to this bug.