telepathy-logger crashed with SIGSEGV in vfprintf()

[avinas]

tried to call, happend wthen hung up

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: telepathy-logger 0.4.0-0ubuntu1
ProcVersionSignature: Ubuntu 3.2.0-38.60-generic 3.2.37
Uname: Linux 3.2.0-38-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.0.1-0ubuntu17.1
Architecture: amd64
Date: Mon Feb 25 15:21:11 2013
ExecutablePath: /usr/lib/telepathy/telepathy-logger
ExecutableTimestamp: 1333475034
InstallationMedia: Ubuntu 12.04.1 LTS "Precise Pangolin" - Release amd64 (20120823.1)
MarkForUpload: True
ProcCmdline: /usr/lib/telepathy/telepathy-logger
ProcCwd: /
ProcEnviron:
 SHELL=/bin/bash
 PATH=(custom, no user)
 LANGUAGE=en_GB:en
 LANG=en_GB.UTF-8
SegvAnalysis:
 Segfault happened at: 0x7f35ef0b63b1 <vfprintf+10737>: repnz scas %es:(%rdi),%al
 PC (0x7f35ef0b63b1) ok
 source "%es:(%rdi)" (0x00000048) not located in a known VMA region (needed readable region)!
 destination "%al" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: telepathy-logger
StacktraceTop:
 _IO_vfprintf_internal (s=<optimised out>, format=<optimised out>, ap=<optimised out>) at vfprintf.c:1630
 __GI___vasprintf_chk (result_ptr=0x7fffa00fa8a8, flags=1, format=0x7f35effc05a0 "%s: Moving to ENDED_STATE, duration=%li reason=%s details=%s", args=0x7fffa00fa8c8) at vasprintf_chk.c:68
 vasprintf (__ap=<optimised out>, __fmt=<optimised out>, __ptr=0x7fffa00fa8a8) at /usr/include/x86_64-linux-gnu/bits/stdio2.h:199
 g_vasprintf (string=0x7fffa00fa8a8, format=<optimised out>, args=<optimised out>) at /build/buildd/glib2.0-2.32.3/./glib/gprintf.c:314
 g_strdup_vprintf (format=<optimised out>, args=<optimised out>) at /build/buildd/glib2.0-2.32.3/./glib/gstrfuncs.c:509
Title: telepathy-logger crashed with SIGSEGV in vfprintf()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm audio cdrom dialout dip fax floppy fuse lpadmin netdev plugdev sambashare scanner tape vboxusers video

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