empathy crashed with SIGSEGV in g_object_unref()

Bug #1037328 reported by Scott Sweeny
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
empathy (Ubuntu)
New
Undecided
Unassigned

Bug Description

Happened on quantal up-to-date as of 2012-08-15. No action triggered it that I'm aware of, though it's possible that it happened as I un-idled my desktop since the popup rose shortly after I returned to my computer.

ProblemType: Crash
DistroRelease: Ubuntu 12.10
Package: empathy 3.5.5-0ubuntu1
ProcVersionSignature: Ubuntu 3.5.0-10.10-generic 3.5.1
Uname: Linux 3.5.0-10-generic x86_64
ApportVersion: 2.4-0ubuntu6
Architecture: amd64
Date: Wed Aug 15 17:36:53 2012
ExecutablePath: /usr/bin/empathy
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release amd64 (20110427.1)
ProcCmdline: empathy
ProcEnviron:
 PATH=(custom, user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x7f9f95ef2fdc: movq $0x0,0x88(%rax)
 PC (0x7f9f95ef2fdc) 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
 ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 g_object_unref () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 g_ptr_array_foreach () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 ?? () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
Title: empathy crashed with SIGSEGV in g_object_unref()
UpgradeStatus: Upgraded to quantal on 2012-07-31 (15 days ago)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare sbuild

Revision history for this message
Scott Sweeny (ssweeny) 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.