empathy crashed with SIGSEGV in g_type_check_instance()

[Brandon S Hosey]

Binary package hint: empathy

After I start empathy it start fine. But once a close the contacts window I can no longer bring it back up.

ProblemType: Crash
Architecture: amd64
CrashCounter: 1
Date: Sun Feb 7 10:10:23 2010
DistroRelease: Ubuntu 10.04
ExecutablePath: /usr/bin/empathy
InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Alpha amd64 (20100203)
Package: empathy 2.29.6-0ubuntu3
ProcCmdline: empathy
ProcEnviron:
 SHELL=/bin/bash
 LANG=en_US.utf8
ProcVersionSignature: Ubuntu 2.6.32-12.17-generic
SegvAnalysis:
 Segfault happened at: 0x7fd02bb2deb9 <g_type_check_instance+9>: mov (%rdi),%rax
 PC (0x7fd02bb2deb9) ok
 source "(%rdi)" (0x0001f5f6) not located in a known VMA region (needed readable region)!
 destination "%rax" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: empathy
StacktraceTop:
 g_type_check_instance ()
 g_signal_emit_valist ()
 g_signal_emit () from /usr/lib/libgobject-2.0.so.0
 g_closure_invoke ()
 ?? () from /usr/lib/libgobject-2.0.so.0
Title: empathy crashed with SIGSEGV in g_type_check_instance()
Uname: Linux 2.6.32-12-generic x86_64
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
XsessionErrors:
 (gnome-settings-daemon:1647): GLib-CRITICAL **: g_propagate_error: assertion `src != NULL' failed
 (gnome-settings-daemon:1647): GLib-CRITICAL **: g_propagate_error: assertion `src != NULL' failed
 (polkit-gnome-authentication-agent-1:1674): GLib-CRITICAL **: g_once_init_leave: assertion `initialization_value != 0' failed

[Apport retracing service (apport)]

StacktraceTop:
 g_type_check_instance ()
 g_signal_emit_valist ()
 g_signal_emit () from /usr/lib/libgobject-2.0.so.0
 g_closure_invoke ()
 ?? () from /usr/lib/libgobject-2.0.so.0

[Sebastien Bacher (seb128)]

Thank you for your bug report, could you try if that's still an issue with current lucid updates?

[Deactivated User (deactivated-user636007-deactivatedaccount)]

Still a bug with the latest Lucid update.

[Sebastien Bacher (seb128)]

Confirmed using 0ubuntu5 and after a session restart

[Sebastien Bacher (seb128)]

in fact the one I got was bug #518735

[Ken VanDine (ken-vandine)]

Thank you for your bug report, could you try if that's still an issue with current lucid updates?

[Martin Mai (mrkanister-deactivatedaccount-deactivatedaccount)]

Closing the bug as no further information has been provided.