telepathy-logger crashed with SIGSEGV in vfprintf()

[Alexander Kallenbach]

Was just writing and receiving messages.

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: telepathy-logger 0.4.0-0ubuntu1
ProcVersionSignature: Ubuntu 3.2.0-23.36-generic 3.2.14
Uname: Linux 3.2.0-23-generic x86_64
NonfreeKernelModules: nvidia
ApportVersion: 2.0.1-0ubuntu4
Architecture: amd64
Date: Tue Apr 17 18:50:44 2012
ExecutablePath: /usr/lib/telepathy/telepathy-logger
ProcCmdline: /usr/lib/telepathy/telepathy-logger
ProcEnviron:
 SHELL=/bin/bash
 LC_MESSAGES=de_DE.UTF-8
 PATH=(custom, no user)
 LANGUAGE=de_DE:en
 LANG=de_DE.UTF-8
SegvAnalysis:
 Segfault happened at: 0x7f755274adba <vfprintf+10042>: repnz scas %es:(%rdi),%al
 PC (0x7f755274adba) 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:
 vfprintf () from /lib/x86_64-linux-gnu/libc.so.6
 __vasprintf_chk () from /lib/x86_64-linux-gnu/libc.so.6
 g_vasprintf () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 g_strdup_vprintf () from /lib/x86_64-linux-gnu/libglib-2.0.so.0
 _tpl_debug () from /usr/lib/x86_64-linux-gnu/libtelepathy-logger.so.2
Title: telepathy-logger crashed with SIGSEGV in vfprintf()
UpgradeStatus: No upgrade log present (probably fresh install)
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 #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.