empathy crashed with SIGSEGV in empathy_contact_get_account()

[Scott Sweeny]

Empathy crashed as I was trying to dial the conference line on my employer's internal SIP service.

I opened the "New Call" dialog via the menu and typed in the number for the conference line. The list of potential call recipients (which was pre-filled with some GChat contacts) was replaced with what looked like the correct entry (<number>@<company>) but when I clicked on "Audio Call" the program segfaulted.

I haven't changed my SIP account settings since upgrading from 11.10, when it worked flawlessly.

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: empathy 3.3.3-0ubuntu4
ProcVersionSignature: Ubuntu 3.2.0-9.16-generic 3.2.1
Uname: Linux 3.2.0-9-generic x86_64
ApportVersion: 1.90-0ubuntu2
Architecture: amd64
CheckboxSubmission: f24bf886cf6158b8cd6d663f166fcff9
CheckboxSystem: 3935143777c965daaa64b51f0134f712
Date: Wed Jan 18 11:14:09 2012
DuplicateOf: https://bugs.launchpad.net/bugs/918158
ExecutablePath: /usr/bin/empathy
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007)
ProcCmdline: empathy
ProcEnviron:
 PATH=(custom, user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
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: Upgraded to precise on 2012-01-17 (1 days ago)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

[Apport retracing service (apport)]

Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #918158, 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.