empathy crashed with SIGSEGV in weak_refs_notify()

Bug #1034261 reported by Anders Kaseorg
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
empathy (Ubuntu)
New
Undecided
Unassigned

Bug Description

empathy crashed with SIGSEGV in weak_refs_notify()

ProblemType: Crash
DistroRelease: Ubuntu 12.10
Package: empathy 3.5.4.1-0ubuntu1
ProcVersionSignature: Ubuntu 3.5.0-8.8-generic 3.5.0
Uname: Linux 3.5.0-8-generic x86_64
NonfreeKernelModules: openafs nvidia
ApportVersion: 2.4-0ubuntu6
Architecture: amd64
Date: Wed Aug 8 01:07:55 2012
EcryptfsInUse: Yes
ExecutablePath: /usr/bin/empathy
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Alpha amd64 (20101202)
ProcCmdline: empathy
SegvAnalysis:
 Segfault happened at: 0x7fa80fc4ffdc: movq $0x0,0x88(%rax)
 PC (0x7fa80fc4ffdc) 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=0x2d900e0) at /build/buildd/glib2.0-2.33.6/./gobject/gobject.c:2469
 g_object_unref (_object=0x42e1480) at /build/buildd/glib2.0-2.33.6/./gobject/gobject.c:2986
 g_ptr_array_foreach (array=array@entry=0x365a460, func=0x415620 <g_object_unref@plt>, user_data=user_data@entry=0x0) at /build/buildd/glib2.0-2.33.6/./glib/garray.c:1434
 ptr_array_free (farray=0x365a460, flags=FREE_SEGMENT) at /build/buildd/glib2.0-2.33.6/./glib/garray.c:1063
Title: empathy crashed with SIGSEGV in weak_refs_notify()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm admin cdrom dialout fuse libvirtd lpadmin plugdev sambashare sudo

Revision history for this message
Anders Kaseorg (andersk) wrote :
Revision history for this message
Apport retracing service (apport) wrote : This bug is a duplicate

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  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.