telepathy-gabble crashed with SIGSEGV in g_signal_emit_valist()

[Ted Gould]

Setting up Google Talk account in Online Accounts.

ProblemType: Crash
DistroRelease: Ubuntu 14.04
Package: telepathy-gabble 0.18.1-2
ProcVersionSignature: Ubuntu 3.13.0-15.35-generic 3.13.5
Uname: Linux 3.13.0-15-generic x86_64
ApportVersion: 2.13.3-0ubuntu1
Architecture: amd64
CurrentDesktop: Unity
Date: Mon Mar 17 13:44:50 2014
DistributionChannelDescriptor:
 # This is a distribution channel descriptor
 # For more information see http://wiki.ubuntu.com/DistributionChannelDescriptor
 canonical-oem-somerville-precise-amd64-20130203-1
EcryptfsInUse: Yes
ExecutablePath: /usr/lib/telepathy/telepathy-gabble
InstallationDate: Installed on 2013-12-13 (94 days ago)
InstallationMedia: Ubuntu 12.04 "Precise" - Build amd64 LIVE Binary 20130203-13:50
ProcCmdline: /usr/lib/telepathy/telepathy-gabble
ProcEnviron:
 XDG_RUNTIME_DIR=<set>
 SHELL=/bin/bash
 LANGUAGE=en_US
 PATH=(custom, no user)
 LANG=en_US.UTF-8
SegvAnalysis:
 Segfault happened at: 0x7ffc696e5d6f: mov 0x18(%r12),%r15
 PC (0x7ffc696e5d6f) ok
 source "0x18(%r12)" (0x00000018) not located in a known VMA region (needed readable region)!
 destination "%r15" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: telepathy-gabble
StacktraceTop:
 ?? () from /usr/lib/telepathy/gabble-0/lib/libwocky-telepathy-gabble-0.18.1.so
 ?? () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
 ?? () from /usr/lib/x86_64-linux-gnu/libgio-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: telepathy-gabble crashed with SIGSEGV in g_signal_emit_valist()
UpgradeStatus: Upgraded to trusty on 2013-12-21 (85 days ago)
UserGroups: adm audio autopilot cdrom dip libvirtd lpadmin plugdev sambashare sudo users

[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 #1237191, 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.