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
Created attachment 947426 [details] File: backtrace
Created attachment 947427 [details] File: cgroup
Created attachment 947428 [details] File: core_backtrace
Created attachment 947429 [details] File: dso_list
Created attachment 947430 [details] File: environ
Created attachment 947431 [details] File: exploitable
Created attachment 947432 [details] File: limits
Created attachment 947433 [details] File: maps
Created attachment 947434 [details] File: open_fds
Created attachment 947435 [details] File: proc_pid_status
Created attachment 947436 [details] File: var_log_messages
Can you describe a little more detailed what happend? Did this issue occurs frequently ?
I got this at boot time.
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.
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.
Test for M. Schwendt :)
(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?
This package has changed ownership in the Fedora Package Database. Reassigning to the new owner of this component.
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.