Bug 1153480

Summary: [abrt] mate-settings-daemon: on_slow_keys_checkbutton_toggled(): mate-settings-daemon killed by SIGSEGV
Product: [Fedora] Fedora Reporter: Wilhelm.Buchmueller
Component: mate-settings-daemonAssignee: Wolfgang Ulbrich <raveit65.sun>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 20CC: dan.mashal, raveit65.sun, samtygier, stefano
Target Milestone: ---   
Target Release: ---   
Hardware: i686   
OS: Unspecified   
URL: https://retrace.fedoraproject.org/faf/reports/bthash/db5413bbe5c4fd1708c61d2a8dfdad6b047fa526
Whiteboard: abrt_hash:4490f0438066dcbdf71d9b3970e441daa6584015
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-06-29 22:55:22 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 Wilhelm.Buchmueller 2014-10-16 05:24:04 UTC 
Version-Release number of selected component:
mate-settings-daemon-1.8.1-2.fc20

Additional info:
reporter:       libreport-2.2.3
backtrace_rating: 4
cmdline:        /usr/libexec/mate-settings-daemon
crash_function: on_slow_keys_checkbutton_toggled
executable:     /usr/libexec/mate-settings-daemon
kernel:         3.16.3-200.fc20.i686+PAE
runlevel:       N 5
type:           CCpp
uid:            1000

Truncated backtrace:
Thread no. 1 (10 frames)
 #0 on_slow_keys_checkbutton_toggled at /usr/lib/mate-settings-daemon/liba11y-keyboard.so
 #1 g_cclosure_marshal_VOID__VOIDv at gmarshal.c:115
 #2 _g_closure_invoke_va at gclosure.c:840
 #5 gtk_toggle_button_toggled at gtktogglebutton.c:365
 #6 gtk_toggle_button_clicked at gtktogglebutton.c:498
 #7 g_cclosure_marshal_VOID__VOIDv at gmarshal.c:115
 #8 g_type_class_meta_marshalv at gclosure.c:997
 #9 _g_closure_invoke_va at gclosure.c:840
 #12 gtk_button_clicked at gtkbutton.c:1115
 #13 ui_set_slow_keys at /usr/lib/mate-settings-daemon/liba11y-keyboard.so
Comment 1 Wilhelm.Buchmueller 2014-10-16 05:24:08 UTC 
Created attachment 947426 [details]
File: backtrace
Comment 2 Wilhelm.Buchmueller 2014-10-16 05:24:09 UTC 
Created attachment 947427 [details]
File: cgroup
Comment 3 Wilhelm.Buchmueller 2014-10-16 05:24:10 UTC 
Created attachment 947428 [details]
File: core_backtrace
Comment 4 Wilhelm.Buchmueller 2014-10-16 05:24:11 UTC 
Created attachment 947429 [details]
File: dso_list
Comment 5 Wilhelm.Buchmueller 2014-10-16 05:24:12 UTC 
Created attachment 947430 [details]
File: environ
Comment 6 Wilhelm.Buchmueller 2014-10-16 05:24:13 UTC 
Created attachment 947431 [details]
File: exploitable
Comment 7 Wilhelm.Buchmueller 2014-10-16 05:24:15 UTC 
Created attachment 947432 [details]
File: limits
Comment 8 Wilhelm.Buchmueller 2014-10-16 05:24:16 UTC 
Created attachment 947433 [details]
File: maps
Comment 9 Wilhelm.Buchmueller 2014-10-16 05:24:17 UTC 
Created attachment 947434 [details]
File: open_fds
Comment 10 Wilhelm.Buchmueller 2014-10-16 05:24:19 UTC 
Created attachment 947435 [details]
File: proc_pid_status
Comment 11 Wilhelm.Buchmueller 2014-10-16 05:24:20 UTC 
Created attachment 947436 [details]
File: var_log_messages
Comment 12 Wolfgang Ulbrich 2014-10-22 22:45:02 UTC 
Can you describe a little more detailed what happend?
Did this issue occurs frequently ?
Comment 13 Sam Tygier 2014-11-10 14:23:03 UTC 
I got this at boot time.
Comment 14 Sam Tygier 2014-12-15 13:08:29 UTC 
Go it again today. Again just a message at after booting saying that it had crashed. Now on version mate-settings-daemon-1.8.2-1.fc20.x86_64. Seems fairly rare to me, less than once a month, but I generally only reboot for kernel updates.
Comment 15 Fedora End Of Life 2015-05-29 13:05:48 UTC 
This message is a reminder that Fedora 20 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 20. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as EOL if it remains open with a Fedora  'version'
of '20'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 20 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.
Comment 16 Wolfgang Ulbrich 2015-05-31 15:28:38 UTC 
Test for M. Schwendt :)
Comment 17 Wolfgang Ulbrich 2015-05-31 15:30:27 UTC 
Test for M. Schwendt :)
Comment 18 Wilhelm.Buchmueller 2015-06-01 08:06:00 UTC 
(In reply to Wolfgang Ulbrich from comment #17)
> Test for M. Schwendt :)

Switching frequency 30/25/24 Hz on external 1920x1080 HDMI Monitor not possible for me now. 
No Monitor available. 

Can someone else test this for me?
Comment 19 Fedora Admin XMLRPC Client 2015-06-17 22:28:54 UTC 
This package has changed ownership in the Fedora Package Database.  Reassigning to the new owner of this component.
Comment 20 Fedora End Of Life 2015-06-29 22:55:22 UTC 
Fedora 20 changed to end-of-life (EOL) status on 2015-06-23. Fedora 20 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.