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

Bug #745424 reported by Gaurav Kumar
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
empathy (Ubuntu)
New
Undecided
Unassigned

Bug Description

Binary package hint: empathy

This crash happened right after starting Empathy, on a 32-bit system, clean installed, with only two accounts set up.

ProblemType: Crash
DistroRelease: Ubuntu 11.04
Package: empathy 2.33.4-0ubuntu1
ProcVersionSignature: Ubuntu 2.6.38-7.39-generic 2.6.38
Uname: Linux 2.6.38-7-generic i686
Architecture: i386
Date: Tue Mar 29 22:53:08 2011
EcryptfsInUse: Yes
ExecutablePath: /usr/lib/empathy/empathy-auth-client
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Beta 1 i386 (20110329.1)
ProcCmdline: /usr/lib/empathy/empathy-auth-client
ProcEnviron:
 SHELL=/bin/bash
 LANGUAGE=en_US:en
 LANG=en_US.UTF-8
SegvAnalysis:
 Segfault happened at: 0x5279f0: mov 0x4(%eax),%ecx
 PC (0x005279f0) ok
 source "0x4(%eax)" (0x00000004) not located in a known VMA region (needed readable region)!
 destination "%ecx" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: empathy
StacktraceTop:
 ?? () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0
 g_closure_invalidate () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0
 g_closure_unref () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0
 g_signal_handler_disconnect () from /usr/lib/i386-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: No upgrade log present (probably fresh install)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

Revision history for this message
Gaurav Kumar (gaurav-b-kumar) wrote :
visibility: private → public
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.

tags: removed: need-i386-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.