Bug 688861

Summary: [abrt] gnome-system-monitor-2.99.1-1.fc15: g_settings_schema_get_value: Process /usr/bin/gnome-system-monitor was killed by signal 6 (SIGABRT)
Product: [Fedora] Fedora Reporter: chi chien lin <chi0541>
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: x86_64   
OS: Unspecified   
Whiteboard: abrt_hash:e452383b6b9d2fa67b83c3a079c3b1fa047381f4
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-03-26 21:48:16 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:
Attachments:
Description Flags
File: backtrace none

Description chi chien lin 2011-03-18 09:55:09 UTC 
abrt version: 1.1.17
architecture: x86_64
Attached file: backtrace, 20507 bytes
cmdline: gnome-system-monitor
component: gnome-system-monitor
Attached file: coredump, 11878400 bytes
crash_function: g_settings_schema_get_value
executable: /usr/bin/gnome-system-monitor
kernel: 2.6.38-1.fc15.x86_64
package: gnome-system-monitor-2.99.1-1.fc15
rating: 4
reason: Process /usr/bin/gnome-system-monitor was killed by signal 6 (SIGABRT)
release: Fedora release 15 (Lovelock)
How to reproduce: 1. ?????
time: 1300442131
uid: 0
Comment 1 chi chien lin 2011-03-18 09:55:12 UTC 
Created attachment 486194 [details]
File: backtrace
Comment 2 chi chien lin 2011-03-21 02:38:40 UTC 
Package: gnome-system-monitor-2.99.1-1.fc15
Architecture: x86_64
OS Release: Fedora release 15 (Lovelock)


How to reproduce
-----
1. gnome-system-monitor error.
Comment 3 chi chien lin 2011-03-21 08:45:28 UTC 
Package: gnome-system-monitor-2.99.1-1.fc15
Architecture: x86_64
OS Release: Fedora release 15 (Lovelock)


How to reproduce
-----
1. error.
Comment 4 Paul W. Frields 2011-03-26 21:48:16 UTC 

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