Bug 962494

Summary: [abrt] mate-system-monitor-1.5.1-1.fc18: main: Process /usr/bin/mate-system-monitor was killed by signal 5 (SIGTRAP)
Product: [Fedora] Fedora Reporter: bizar <yo_bizar>
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: 18CC: dan.mashal, raveit65.sun, rdieter
Target Milestone: ---   
Target Release: ---   
Hardware: i686   
OS: Unspecified   
Whiteboard: abrt_hash:2388fb6b5a1c2a54f664ee2ed4fb43cdf8f67bee
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-07-06 18:58:59 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

Description bizar 2013-05-13 16:33:20 UTC 
Version-Release number of selected component:
mate-system-monitor-1.5.1-1.fc18

Additional info:
backtrace_rating: 4
cmdline:        mate-system-monitor
crash_function: main
executable:     /usr/bin/mate-system-monitor
kernel:         3.8.11-200.fc18.i686.PAE
uid:            1000
ureports_counter: 1
var_log_messages: May 13 19:00:42 bizare abrt[25879]: Saved core dump of pid 25878 (/usr/bin/mate-system-monitor) to /var/tmp/abrt/ccpp-2013-05-13-19:00:41-25878 (36356096 bytes)
xsession_errors: 

Truncated backtrace:
Thread no. 1 (0 frames)
Comment 1 bizar 2013-05-13 16:33:23 UTC 
Created attachment 747286 [details]
File: backtrace
Comment 2 bizar 2013-05-13 16:33:25 UTC 
Created attachment 747287 [details]
File: cgroup
Comment 3 bizar 2013-05-13 16:33:27 UTC 
Created attachment 747288 [details]
File: core_backtrace
Comment 4 bizar 2013-05-13 16:33:29 UTC 
Created attachment 747289 [details]
File: dso_list
Comment 5 bizar 2013-05-13 16:33:32 UTC 
Created attachment 747290 [details]
File: environ
Comment 6 bizar 2013-05-13 16:33:34 UTC 
Created attachment 747291 [details]
File: limits
Comment 7 bizar 2013-05-13 16:33:36 UTC 
Created attachment 747292 [details]
File: maps
Comment 8 bizar 2013-05-13 16:33:39 UTC 
Created attachment 747293 [details]
File: open_fds
Comment 9 bizar 2013-05-13 16:33:41 UTC 
Created attachment 747294 [details]
File: proc_pid_status
Comment 10 Wolfgang Ulbrich 2013-06-29 14:23:35 UTC 
Can you describe a little more detailed what's happend?
Does this error ocours frequently?