empathy-auth-client crashed with SIGSEGV in g_simple_async_result_complete()

Bug #1031248 reported by Gerhard Bogner
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
empathy (Ubuntu)
New
Undecided
Unassigned

Bug Description

the crash occurred right after logging in, probably when gnome shell tried connecting to one of the online accounts.

ProblemType: Crash
DistroRelease: Ubuntu 12.10
Package: empathy 3.5.4.1-0ubuntu1
ProcVersionSignature: Ubuntu 3.5.0-6.6-generic 3.5.0
Uname: Linux 3.5.0-6-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.4-0ubuntu6
Architecture: amd64
Date: Tue Jul 31 10:14:14 2012
ExecutablePath: /usr/lib/empathy/empathy-auth-client
InstallationMedia: Ubuntu 12.10 "Quantal Quetzal" - Alpha amd64+mac (20120627)
ProcCmdline: /usr/lib/empathy/empathy-auth-client
SegvAnalysis:
 Segfault happened at: 0x7fe3f2473fd4: mov (%rdi),%rdi
 PC (0x7fe3f2473fd4) ok
 source "(%rdi)" (0x00000000) not located in a known VMA region (needed readable region)!
 destination "%rdi" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: empathy
StacktraceTop:
 ?? () from /usr/lib/empathy/libempathy-3.5.4.1.so
 ?? () from /usr/lib/empathy/libempathy-3.5.4.1.so
 g_simple_async_result_complete () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
 ?? () from /usr/lib/empathy/libempathy-3.5.4.1.so
 ?? () from /usr/lib/x86_64-linux-gnu/libtelepathy-glib.so.0
Title: empathy-auth-client crashed with SIGSEGV in g_simple_async_result_complete()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom debian-transmission dip lpadmin plugdev sambashare sudo

Revision history for this message
Gerhard Bogner (bogi788) 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 #1029258, 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.