telepathy-salut crashed with signal 5 in g_object_get()

[Lucas Benninger]

I tried sending a message to a computer on my LAN via empathy. It never recieved the message

telepathy-salut:
  Installed: 0.8.0-0ubuntu1
  Candidate: 0.8.0-0ubuntu1
  Version table:
 *** 0.8.0-0ubuntu1 0
        500 http://ca.archive.ubuntu.com/ubuntu/ precise/main amd64 Packages
        100 /var/lib/dpkg/status

empathy:
  Installed: 3.4.0.2-0ubuntu1
  Candidate: 3.4.0.2-0ubuntu1
  Version table:
 *** 3.4.0.2-0ubuntu1 0
        500 http://ca.archive.ubuntu.com/ubuntu/ precise/main amd64 Packages
        100 /var/lib/dpkg/status

Description: Ubuntu precise (development branch)
Release: 12.04

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: telepathy-salut 0.8.0-0ubuntu1
ProcVersionSignature: Ubuntu 3.2.0-23.36-generic 3.2.14
Uname: Linux 3.2.0-23-generic x86_64
NonfreeKernelModules: wl fglrx
ApportVersion: 2.0.1-0ubuntu3
Architecture: amd64
Date: Sun Apr 15 12:54:55 2012
ExecutablePath: /usr/lib/telepathy/telepathy-salut
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Alpha amd64 (20120303)
ProcCmdline: /usr/lib/telepathy/telepathy-salut
ProcEnviron:
 SHELL=/bin/bash
 PATH=(custom, no user)
 LANGUAGE=en_CA:en
 LANG=en_CA.UTF-8
Signal: 5
SourcePackage: telepathy-salut
StacktraceTop:
 g_object_get () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 text_helper_report_delivery_error ()
 ?? ()
 g_simple_async_result_complete () from /usr/lib/x86_64-linux-gnu/libgio-2.0.so.0
 ?? () from /usr/lib/telepathy/salut-0/lib/libwocky-telepathy-salut-0.8.0.so
Title: telepathy-salut crashed with signal 5 in g_object_get()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

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