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

Bug #750118 reported by Guy Van Sanden
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
empathy (Ubuntu)
New
Undecided
Unassigned

Bug Description

Binary package hint: empathy

This happens every time on using Facebook XMPP chat, Google Talk is working perfectly

ProblemType: Crash
DistroRelease: Ubuntu 11.04
Package: empathy 2.34.0-0ubuntu1
ProcVersionSignature: Ubuntu 2.6.38-7.39-generic 2.6.38
Uname: Linux 2.6.38-7-generic x86_64
NonfreeKernelModules: nvidia
Architecture: amd64
Date: Mon Apr 4 11:50:34 2011
ExecutablePath: /usr/lib/empathy/empathy-auth-client
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Alpha amd64 (20110321)
ProcCmdline: /usr/lib/empathy/empathy-auth-client
ProcEnviron:
 SHELL=/usr/bin/zsh
 PATH=(custom, user)
 LANGUAGE=en_IE:en
 LANG=en_IE.utf8
SegvAnalysis:
 Segfault happened at: 0x7fe869438316: mov 0x8(%rax),%edi
 PC (0x7fe869438316) ok
 source "0x8(%rax)" (0x00000008) not located in a known VMA region (needed readable region)!
 destination "%edi" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: empathy
StacktraceTop:
 ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 g_closure_invalidate () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 g_closure_unref () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 g_signal_handler_disconnect () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 ?? () from /usr/lib/libtelepathy-glib.so.0
Title: empathy-auth-client crashed with SIGSEGV in g_closure_invalidate()
UpgradeStatus: Upgraded to natty on 2011-03-25 (10 days ago)
UserGroups: adm admin cdrom dialout libvirtd lpadmin plugdev sambashare vboxusers

Revision history for this message
Guy Van Sanden (gvs) 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 Ubuntu better. This particular crash has already been reported and is a duplicate of bug #726842, 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.