Bug 1086636

Summary: [abrt] mate-screensaver: _dbus_list_unlink(): mate-screensaver-dialog killed by SIGSEGV
Product: [Fedora] Fedora Reporter: Mirco Scaramucci <beakerpeterlion>
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, dan.mashal, raveit65.sun, rdieter, scattol, stefano
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
URL: https://retrace.fedoraproject.org/faf/reports/bthash/7b6741ed857ff45a0f6733e82468c00f8bea9629
Whiteboard: abrt_hash:eb32f81a5e8e81098d2e2df08862fd37afbff71f
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-06-21 16:11:55 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

Description Mirco Scaramucci 2014-04-11 08:47:42 UTC 
Version-Release number of selected component:
mate-screensaver-1.6.2-1.fc20

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

Truncated backtrace:
Thread no. 1 (10 frames)
 #0 _dbus_list_unlink at dbus-list.c:491
 #1 _dbus_list_remove_link at dbus-list.c:519
 #2 _dbus_message_remove_counter at dbus-message.c:360
 #3 _dbus_connection_message_sent_unlocked at dbus-connection.c:671
 #4 do_writing at dbus-transport-socket.c:680
 #5 socket_do_iteration at dbus-transport-socket.c:1075
 #6 _dbus_transport_do_iteration at dbus-transport.c:976
 #7 _dbus_connection_do_iteration_unlocked at dbus-connection.c:1234
 #8 _dbus_connection_send_preallocated_unlocked_no_update at dbus-connection.c:2040
 #9 _dbus_connection_send_unlocked_no_update at dbus-connection.c:3222

Potential duplicate: bug 1012948
Comment 1 Mirco Scaramucci 2014-04-11 08:47:46 UTC 
Created attachment 885288 [details]
File: backtrace
Comment 2 Mirco Scaramucci 2014-04-11 08:47:48 UTC 
Created attachment 885289 [details]
File: cgroup
Comment 3 Mirco Scaramucci 2014-04-11 08:47:50 UTC 
Created attachment 885290 [details]
File: core_backtrace
Comment 4 Mirco Scaramucci 2014-04-11 08:47:53 UTC 
Created attachment 885291 [details]
File: dso_list
Comment 5 Mirco Scaramucci 2014-04-11 08:47:54 UTC 
Created attachment 885292 [details]
File: environ
Comment 6 Mirco Scaramucci 2014-04-11 08:47:56 UTC 
Created attachment 885293 [details]
File: exploitable
Comment 7 Mirco Scaramucci 2014-04-11 08:47:58 UTC 
Created attachment 885294 [details]
File: limits
Comment 8 Mirco Scaramucci 2014-04-11 08:48:00 UTC 
Created attachment 885295 [details]
File: maps
Comment 9 Mirco Scaramucci 2014-04-11 08:48:02 UTC 
Created attachment 885296 [details]
File: open_fds
Comment 10 Mirco Scaramucci 2014-04-11 08:48:04 UTC 
Created attachment 885297 [details]
File: proc_pid_status
Comment 11 Mirco Scaramucci 2014-04-11 08:48:06 UTC 
Created attachment 885298 [details]
File: var_log_messages
Comment 12 Wolfgang Ulbrich 2014-04-19 23:11:30 UTC 
Can you describe a little more detailed what happend?
Did this issue occurs frequently ?
Comment 13 Wolfgang Ulbrich 2014-06-21 16:11:55 UTC 
no user response!