Bug 1085135

Summary: [abrt] mate-screensaver: rate_limiter_free(): mate-screensaver killed by SIGSEGV
Product: [Fedora] Fedora Reporter: moroveno30
Component: mate-screensaverAssignee: 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, stefano
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
URL: https://retrace.fedoraproject.org/faf/reports/bthash/92aa5c3592555c15d5b8688b4ccc10cb3284ada4
Whiteboard: abrt_hash:29b6c83267734a0e029e63d09941ed3cd19a98b7
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-06-21 16:11:01 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 moroveno30 2014-04-07 23:24:27 UTC 
Version-Release number of selected component:
mate-screensaver-1.6.2-1.fc20

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

Truncated backtrace:
Thread no. 1 (10 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 update_rate_limiter_timeout at gfilemonitor.c:625
 #4 g_file_monitor_emit_event at gfilemonitor.c:689
 #5 ih_event_callback at inotify-helper.c:196
 #6 ip_event_dispatch at inotify-path.c:493
 #7 ip_event_callback at inotify-path.c:629
 #8 ik_process_eq_callback at inotify-kernel.c:579
 #13 g_main_context_iteration at gmain.c:3774
Comment 1 moroveno30 2014-04-07 23:24:31 UTC 
Created attachment 883780 [details]
File: backtrace
Comment 2 moroveno30 2014-04-07 23:24:33 UTC 
Created attachment 883781 [details]
File: cgroup
Comment 3 moroveno30 2014-04-07 23:24:34 UTC 
Created attachment 883782 [details]
File: core_backtrace
Comment 4 moroveno30 2014-04-07 23:24:37 UTC 
Created attachment 883783 [details]
File: dso_list
Comment 5 moroveno30 2014-04-07 23:24:43 UTC 
Created attachment 883784 [details]
File: environ
Comment 6 moroveno30 2014-04-07 23:24:44 UTC 
Created attachment 883785 [details]
File: exploitable
Comment 7 moroveno30 2014-04-07 23:24:51 UTC 
Created attachment 883786 [details]
File: limits
Comment 8 moroveno30 2014-04-07 23:24:54 UTC 
Created attachment 883787 [details]
File: maps
Comment 9 moroveno30 2014-04-07 23:24:57 UTC 
Created attachment 883788 [details]
File: open_fds
Comment 10 moroveno30 2014-04-07 23:25:02 UTC 
Created attachment 883789 [details]
File: proc_pid_status
Comment 11 moroveno30 2014-04-07 23:25:04 UTC 
Created attachment 883790 [details]
File: var_log_messages
Comment 12 Wolfgang Ulbrich 2014-04-19 23:11:54 UTC 
Can you describe a little more detailed what happend?
Did this issue occurs frequently ?
Comment 13 Wolfgang Ulbrich 2014-06-21 16:11:01 UTC 
no user response !