empathy crashed with SIGSEGV in weak_refs_notify()

Bug #1036378 reported by Felix Möller on 2012-08-13
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
empathy (Ubuntu)
Undecided
Unassigned

Bug Description

I had empathy running for several hours and this crashed occured after doing nothing empathy related for at least an hour.

ProblemType: Crash
DistroRelease: Ubuntu 12.10
Package: empathy 3.5.5-0ubuntu1
ProcVersionSignature: Ubuntu 3.5.0-9.9-generic 3.5.0
Uname: Linux 3.5.0-9-generic x86_64
ApportVersion: 2.4-0ubuntu6
Architecture: amd64
Date: Mon Aug 13 22:29:15 2012
ExecutablePath: /usr/bin/empathy
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Beta amd64 (20120331)
ProcCmdline: empathy
ProcEnviron:
 PATH=(custom, user)
 LANG=de_DE.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x7fc2c8c70fdc: movq $0x0,0x88(%rax)
 PC (0x7fc2c8c70fdc) ok
 source "$0x0" ok
 destination "0x88(%rax)" (0xaaaaaaaaaaaaab32) not located in a known VMA region (needed writable region)!
SegvReason: writing unknown VMA
Signal: 11
SourcePackage: empathy
StacktraceTop:
 ?? () from /usr/lib/libfolks-telepathy.so.25
 weak_refs_notify (data=0x116ab60) at /build/buildd/glib2.0-2.33.8/./gobject/gobject.c:2469
 g_object_unref (_object=0x1b08d50) at /build/buildd/glib2.0-2.33.8/./gobject/gobject.c:2986
 g_ptr_array_foreach (array=array@entry=0x4b92c00, func=0x415550 <g_object_unref@plt>, user_data=user_data@entry=0x0) at /build/buildd/glib2.0-2.33.8/./glib/garray.c:1434
 ptr_array_free (farray=0x4b92c00, flags=FREE_SEGMENT) at /build/buildd/glib2.0-2.33.8/./glib/garray.c:1063
Title: empathy crashed with SIGSEGV in weak_refs_notify()
UpgradeStatus: Upgraded to quantal on 2012-08-02 (10 days ago)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

Felix Möller (felix-derklecks) wrote :

Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1024217, so is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Please continue to report any other bugs you may find.

visibility: private → public
tags: removed: need-amd64-retrace
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers