the issue is fixed in this update
telepathy-logger (0.2.3-0ubuntu1) natty; urgency=low
* New upstream version fixing some crashers
** Changed in: telepathy-logger (Ubuntu)
Importance: Undecided => Low
** Changed in: telepathy-logger (Ubuntu)
Status: Confirmed => Fix Released
--
Yo
** Changed in: telepathy-logger (Ubuntu)
Status: New => Confirmed
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/725422
Title:
telepathy-logger crashed with SIGSEGV in strchr()
--
ubuntu-bug
Here's another stacktrace, with additional symbols:
StacktraceTop:
strchr () at ../sysdeps/i386/strchr.S:67
g_param_spec_pool_lookup (pool=0x9262140, param_name=0x2 , owner_type=153738496, walk_ancestors=1) at
/build/buildd/glib2.0-2.28.1/./gobject/gparam.c:1053
g_object_new_valist (object_typ
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/725422
Title:
telepathy-logger crashed with SIGSEGV in strchr()
--
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailm
