Description of problem: open or close VGA input output Version-Release number of selected component: mate-control-center-1.6.1-2.fc20 Additional info: reporter: libreport-2.1.9 backtrace_rating: 3 cmdline: mate-display-properties executable: /usr/bin/mate-display-properties kernel: 3.11.6-301.fc20.x86_64 runlevel: N 5 type: CCpp uid: 1000 Truncated backtrace: Thread no. 1 (6 frames) #0 ?? #1 gdk_event_apply_filters at gdkevents-x11.c:356 #2 gdk_event_translate at gdkevents-x11.c:1052 #3 _gdk_events_queue at gdkevents-x11.c:2336 #9 gtk_dialog_run at gtkdialog.c:1094 #10 run_application at xrandr-capplet.c:2520 Potential duplicate: bug 879663
Created attachment 822344 [details] File: backtrace
Created attachment 822345 [details] File: cgroup
Created attachment 822346 [details] File: core_backtrace
Created attachment 822347 [details] File: dso_list
Created attachment 822348 [details] File: environ
Created attachment 822349 [details] File: exploitable
Created attachment 822350 [details] File: limits
Created attachment 822351 [details] File: maps
Created attachment 822352 [details] File: open_fds
Created attachment 822353 [details] File: proc_pid_status
Created attachment 822354 [details] File: var_log_messages
Just happened to me. I had just finished adjusting monitor refresh rate settings when the crash occurred. Abrt, however, would not let me report anything because it had already been reported. Executable that caused the crash was: /usr/bin/mate-display-properties Coredump and backtrace to follow.
Created attachment 853968 [details] Core_Backtrace from crash Attached to this post is the backtrace. I tried but I could not send up the coredump, however, because it was too large.
ABRT brought me here, but looks like the current open report is Bug 1062796 and upstream as https://github.com/mate-desktop/mate-control-center/issues/48
*** This bug has been marked as a duplicate of bug 1062796 ***