Bug 1028952

Summary: [abrt] mate-control-center-1.6.1-2.fc20: Process /usr/bin/mate-display-properties was killed by signal 11 (SIGSEGV)
Product: [Fedora] Fedora Reporter: danny_zhoujian <zhoujian8585169>
Component: mate-control-centerAssignee: Dan Mashal <dan.mashal>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 20CC: dan.mashal, dcharlespyle, fedora, rdieter, ricatiecher, samtygier, stefano, tombouwman, uraharakisuke153, Wilhelm.Buchmueller, xmach01
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
URL: https://retrace.fedoraproject.org/faf/reports/bthash/81b6271f3aa1a73c2dcab9885cebc309b91fa1ae
Whiteboard: abrt_hash:3a814a937c52256fd2f2841013fbe867daee5649
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-11-11 13:32:33 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
Core_Backtrace from crash none

Description danny_zhoujian 2013-11-11 10:29:01 UTC 
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
Comment 1 danny_zhoujian 2013-11-11 10:29:13 UTC 
Created attachment 822344 [details]
File: backtrace
Comment 2 danny_zhoujian 2013-11-11 10:29:19 UTC 
Created attachment 822345 [details]
File: cgroup
Comment 3 danny_zhoujian 2013-11-11 10:29:23 UTC 
Created attachment 822346 [details]
File: core_backtrace
Comment 4 danny_zhoujian 2013-11-11 10:29:28 UTC 
Created attachment 822347 [details]
File: dso_list
Comment 5 danny_zhoujian 2013-11-11 10:29:32 UTC 
Created attachment 822348 [details]
File: environ
Comment 6 danny_zhoujian 2013-11-11 10:29:36 UTC 
Created attachment 822349 [details]
File: exploitable
Comment 7 danny_zhoujian 2013-11-11 10:29:40 UTC 
Created attachment 822350 [details]
File: limits
Comment 8 danny_zhoujian 2013-11-11 10:29:45 UTC 
Created attachment 822351 [details]
File: maps
Comment 9 danny_zhoujian 2013-11-11 10:29:48 UTC 
Created attachment 822352 [details]
File: open_fds
Comment 10 danny_zhoujian 2013-11-11 10:29:52 UTC 
Created attachment 822353 [details]
File: proc_pid_status
Comment 11 danny_zhoujian 2013-11-11 10:29:57 UTC 
Created attachment 822354 [details]
File: var_log_messages
Comment 12 D. Charles Pyle 2014-01-22 17:37:25 UTC 
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.
Comment 13 D. Charles Pyle 2014-01-22 17:40:42 UTC 
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.
Comment 14 Sam Tygier 2014-08-28 12:26:17 UTC 
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
Comment 15 Wolfgang Ulbrich 2014-08-28 14:56:12 UTC 

*** This bug has been marked as a duplicate of bug 1062796 ***