Bug 1051253

Summary: [abrt] mate-settings-daemon: grab_key_unsafe(): mate-settings-daemon killed by SIGSEGV
Product: [Fedora] Fedora Reporter: Pavel Mlčoch <pavkamlc>
Component: mate-settings-daemonAssignee: 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, stefano
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
URL: https://retrace.fedoraproject.org/faf/reports/bthash/8e10621ef5f2742d9149c8877e1e94012abe1146
Whiteboard: abrt_hash:70b09227fbd711a52ceb27d63079809df9d085cd
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-04-02 15:26:27 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 Pavel Mlčoch 2014-01-09 22:38:00 UTC 
Version-Release number of selected component:
mate-settings-daemon-1.6.2-2.fc20

Additional info:
reporter:       libreport-2.1.10
backtrace_rating: 4
cmdline:        /usr/libexec/mate-settings-daemon
crash_function: grab_key_unsafe
executable:     /usr/libexec/mate-settings-daemon
kernel:         3.12.6-300.fc20.x86_64
runlevel:       N 5
type:           CCpp
uid:            1000

Truncated backtrace:
Thread no. 1 (9 frames)
 #0 grab_key_unsafe at msd-keygrab.c:154
 #1 binding_unregister_keys at msd-keybindings-manager.c:327
 #2 bindings_callback at msd-keybindings-manager.c:533
 #3 ffi_call_unix64 at ../src/x86/unix64.S:76
 #4 ffi_call at ../src/x86/ffi64.c:522
 #5 g_cclosure_marshal_generic_va at gclosure.c:1550
 #6 _g_closure_invoke_va at gclosure.c:840
 #9 dconf_client_dispatch_change_signal at dconf-client.c:150
 #14 gtk_main at gtkmain.c:1257
Comment 1 Pavel Mlčoch 2014-01-09 22:38:39 UTC 
Created attachment 847888 [details]
File: backtrace
Comment 2 Pavel Mlčoch 2014-01-09 22:38:53 UTC 
Created attachment 847889 [details]
File: cgroup
Comment 3 Pavel Mlčoch 2014-01-09 22:39:25 UTC 
Created attachment 847890 [details]
File: core_backtrace
Comment 4 Pavel Mlčoch 2014-01-09 22:39:49 UTC 
Created attachment 847891 [details]
File: dso_list
Comment 5 Pavel Mlčoch 2014-01-09 22:40:04 UTC 
Created attachment 847892 [details]
File: environ
Comment 6 Pavel Mlčoch 2014-01-09 22:40:17 UTC 
Created attachment 847893 [details]
File: exploitable
Comment 7 Pavel Mlčoch 2014-01-09 22:40:35 UTC 
Created attachment 847894 [details]
File: limits
Comment 8 Pavel Mlčoch 2014-01-09 22:40:48 UTC 
Created attachment 847895 [details]
File: maps
Comment 9 Pavel Mlčoch 2014-01-09 22:40:51 UTC 
Created attachment 847896 [details]
File: open_fds
Comment 10 Pavel Mlčoch 2014-01-09 22:40:56 UTC 
Created attachment 847897 [details]
File: proc_pid_status
Comment 11 Pavel Mlčoch 2014-01-09 22:41:00 UTC 
Created attachment 847898 [details]
File: var_log_messages
Comment 12 Wolfgang Ulbrich 2014-02-15 14:38:02 UTC 
Can you describe a little more detailed what happend?
Did this issue occurs frequently ?
Comment 13 Pavel Mlčoch 2014-02-15 15:29:45 UTC 
It occurs maybe twice and in background, I don't know when It crash.
Comment 14 Wolfgang Ulbrich 2014-02-23 20:49:36 UTC 
Ok, not enogh information to forward the issue to upstream, i will left the issue a while open, feel free to report here if it happens again.
Comment 15 Wolfgang Ulbrich 2014-04-02 15:26:27 UTC 
Feel free to post here if it happens again