Bug 1093519

Summary: [abrt] mate-screensaver: _dbus_mem_pool_dealloc(): mate-screensaver-dialog killed by SIGSEGV
Product: [Fedora] Fedora Reporter: liuyuqi.crh
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: dan.mashal, raveit65.sun, rdieter, stefano
Target Milestone: ---   
Target Release: ---   
Hardware: i686   
OS: Unspecified   
URL: https://retrace.fedoraproject.org/faf/reports/bthash/0f26f616bcf4ab6c1a1d002864c528291663efe0
Whiteboard: abrt_hash:ebdb2e37b60398d8a59a50c492c7b38786dd2489
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-07-09 18:12:05 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 liuyuqi.crh 2014-05-02 00:31:11 UTC 
Version-Release number of selected component:
mate-screensaver-1.6.1-4.fc20

Additional info:
reporter:       libreport-2.1.10
backtrace_rating: 4
cmdline:        /usr/libexec/mate-screensaver-dialog --status-message= --enable-switch
crash_function: _dbus_mem_pool_dealloc
executable:     /usr/libexec/mate-screensaver-dialog
kernel:         3.12.5-302.fc20.i686
runlevel:       N 5
type:           CCpp
uid:            1000

Truncated backtrace:
Thread no. 1 (10 frames)
 #0 _dbus_mem_pool_dealloc at dbus-mempool.c:398
 #1 free_link at dbus-list.c:97
 #2 _dbus_list_remove_link at dbus-list.c:520
 #3 _dbus_list_remove at dbus-list.c:414
 #4 _dbus_rmutex_free_at_location at dbus-threads.c:139
 #5 _dbus_connection_last_unref at dbus-connection.c:2747
 #6 dbus_connection_unref at dbus-connection.c:2796
 #7 dbus_g_connection_unref at dbus-glib.c:91
 #8 close_and_unref at pam_fprintd.c:170
 #9 do_auth at pam_fprintd.c:401
Comment 1 liuyuqi.crh 2014-05-02 00:31:15 UTC 
Created attachment 891649 [details]
File: backtrace
Comment 2 liuyuqi.crh 2014-05-02 00:31:17 UTC 
Created attachment 891650 [details]
File: cgroup
Comment 3 liuyuqi.crh 2014-05-02 00:31:18 UTC 
Created attachment 891651 [details]
File: core_backtrace
Comment 4 liuyuqi.crh 2014-05-02 00:31:20 UTC 
Created attachment 891652 [details]
File: dso_list
Comment 5 liuyuqi.crh 2014-05-02 00:31:22 UTC 
Created attachment 891653 [details]
File: environ
Comment 6 liuyuqi.crh 2014-05-02 00:31:23 UTC 
Created attachment 891654 [details]
File: exploitable
Comment 7 liuyuqi.crh 2014-05-02 00:31:25 UTC 
Created attachment 891655 [details]
File: limits
Comment 8 liuyuqi.crh 2014-05-02 00:31:26 UTC 
Created attachment 891656 [details]
File: maps
Comment 9 liuyuqi.crh 2014-05-02 00:31:28 UTC 
Created attachment 891657 [details]
File: open_fds
Comment 10 liuyuqi.crh 2014-05-02 00:31:29 UTC 
Created attachment 891658 [details]
File: proc_pid_status
Comment 11 liuyuqi.crh 2014-05-02 00:31:31 UTC 
Created attachment 891659 [details]
File: var_log_messages
Comment 12 Wolfgang Ulbrich 2014-06-21 16:09:03 UTC 
Can you describe a little more detailed what happend?
Did this issue occurs frequently ?
Comment 13 Wolfgang Ulbrich 2014-07-09 18:12:05 UTC 
No answer from reporter!