Bug 1090166

Summary: [abrt] mate-screensaver: link_before(): mate-screensaver-dialog killed by SIGSEGV
Product: [Fedora] Fedora Reporter: Brett Yoakum <cgkades>
Component: mate-screensaverAssignee: Dan Mashal <dan.mashal>
Status: CLOSED INSUFFICIENT_DATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 20CC: bugzilla, bzf, dan.mashal, raveit65.sun, rdieter, stefano
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
URL: https://retrace.fedoraproject.org/faf/reports/bthash/59022fdf51326b5840e08e34ebc900d394f96b0f
Whiteboard: abrt_hash:0f2f0e28372478eddf8d7aac07048a80bc6c93ae
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-07-09 18:08:07 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: limits
none
File: maps
none
File: open_fds
none
File: proc_pid_status
none
File: var_log_messages none

Description Brett Yoakum 2014-04-22 19:23:51 UTC 
Description of problem:
I tried to wake from the screen saver.

Version-Release number of selected component:
mate-screensaver-1.6.2-1.fc20

Additional info:
reporter:       libreport-2.2.1
backtrace_rating: 4
cmdline:        /usr/libexec/mate-screensaver-dialog --status-message= --enable-switch
crash_function: link_before
executable:     /usr/libexec/mate-screensaver-dialog
kernel:         3.11.10-301.fc20.x86_64
runlevel:       N 5
type:           CCpp
uid:            1000

Truncated backtrace:
Thread no. 1 (10 frames)
 #0 link_before at dbus-list.c:120
 #1 _dbus_list_prepend_link at dbus-list.c:325
 #2 _dbus_list_append_link at dbus-list.c:307
 #3 _dbus_message_add_counter_link at dbus-message.c:304
 #4 _dbus_message_add_counter at dbus-message.c:338
 #5 _dbus_transport_queue_messages at dbus-transport.c:1140
 #6 do_reading at dbus-transport-socket.c:851
 #7 socket_do_iteration at dbus-transport-socket.c:1162
 #8 _dbus_transport_do_iteration at dbus-transport.c:976
 #9 _dbus_connection_do_iteration_unlocked at dbus-connection.c:1234
Comment 1 Brett Yoakum 2014-04-22 19:23:54 UTC 
Created attachment 888638 [details]
File: backtrace
Comment 2 Brett Yoakum 2014-04-22 19:23:56 UTC 
Created attachment 888639 [details]
File: cgroup
Comment 3 Brett Yoakum 2014-04-22 19:23:58 UTC 
Created attachment 888640 [details]
File: core_backtrace
Comment 4 Brett Yoakum 2014-04-22 19:23:59 UTC 
Created attachment 888641 [details]
File: dso_list
Comment 5 Brett Yoakum 2014-04-22 19:24:01 UTC 
Created attachment 888642 [details]
File: environ
Comment 6 Brett Yoakum 2014-04-22 19:24:02 UTC 
Created attachment 888643 [details]
File: limits
Comment 7 Brett Yoakum 2014-04-22 19:24:03 UTC 
Created attachment 888644 [details]
File: maps
Comment 8 Brett Yoakum 2014-04-22 19:24:05 UTC 
Created attachment 888645 [details]
File: open_fds
Comment 9 Brett Yoakum 2014-04-22 19:24:07 UTC 
Created attachment 888646 [details]
File: proc_pid_status
Comment 10 Brett Yoakum 2014-04-22 19:24:08 UTC 
Created attachment 888647 [details]
File: var_log_messages
Comment 11 Wolfgang Ulbrich 2014-06-21 16:09:31 UTC 
Can you describe a little more detailed what happend?
Did this issue occurs frequently ?
Comment 12 Wolfgang Ulbrich 2014-07-09 18:08:07 UTC 
No answer to reporter!