Bug 1170280

Summary: [abrt] mate-panel: rate_limiter_free(): mate-panel killed by SIGSEGV
Product: [Fedora] Fedora Reporter: Steve Meisner <smeisner>
Component: glib2Assignee: Matthias Clasen <mclasen>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 20CC: dan.mashal, jharriga, mclasen, raveit65.sun, stefano
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
URL: https://retrace.fedoraproject.org/faf/reports/bthash/a865034d98bbb1995bdfcdcb297fbe68482e8b25
Whiteboard: abrt_hash:fe25c86a28eddff04808ff574773544f0fe547fa
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-04-09 02:16:11 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: exploitable
none
File: limits
none
File: maps
none
File: open_fds
none
File: proc_pid_status
none
File: var_log_messages none

Description Steve Meisner 2014-12-03 16:37:31 UTC 
Description of problem:
Performing a yum update (using yumex) at the time.

Version-Release number of selected component:
mate-panel-1.8.1-1.fc20

Additional info:
reporter:       libreport-2.2.3
backtrace_rating: 4
cmdline:        mate-panel
crash_function: rate_limiter_free
executable:     /usr/bin/mate-panel
kernel:         3.17.3-200.fc20.x86_64
runlevel:       N 5
type:           CCpp
uid:            1000

Truncated backtrace:
Thread no. 1 (5 frames)
 #0 rate_limiter_free at gfilemonitor.c:160
 #1 g_hash_table_foreach_remove_or_steal at ghash.c:1412
 #2 g_hash_table_foreach_remove at ghash.c:1456
 #3 rate_limiter_timeout at gfilemonitor.c:573
 #9 gtk_main at gtkmain.c:1257
Comment 1 Steve Meisner 2014-12-03 16:37:33 UTC 
Created attachment 964203 [details]
File: backtrace
Comment 2 Steve Meisner 2014-12-03 16:37:34 UTC 
Created attachment 964204 [details]
File: cgroup
Comment 3 Steve Meisner 2014-12-03 16:37:35 UTC 
Created attachment 964205 [details]
File: core_backtrace
Comment 4 Steve Meisner 2014-12-03 16:37:36 UTC 
Created attachment 964206 [details]
File: dso_list
Comment 5 Steve Meisner 2014-12-03 16:37:36 UTC 
Created attachment 964207 [details]
File: environ
Comment 6 Steve Meisner 2014-12-03 16:37:37 UTC 
Created attachment 964208 [details]
File: exploitable
Comment 7 Steve Meisner 2014-12-03 16:37:38 UTC 
Created attachment 964209 [details]
File: limits
Comment 8 Steve Meisner 2014-12-03 16:37:39 UTC 
Created attachment 964210 [details]
File: maps
Comment 9 Steve Meisner 2014-12-03 16:37:40 UTC 
Created attachment 964211 [details]
File: open_fds
Comment 10 Steve Meisner 2014-12-03 16:37:40 UTC 
Created attachment 964212 [details]
File: proc_pid_status
Comment 11 Steve Meisner 2014-12-03 16:37:41 UTC 
Created attachment 964213 [details]
File: var_log_messages
Comment 12 Wolfgang Ulbrich 2015-02-01 23:49:01 UTC 
Can you describe a little more detailed what happend?
Did this issue occurs frequently ?
... my crystal ball is dead......
Comment 13 Matthias Clasen 2015-04-09 02:16:11 UTC 

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