empathy crashed with SIGSEGV in empathy_contact_get_account()

[Timo Jyrinki]

Happens reliably at the get_account when trying to do an audio call via SIP after setting an account.

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: empathy 3.3.3-0ubuntu4
ProcVersionSignature: Ubuntu 3.2.0-8.15-generic 3.2.0
Uname: Linux 3.2.0-8-generic x86_64
ApportVersion: 1.90-0ubuntu2
Architecture: amd64
Date: Wed Jan 18 14:07:08 2012
EcryptfsInUse: Yes
ExecutablePath: /usr/bin/empathy
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Alpha amd64 (20111117)
ProcCmdline: empathy
SegvAnalysis:
 Segfault happened at: 0x47e896 <empathy_contact_get_account+22>: cmp %rax,(%rdx)
 PC (0x0047e896) ok
 source "%rax" ok
 destination "(%rdx)" (0xe7894cc689f2894c) not located in a known VMA region (needed writable region)!
SegvReason: writing unknown VMA
Signal: 11
SourcePackage: empathy
StacktraceTop:
 empathy_contact_get_account ()
 ?? ()
 g_closure_invoke () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 g_signal_emit_valist () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
Title: empathy crashed with SIGSEGV in empathy_contact_get_account()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

[Apport retracing service (apport)]

StacktraceTop:
 empathy_contact_get_account (contact=0x7fe29a12eb5f) at empathy-contact.c:978
 empathy_new_call_dialog_response (dialog=0xd9f380, response_id=-3) at empathy-new-call-dialog.c:99
 g_closure_invoke (closure=0xcf59a0, return_value=0x0, n_param_values=2, param_values=0x1131a30, invocation_hint=<optimized out>) at /build/buildd/glib2.0-2.31.10/./gobject/gclosure.c:774
 signal_emit_unlocked_R (node=<optimized out>, detail=0, instance=<optimized out>, emission_return=0x0, instance_and_params=0x1131a30) at /build/buildd/glib2.0-2.31.10/./gobject/gsignal.c:3340
 g_signal_emit_valist (instance=<optimized out>, signal_id=<optimized out>, detail=<optimized out>, var_args=0x7fff3e6f8e18) at /build/buildd/glib2.0-2.31.10/./gobject/gsignal.c:3033

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[Bilal Shahid (s9iper1)]

Thank you for taking the time to report this bug and helping to make Ubuntu better. Please answer these questions:

* Is this reproducible?
* If so, what specific steps should we take to recreate this bug?

This will help us to find and resolve the problem

[Timo Jyrinki (timo-jyrinki)]

Now fixed in precise again, it seems. Calling doesn't crash anymore and the call actually works.