Bug 1079716

Summary: [abrt] empathy: folks_persona_store_get_id(): empathy-chat killed by SIGSEGV
Product: [Fedora] Fedora Reporter: Nicolas Mailhot <nicolas.mailhot>
Component: empathyAssignee: Brian Pepple <bdpepple>
Status: CLOSED EOL QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 22CC: bdpepple, uraeus
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
URL: https://retrace.fedoraproject.org/faf/reports/bthash/5a3ecf7b888c417699b7a45259a18d6b9fae16f1
Whiteboard: abrt_hash:ee95fba7f5c49fe7734ad7740cf416915bd2407a
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-07-19 11:13:48 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 Nicolas Mailhot 2014-03-23 12:39:13 UTC 
Version-Release number of selected component:
empathy-3.11.92-1.fc21

Additional info:
reporter:       libreport-2.2.0
backtrace_rating: 3
cmdline:        /usr/libexec/empathy-chat
crash_function: folks_persona_store_get_id
executable:     /usr/libexec/empathy-chat
kernel:         3.14.0-0.rc6.git4.1.fc21.x86_64
runlevel:       N 5
type:           CCpp
uid:            1000

Truncated backtrace:
Thread no. 1 (10 frames)
 #0 folks_persona_store_get_id at persona-store.c:589
 #1 _tpf_persona_store_set_cache_needs_update at tpf-persona-store.c:3137
 #2 _tpf_persona___lambda14_ at tpf-persona.c:4317
 #3 __tpf_persona___lambda14__g_object_notify at tpf-persona.c:4324
 #9 g_object_notify_by_spec_internal at gobject.c:1147
 #10 g_object_notify at gobject.c:1194
 #11 contact_maybe_set_client_types at contact.c:2663
 #12 ??
 #13 ??
 #14 ?? at contact.c:3110
Comment 1 Nicolas Mailhot 2014-03-23 12:39:30 UTC 
Created attachment 877802 [details]
File: backtrace
Comment 2 Nicolas Mailhot 2014-03-23 12:39:36 UTC 
Created attachment 877805 [details]
File: cgroup
Comment 3 Nicolas Mailhot 2014-03-23 12:39:52 UTC 
Created attachment 877811 [details]
File: core_backtrace
Comment 4 Nicolas Mailhot 2014-03-23 12:39:55 UTC 
Created attachment 877813 [details]
File: dso_list
Comment 5 Nicolas Mailhot 2014-03-23 12:40:00 UTC 
Created attachment 877814 [details]
File: environ
Comment 6 Nicolas Mailhot 2014-03-23 12:40:18 UTC 
Created attachment 877817 [details]
File: exploitable
Comment 7 Nicolas Mailhot 2014-03-23 12:40:25 UTC 
Created attachment 877818 [details]
File: limits
Comment 8 Nicolas Mailhot 2014-03-23 12:40:29 UTC 
Created attachment 877820 [details]
File: maps
Comment 9 Nicolas Mailhot 2014-03-23 12:40:38 UTC 
Created attachment 877821 [details]
File: open_fds
Comment 10 Nicolas Mailhot 2014-03-23 12:40:43 UTC 
Created attachment 877822 [details]
File: proc_pid_status
Comment 11 Nicolas Mailhot 2014-03-23 12:40:51 UTC 
Created attachment 877823 [details]
File: var_log_messages
Comment 12 Jaroslav Reznik 2015-03-03 15:37:30 UTC 
This bug appears to have been reported against 'rawhide' during the Fedora 22 development cycle.
Changing version to '22'.

More information and reason for this action is here:
https://fedoraproject.org/wiki/Fedora_Program_Management/HouseKeeping/Fedora22
Comment 13 Fedora End Of Life 2016-07-19 11:13:48 UTC 
Fedora 22 changed to end-of-life (EOL) status on 2016-07-19. Fedora 22 is
no longer maintained, which means that it will not receive any further
security or bug fix updates. As a result we are closing this bug.

If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen this bug against that version. If you
are unable to reopen this bug, please file a new report against the
current release. If you experience problems, please add a comment to this
bug.

Thank you for reporting this bug and we are sorry it could not be fixed.