Bug 886535

Summary: [abrt] empathy-3.6.2-2.fc18: g_malloc0: Process /usr/libexec/empathy-auth-client was killed by signal 6 (SIGABRT)
Product: [Fedora] Fedora Reporter: admin
Component: empathyAssignee: Brian Pepple <bdpepple>
Status: CLOSED WONTFIX QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 18CC: bdpepple, uraeus
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
Whiteboard: abrt_hash:69c871a399e050e1a1eed0ee44ba1da8d31b9dc7
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-02-05 13:50:20 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: smolt_data none

Description admin 2012-12-12 13:55:46 UTC 
Description of problem:
just log in to kde

Version-Release number of selected component:
empathy-3.6.2-2.fc18

Additional info:
backtrace_rating: 4
cmdline:        /usr/libexec/empathy-auth-client
crash_function: g_malloc0
executable:     /usr/libexec/empathy-auth-client
kernel:         3.6.10-4.fc18.x86_64
remote_result:  NOTFOUND
uid:            1000
var_log_messages: Dec 12 19:32:11 mobile abrt[3158]: Saved core dump of pid 3149 (/usr/libexec/empathy-auth-client) to /var/spool/abrt/ccpp-2012-12-12-19:32:10-3149 (14446592 bytes)
xsession_errors: 

Truncated backtrace:
Thread no. 1 (10 frames)
 #4 g_malloc0 at gmem.c:194
 #5 thread_memory_from_self at gslice.c:512
 #6 smc_tree_branch_lookup_nearest_L at gslice.c:1561
 #7 smc_tree_insert at gslice.c:1595
 #8 smc_notify_alloc at gslice.c:1467
 #9 g_slice_alloc at gslice.c:1005
 #10 g_string_sized_new at gstring.c:126
 #11 g_string_new at gstring.c:152
 #12 g_log_default_handler at gmessages.c:1322
 #15 g_malloc0 at gmem.c:194
Comment 1 admin 2012-12-12 13:55:50 UTC 
Created attachment 662368 [details]
File: backtrace
Comment 2 admin 2012-12-12 13:55:53 UTC 
Created attachment 662369 [details]
File: cgroup
Comment 3 admin 2012-12-12 13:55:55 UTC 
Created attachment 662370 [details]
File: core_backtrace
Comment 4 admin 2012-12-12 13:55:58 UTC 
Created attachment 662371 [details]
File: dso_list
Comment 5 admin 2012-12-12 13:56:01 UTC 
Created attachment 662372 [details]
File: environ
Comment 6 admin 2012-12-12 13:56:04 UTC 
Created attachment 662373 [details]
File: limits
Comment 7 admin 2012-12-12 13:56:07 UTC 
Created attachment 662374 [details]
File: maps
Comment 8 admin 2012-12-12 13:56:10 UTC 
Created attachment 662375 [details]
File: open_fds
Comment 9 admin 2012-12-12 13:56:12 UTC 
Created attachment 662376 [details]
File: proc_pid_status
Comment 10 admin 2012-12-12 13:56:15 UTC 
Created attachment 662377 [details]
File: smolt_data
Comment 11 Fedora End Of Life 2013-12-21 09:52:43 UTC 
This message is a reminder that Fedora 18 is nearing its end of life.
Approximately 4 (four) weeks from now Fedora will stop maintaining
and issuing updates for Fedora 18. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as WONTFIX if it remains open with a Fedora 
'version' of '18'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version prior to Fedora 18's end of life.

Thank you for reporting this issue and we are sorry that we may not be 
able to fix it before Fedora 18 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior to Fedora 18's end of life.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.
Comment 12 Fedora End Of Life 2014-02-05 13:50:26 UTC 
Fedora 18 changed to end-of-life (EOL) status on 2014-01-14. Fedora 18 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.