Bug 1093919

Summary: [abrt] mate-system-monitor: _g_log_abort(): mate-system-monitor killed by SIGABRT
Product: [Fedora] Fedora Reporter: Bob <bobkaiser1>
Component: mate-system-monitorAssignee: Dan Mashal <dan.mashal>
Status: CLOSED INSUFFICIENT_DATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 20CC: dan.mashal, raveit65.sun, rdieter
Target Milestone: ---   
Target Release: ---   
Hardware: i686   
OS: Unspecified   
URL: https://retrace.fedoraproject.org/faf/reports/bthash/5c5ee73ceec396652ff3e0aeaecd49891cb30aff
Whiteboard: abrt_hash:1e1def8263b8b62e37544731b6e7ffb5fd565b46
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-07-09 18:04:47 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
File: cgroup
none
File: core_backtrace
none
File: dso_list
none
File: environ
none
File: limits
none
File: maps
none
File: open_fds
none
File: proc_pid_status
none
File: var_log_messages none

Description Bob 2014-05-03 09:45:16 UTC 
Description of problem:
System went to sleep after I unplugged AC power and went on battery power.

Version-Release number of selected component:
mate-system-monitor-1.6.1-1.fc20

Additional info:
reporter:       libreport-2.2.2
backtrace_rating: 4
cmdline:        mate-system-monitor
crash_function: _g_log_abort
executable:     /usr/bin/mate-system-monitor
kernel:         3.13.10-200.fc20.i686
runlevel:       N 5
type:           CCpp
uid:            1000

Truncated backtrace:
Thread no. 1 (7 frames)
 #3 _g_log_abort at gmessages.c:255
 #6 net_scale at load-graph.cpp:419
 #7 get_net at load-graph.cpp:525
 #8 load_graph_update at load-graph.cpp:553
 #14 gtk_main at gtkmain.c:1257
 #15 Gtk::Main::run_impl at main.cc:534
 #16 Gtk::Main::run at main.cc:477
Comment 1 Bob 2014-05-03 09:45:25 UTC 
Created attachment 892105 [details]
File: backtrace
Comment 2 Bob 2014-05-03 09:45:29 UTC 
Created attachment 892106 [details]
File: cgroup
Comment 3 Bob 2014-05-03 09:45:34 UTC 
Created attachment 892107 [details]
File: core_backtrace
Comment 4 Bob 2014-05-03 09:45:38 UTC 
Created attachment 892108 [details]
File: dso_list
Comment 5 Bob 2014-05-03 09:45:43 UTC 
Created attachment 892109 [details]
File: environ
Comment 6 Bob 2014-05-03 09:45:47 UTC 
Created attachment 892110 [details]
File: limits
Comment 7 Bob 2014-05-03 09:45:52 UTC 
Created attachment 892111 [details]
File: maps
Comment 8 Bob 2014-05-03 09:45:56 UTC 
Created attachment 892112 [details]
File: open_fds
Comment 9 Bob 2014-05-03 09:46:00 UTC 
Created attachment 892113 [details]
File: proc_pid_status
Comment 10 Bob 2014-05-03 09:46:10 UTC 
Created attachment 892114 [details]
File: var_log_messages
Comment 11 Wolfgang Ulbrich 2014-06-21 16:03:33 UTC 
Does this issue exists if no hybernate state is used?
When this issue occours? before or after hybernate.
Sorry, without a detailed description and steps to reproduce this report is useless.
Comment 12 Wolfgang Ulbrich 2014-07-09 18:04:47 UTC 
No answer from reporter!