Bug 688861 - [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)
Summary: [abrt] gnome-system-monitor-2.99.1-1.fc15: g_settings_schema_get_value: Proce...
Keywords:
Status: CLOSED DUPLICATE of bug 684806
Alias: None
Product: Fedora
Classification: Fedora
Component: gnome-system-monitor
Version: 15
Hardware: x86_64
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Søren Sandmann Pedersen
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard: abrt_hash:e452383b6b9d2fa67b83c3a079c...
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-03-18 09:55 UTC by chi chien lin
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:16 UTC
Type: ---
Embargoed:

Attachments (Terms of Use)
File: backtrace (20.03 KB, text/plain)
2011-03-18 09:55 UTC, chi chien lin 		no flags Details
View All

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 ***
Note You need to log in before you can comment on or make changes to this bug.