telepathy-logger crashed with SIGSEGV in strchr()

[Curtis Hovey]

Binary package hint: telepathy-logger

I was logging into canonical and freenode irc. At this moment, I cannot see the menu to join favorite channels.

ProblemType: Crash
DistroRelease: Ubuntu 11.04
Package: telepathy-logger 0.2.1-0ubuntu1
ProcVersionSignature: Ubuntu 2.6.38-5.32-generic 2.6.38-rc6
Uname: Linux 2.6.38-5-generic i686
NonfreeKernelModules: nvidia wl
Architecture: i386
Date: Fri Feb 25 09:30:40 2011
ExecutablePath: /usr/lib/telepathy/telepathy-logger
ProcCmdline: /usr/lib/telepathy/telepathy-logger
ProcEnviron:
 SHELL=/bin/bash
 LANGUAGE=en_US:en
 LANG=en_US.UTF-8
SegvAnalysis:
 Segfault happened at: 0x2f6617 <strchr+23>: mov (%eax),%cl
 PC (0x002f6617) ok
 source "(%eax)" (0x00000002) not located in a known VMA region (needed readable region)!
 destination "%cl" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: telepathy-logger
StacktraceTop:
 strchr () from /lib/libc.so.6
 g_param_spec_pool_lookup () from /usr/lib/libgobject-2.0.so.0
 g_object_new_valist () from /usr/lib/libgobject-2.0.so.0
 g_object_new () from /usr/lib/libgobject-2.0.so.0
 ?? () from /usr/lib/libtelepathy-logger.so.2
Title: telepathy-logger crashed with SIGSEGV in strchr()
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

[Apport retracing service (apport)]

StacktraceTop:
 strchr () at ../sysdeps/i386/strchr.S:67
 g_param_spec_pool_lookup (pool=0x8147140, param_name=0x2 <Address 0x2 out of bounds>, owner_type=135798600, walk_ancestors=1) at /build/buildd/glib2.0-2.28.1/./gobject/gparam.c:1053
 g_object_new_valist (object_type=135798600, first_property_name=0x9a1c22 "account", var_args=<value optimized out>) at /build/buildd/glib2.0-2.28.1/./gobject/gobject.c:1564
 g_object_new (object_type=135798600, first_property_name=0x9a1c22 "account") at /build/buildd/glib2.0-2.28.1/./gobject/gobject.c:1311
 keepon_on_receiving_signal (tpl_text=0x818d808, remote=<value optimized out>, data=0x8180738) at text-channel.c:1184

[Sebastien Bacher (seb128)]

the issue is fixed in this update

telepathy-logger (0.2.3-0ubuntu1) natty; urgency=low

  * New upstream version fixing some crashers