empathy crashed with SIGSEGV in _empathy_marshal_VOID__UINT_UINT()

[Massimiliano Forner]

Binary package hint: empathy

Just happened, without any clear reason. In the last alpha push of Ubuntu, empathy was more stable. It must be said that I'm currently using the Gnome Shell and not Unity.

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 i686
NonfreeKernelModules: openafs nvidia
Architecture: i386
CheckboxSubmission: 39353571f10042c61cadb5c2e632569c
CheckboxSystem: e704f33cc0866ff0f0256a33de39ea1c
Date: Fri Apr 1 17:58:44 2011
ExecutablePath: /usr/bin/empathy
ProcCmdline: /usr/bin/empathy
ProcEnviron:
 LANGUAGE=en
 LANG=it_IT.utf8
 LC_MESSAGES=en_GB.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x807b49e: mov 0x14(%esi),%eax
 PC (0x0807b49e) ok
 source "0x14(%esi)" (0x00000014) not located in a known VMA region (needed readable region)!
 destination "%eax" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: empathy
StacktraceTop:
 ?? ()
 ?? ()
 _empathy_marshal_VOID__UINT_UINT ()
 g_closure_invoke () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0
 ?? () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0
Title: empathy crashed with SIGSEGV in _empathy_marshal_VOID__UINT_UINT()
UpgradeStatus: Upgraded to natty on 2011-03-29 (2 days ago)
UserGroups: adm admin cdrom dialout dip fuse lpadmin netdev plugdev sambashare
XsessionErrors:
 (firefox-bin:11199): Gtk-CRITICAL **: IA__gtk_clipboard_get_for_display: assertion `!display->closed' failed
 (firefox-bin:11199): Gtk-CRITICAL **: IA__gtk_clipboard_get_for_display: assertion `!display->closed' failed

[Apport retracing service (apport)]

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 #746712, 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.