Bug 1304369

Summary: [abrt] mate-control-center: g_type_check_instance_cast(): mate-display-properties killed by SIGSEGV
Product: [Fedora] Fedora Reporter: Peter Gervase <pgervase>
Component: mate-control-centerAssignee: Wolfgang Ulbrich <fedora>
Status: CLOSED CURRENTRELEASE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 24CC: fedora, rdieter, stefano
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
URL: https://retrace.fedoraproject.org/faf/reports/bthash/ba422570e5c267262840cb9d1398c04a83c356ce
Whiteboard: abrt_hash:93c280c17452ad5710e0a1426b2717424f06ac08;
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-05-01 17:20:53 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
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: mountinfo
none
File: namespaces
none
File: open_fds
none
File: proc_pid_status
none
File: var_log_messages none

Description Peter Gervase 2016-02-03 12:37:31 UTC
Description of problem:
Because the suspend in Mate doesn't work, I use a script to suspend my system at night:
#!/bin/bash
/usr/bin/dbus-send --system --print-reply   --dest="org.freedesktop.login1"   /org/freedesktop/login1 org.freedesktop.login1.Manager.Suspend boolean:true

Usually, it works fine. This morning, I hit the power button on my laptop to unsuspend it and one of my external monitors did not start. I went to System and then Displays. I tried hitting just the apply button since the monitors were all detected, but that didn't bring back the second external monitor. It was just a few seconds after this that the program crashed, but I'm not 100% sure on exactly where I clicked, if anywhere. It may have been to try unchecking one of the monitors or maybe hitting apply again. 



Version-Release number of selected component:
mate-control-center-1.12.1-2.fc24

Additional info:
reporter:       libreport-2.6.3
backtrace_rating: 4
cmdline:        mate-display-properties
crash_function: g_type_check_instance_cast
executable:     /usr/bin/mate-display-properties
global_pid:     1029
kernel:         4.5.0-0.rc0.git1.1.fc24.x86_64
runlevel:       N 5
type:           CCpp
uid:            1000

Truncated backtrace:
Thread no. 1 (10 frames)
 #0 g_type_check_instance_cast at gtype.c:4065
 #1 on_output_event at xrandr-capplet.c:1575
 #2 emit_input at scrollarea.c:1016
 #3 process_event at scrollarea.c:1066
 #4 process_gdk_event at scrollarea.c:1103
 #5 foo_scroll_area_motion at scrollarea.c:1134
 #6 _gtk_marshal_BOOLEAN__BOXED at gtkmarshalers.c:86
 #11 gtk_widget_event_internal at gtkwidget.c:5017
 #12 gtk_widget_event at gtkwidget.c:4814
 #13 gtk_propagate_event at gtkmain.c:2501

Comment 1 Peter Gervase 2016-02-03 12:37:37 UTC
Created attachment 1120746 [details]
File: backtrace

Comment 2 Peter Gervase 2016-02-03 12:37:38 UTC
Created attachment 1120747 [details]
File: cgroup

Comment 3 Peter Gervase 2016-02-03 12:37:39 UTC
Created attachment 1120748 [details]
File: core_backtrace

Comment 4 Peter Gervase 2016-02-03 12:37:40 UTC
Created attachment 1120749 [details]
File: dso_list

Comment 5 Peter Gervase 2016-02-03 12:37:41 UTC
Created attachment 1120750 [details]
File: environ

Comment 6 Peter Gervase 2016-02-03 12:37:42 UTC
Created attachment 1120751 [details]
File: exploitable

Comment 7 Peter Gervase 2016-02-03 12:37:43 UTC
Created attachment 1120752 [details]
File: limits

Comment 8 Peter Gervase 2016-02-03 12:37:45 UTC
Created attachment 1120753 [details]
File: maps

Comment 9 Peter Gervase 2016-02-03 12:37:46 UTC
Created attachment 1120754 [details]
File: mountinfo

Comment 10 Peter Gervase 2016-02-03 12:37:47 UTC
Created attachment 1120755 [details]
File: namespaces

Comment 11 Peter Gervase 2016-02-03 12:37:48 UTC
Created attachment 1120756 [details]
File: open_fds

Comment 12 Peter Gervase 2016-02-03 12:37:49 UTC
Created attachment 1120757 [details]
File: proc_pid_status

Comment 13 Peter Gervase 2016-02-03 12:37:50 UTC
Created attachment 1120758 [details]
File: var_log_messages

Comment 14 Jan Kurik 2016-02-24 14:24:00 UTC
This bug appears to have been reported against 'rawhide' during the Fedora 24 development cycle.
Changing version to '24'.

More information and reason for this action is here:
https://fedoraproject.org/wiki/Fedora_Program_Management/HouseKeeping/Fedora24#Rawhide_Rebase

Comment 15 Wolfgang Ulbrich 2016-04-14 10:03:17 UTC
Hmm, that suspend does not work in f24 is new for me, but i do not install f24 on my notebook before beta release, so i can't reproduce it.
Is the other issue reproducible?

Comment 16 Wolfgang Ulbrich 2016-04-14 10:04:33 UTC
Btw. on normal box i see no crash with mate-display-properties.

Comment 17 Wolfgang Ulbrich 2016-08-13 11:13:52 UTC
On my notebook works suspend very well.
Is the issue still exists?

Comment 18 Wolfgang Ulbrich 2017-05-01 17:20:53 UTC
No answer from reporter!

Comment 19 Peter Gervase 2017-05-02 19:25:42 UTC
(In reply to Wolfgang Ulbrich from comment #17)
> On my notebook works suspend very well.
> Is the issue still exists?

I'm sorry. I didn't see this post before. I don't remember what happened with mate, but I'm back using kde.