empathy crashed with SIGSEGV

[Andrew Fister]

Binary package hint: empathy

Just installed Lucid Alpha 2 with all of the packages updated as of posting this bug report. The first thing I tried to do after installing and updating was to click on the "Me Menu" and then "Chat Accounts", which attempts to launch Empathy in order to set up chat accounts, presumably. This was before I opened Empathy even one time, as I just finished the install process.

Empathy crashes in this case, and Apport responds appropriately.

ProblemType: Crash
Architecture: amd64
CrashCounter: 1
Date: Sun Feb 7 01:45:22 2010
DistroRelease: Ubuntu 10.04
ExecutablePath: /usr/bin/empathy
InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Alpha amd64 (20100113)
Package: empathy 2.29.6-0ubuntu2
ProcCmdline: empathy -a
ProcEnviron:
 LANG=en_US.utf8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.32-12.17-generic
SegvAnalysis:
 Segfault happened at: 0x47cefb: mov 0x18(%rdi),%rbp
 PC (0x0047cefb) ok
 source "0x18(%rdi)" (0x00000018) not located in a known VMA region (needed readable region)!
 destination "%rbp" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: empathy
StacktraceTop:
 ?? ()
 ?? ()
 ?? () from /usr/lib/libtelepathy-glib.so.0
 ?? () from /usr/lib/libtelepathy-glib.so.0
 ?? () from /usr/lib/libtelepathy-glib.so.0
Title: empathy crashed with SIGSEGV
Uname: Linux 2.6.32-12-generic x86_64
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
XsessionErrors:
 (gnome-settings-daemon:1392): GLib-CRITICAL **: g_propagate_error: assertion `src != NULL' failed
 (gnome-settings-daemon:1392): GLib-CRITICAL **: g_propagate_error: assertion `src != NULL' failed
 (polkit-gnome-authentication-agent-1:1408): GLib-CRITICAL **: g_once_init_leave: assertion `initialization_value != 0' 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 #518066, 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.