empathy crashed with SIGSEGV in g_object_unref()

Bug #1035362 reported by James Lewis on 2012-08-10
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
empathy (Ubuntu)
Undecided
Unassigned

Bug Description

I came back to my desk after being away to find this error, I had left myself in an IRC chat room... but I don't know if that is related.

ProblemType: Crash
DistroRelease: Ubuntu 12.10
Package: empathy 3.5.4.1-0ubuntu1
ProcVersionSignature: Ubuntu 3.5.0-9.9-generic 3.5.0
Uname: Linux 3.5.0-9-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.4-0ubuntu6
Architecture: amd64
CrashCounter: 1
Date: Fri Aug 10 15:53:33 2012
ExecutablePath: /usr/bin/empathy
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Beta amd64 (20120418.1)
ProcCmdline: empathy
ProcEnviron:
 LANGUAGE=en_GB:en
 PATH=(custom, no user)
 LANG=en_GB.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x7fcb2d24bfdc: movq $0x0,0x88(%rax)
 PC (0x7fcb2d24bfdc) 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-06-05 (66 days ago)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

James Lewis (james-fsck) 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