Bug 1156030

Summary: [abrt] mate-settings-daemon: on_screen_size_changed(): mate-settings-daemon killed by SIGSEGV
Product: [Fedora] Fedora Reporter: Jozef Mlich <jmlich>
Component: mate-settings-daemonAssignee: Dan Mashal <dan.mashal>
Status: CLOSED DUPLICATE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 21CC: dan.mashal, fedora, hhorak, stefano
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
URL: https://retrace.fedoraproject.org/faf/reports/bthash/9b76b00a7b38b079db98b476ba590ba72d72774d
Whiteboard: abrt_hash:947a161ab1a4f616eb609b7e9ec1fb749f67ff7f
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-12-01 17:05:29 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: audit.txt
none
File: backtrace
none
File: cgroup
none
File: core_backtrace
none
File: dso_list
none
File: environ
none
File: exploitable
none
File: journal.txt
none
File: limits
none
File: maps
none
File: open_fds
none
File: proc_pid_status
none
File: var_log_messages none

Description Jozef Mlich 2014-10-23 12:42:18 UTC 
Version-Release number of selected component:
mate-settings-daemon-1.8.2-2.fc21

Additional info:
reporter:       libreport-2.3.0
backtrace_rating: 4
cmdline:        /usr/libexec/mate-settings-daemon
crash_function: on_screen_size_changed
executable:     /usr/libexec/mate-settings-daemon
kernel:         3.17.1-302.fc21.x86_64+debug
runlevel:       N 5
type:           CCpp
uid:            21446

Truncated backtrace:
Thread no. 1 (6 frames)
 #0 on_screen_size_changed at msd-background-manager.c:272
 #1 _g_closure_invoke_va at gclosure.c:831
 #3 g_signal_emit_by_name at gsignal.c:3405
 #4 gdk_event_translate at gdkevents-x11.c:2152
 #5 _gdk_events_queue at gdkevents-x11.c:2336
 #11 gtk_main at gtkmain.c:1257

Potential duplicate: bug 920960
Comment 1 Jozef Mlich 2014-10-23 12:42:23 UTC 
Created attachment 949851 [details]
File: audit.txt
Comment 2 Jozef Mlich 2014-10-23 12:42:25 UTC 
Created attachment 949852 [details]
File: backtrace
Comment 3 Jozef Mlich 2014-10-23 12:42:26 UTC 
Created attachment 949853 [details]
File: cgroup
Comment 4 Jozef Mlich 2014-10-23 12:42:28 UTC 
Created attachment 949854 [details]
File: core_backtrace
Comment 5 Jozef Mlich 2014-10-23 12:42:30 UTC 
Created attachment 949855 [details]
File: dso_list
Comment 6 Jozef Mlich 2014-10-23 12:42:31 UTC 
Created attachment 949856 [details]
File: environ
Comment 7 Jozef Mlich 2014-10-23 12:42:32 UTC 
Created attachment 949857 [details]
File: exploitable
Comment 8 Jozef Mlich 2014-10-23 12:42:33 UTC 
Created attachment 949858 [details]
File: journal.txt
Comment 9 Jozef Mlich 2014-10-23 12:42:35 UTC 
Created attachment 949859 [details]
File: limits
Comment 10 Jozef Mlich 2014-10-23 12:42:37 UTC 
Created attachment 949860 [details]
File: maps
Comment 11 Jozef Mlich 2014-10-23 12:42:38 UTC 
Created attachment 949861 [details]
File: open_fds
Comment 12 Jozef Mlich 2014-10-23 12:42:39 UTC 
Created attachment 949862 [details]
File: proc_pid_status
Comment 13 Jozef Mlich 2014-10-23 12:42:40 UTC 
Created attachment 949863 [details]
File: var_log_messages
Comment 14 Wolfgang Ulbrich 2014-12-01 16:31:51 UTC 
an you describe a little more detailed what happend?
Did this issue occurs frequently ?
Comment 15 Jozef Mlich 2014-12-01 16:47:48 UTC 
I have connected my Lenovo T430s to external display. First, I used VGA, then colegue connected also HDMI (displayport?), so both were connected. Then I unplugged VGA. I am not sure when exactly app crashed. It occured once. I didn't try to reproduce it.
Comment 16 Wolfgang Ulbrich 2014-12-01 17:05:29 UTC 
There is a other report which is linked to upstream, so i close this as duplicate.

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