empathy crashed with SIGSEGV in g_strdup()

[Sulle]

Binary package hint: empathy

Got this error while chatting on empathy.

ProblemType: Crash
Architecture: amd64
Date: Tue Mar 23 17:55:25 2010
DistroRelease: Ubuntu 10.04
ExecutablePath: /usr/bin/empathy
InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Beta amd64 (20100318)
NonfreeKernelModules: nvidia
Package: empathy 2.29.93-0ubuntu2
ProcCmdline: empathy
ProcEnviron:
 LANGUAGE=nb_NO:nb:no_NO:no:nn_NO:nn:en
 LANG=nb_NO.utf8
 SHELL=/bin/bash
ProcVersionSignature: Ubuntu 2.6.32-16.25-generic
SegvAnalysis:
 Segfault happened at: 0x7f224cadb022: pcmpeqb (%rdi),%xmm2
 PC (0x7f224cadb022) ok
 source "(%rdi)" (0xaaaaaaaaaaaaaaa0) not located in a known VMA region (needed readable region)!
 destination "%xmm2" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: empathy
StacktraceTop:
 ?? () from /lib/libc.so.6
 g_strdup () from /lib/libglib-2.0.so.0
 ?? () from /usr/lib/libgobject-2.0.so.0
 ?? () from /usr/lib/libdbus-glib-1.so.2
 ?? () from /usr/lib/libdbus-glib-1.so.2
Title: empathy crashed with SIGSEGV in g_strdup()
Uname: Linux 2.6.32-16-generic x86_64
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
XsessionErrors:
 (polkit-gnome-authentication-agent-1:1446): GLib-CRITICAL **: g_once_init_leave: assertion `initialization_value != 0' failed
 (gnome-terminal:1610): Gtk-CRITICAL **: gtk_accel_map_unlock_path: assertion `entry != NULL && entry->lock_count > 0' failed

[Apport retracing service (apport)]

StacktraceTop:
 __strlen_sse2 () at ../sysdeps/x86_64/multiarch/../strlen.S:31
 g_ascii_strncasecmp () from /lib/libglib-2.0.so.0
 ?? ()
 ?? ()
 g_value_get_boxed ()

[Omer Akram (om26er)]

thanks for the bug report. is this still an issue?

[Vish (vish)]

Thank you for taking the time to report this bug and helping to make Ubuntu better.
 If this is still an issue, Please try to obtain a backtrace following the instructions at http://wiki.ubuntu.com/DebuggingProgramCrash and upload the backtrace (as an attachment) to the bug report. This will greatly help us in tracking down your problem.

[Omer Akram (om26er)]

We are closing this bug report because it lacks the information we need to investigate the problem, as described in the previous comments. Please reopen it if you can give us the missing information, and don't hesitate to submit bug reports in the future. To reopen the bug report you can click on the current status, under the Status column, and change the Status back to "New". Thanks again!