telepathy-logger crashed with SIGSEGV in strchr()

[David Planella]

Binary package hint: telepathy-logger

I got a new crash with Version: 0.2.3-0ubuntu1

I've had a look at bug 725422 and bug 725015, but unlike here, in those cases it seems that the issue was fixed with that upload.

ProblemType: Crash
DistroRelease: Ubuntu 11.04
Package: telepathy-logger 0.2.3-0ubuntu1
ProcVersionSignature: Ubuntu 2.6.38-5.32-generic 2.6.38-rc6
Uname: Linux 2.6.38-5-generic i686
Architecture: i386
Date: Thu Mar 3 09:46:48 2011
EcryptfsInUse: Yes
ExecutablePath: /usr/lib/telepathy/telepathy-logger
ProcCmdline: /usr/lib/telepathy/telepathy-logger
ProcEnviron:
 SHELL=/bin/bash
 LANGUAGE=ca:en_GB:en
 LANG=ca_ES.utf8
SegvAnalysis:
 Segfault happened at: 0x357617 <strchr+23>: mov (%eax),%cl
 PC (0x00357617) 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 () at ../sysdeps/i386/strchr.S:67
 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()
UpgradeStatus: Upgraded to natty on 2010-12-20 (72 days ago)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

[Omer Akram (om26er)]

I have opened a new upstream bug for the latest version. If you are able to reproduce this bug a backtrace would be really helpful, also it seems the issue is specific to 32-bit installs.

[Omer Akram (om26er)]

It seems there is a new upstream release which fixes another 32-bit crash.. Upstream again recommends.

* Add output annotations in TplLogManager (Jasper)
* Make the introspection files be 0.2 instead of 1.0 (Emilio)
* Fix use of uninitialised variable (Nicolas)
* Remove reference to Gnome in configure.ac (Nicolas)
* Remove GPL warning in README, Logger is now fully LGPL (Nicolas)
* Move observer and SQlite tests with dbus enabled tests (Nicolas)
* Update valgrind suppressions. (Nicolas)
* Fix XML store test crash on 32bit computer. (Nicolas)

[Andrea Carpineti (acarpine)]

Hi Omer, I updated my system just some minutes ago but it seems that the latest version is still the 0.2.3-0ubuntu1 version. The new upstream release which you are talking about is already available for Ubuntu? Also looking at http://packages.debian.org/changelogs/pool/main/t/telepathy-logger/telepathy-logger_0.2.3-1/changelog seems that the latest version is 0.2.3 seems that the latest Debian version is 0.2.3-1 with the comment * New upstream release. Tks Omer

[Omer Akram (om26er)]

it seems its not packaged in debian yet. the latest release is 0.2.4 which
came on 1st March a little after the 0.2.3 update was uploaded to natty
http://telepathy.freedesktop.org/releases/telepathy-logger/

On Thu, Mar 3, 2011 at 5:31 PM, Andrea Carpineti <email address hidden>wrote:

> Hi Omer, I updated my system just some minutes ago but it seems that the
> latest version is still the 0.2.3-0ubuntu1 version. The new upstream
> release which you are talking about is already available for Ubuntu?
> Also looking at http://packages.debian.org/changelogs/pool/main/t
> /telepathy-logger/telepathy-logger_0.2.3-1/changelog seems that the
> latest version is 0.2.3 seems that the latest Debian version is 0.2.3-1
> with the comment * New upstream release. Tks Omer
>
> --
> You received this bug notification because you are a member of
> Telepathy, which is subscribed to telepathy-logger in ubuntu.
> https://bugs.launchpad.net/bugs/728302
>
> Title:
> telepathy-logger crashed with SIGSEGV in strchr()
>
> --
> Ubuntu-telepathy mailing list
> <email address hidden>
> Modify settings or unsubscribe at:
> https://lists.ubuntu.com/mailman/listinfo/ubuntu-telepathy
>

[Nicolas-dufresne (nicolas-dufresne)]

Just a reminder, you backtrace does not contain debug symbols, and you opened an upstream bug without the basic information:

1) Instruction to reproduce
2) System architecture (32bit/64bit if Intel)
3) Dependency version, especially GLib in this case

Note that I'm trying to be kind now, but we usually don't like to go back and forth from freedesktop bugzilla to launchpad bug system.

[Brian Curtis (bcurtiswx)]

Thanks Nicolas,

Omer, make sure that the bug report is reproducable with steps to reproduce, as well as provides Nicolas's information before reporting upstream. Could the reporter please give us a list of steps to reproduce, as well as the version of GLib you are using. The system arch is in the original report as i386. (32 bit)

[Omer Akram (om26er)]

I have build tp-logger with the fix that telepathy developers believe should fix this issue. Could anyone facing the issue please try this ppa https://launchpad.net/~om26er/+archive/unity and see if the telepathy-logger from the ppa fix the issue.

and there are no steps to reproduce the issue. it can happen in different situations it seems.

[David Planella (dpm)]

Hi Brian, Nicolas,

Let me address your questions:

* Steps to reproduce: none, this seems to happen at random, either opening a chat window in empathy, or in the middle of a conversation

* Glib version: it's listed on the Dependencies.txt file attached on the original post. It's libglib2.0-0 2.28.1-1ubuntu1

Thanks.

[Andrea Carpineti (acarpine)]

I'm experiencing a similar problem (maybe same). I will try to answer to the
questions raised to complete the investigation:
1) In my case the crash occurs launching Empathy (Application -> Internet ->
Empathy).
I saw the main empathy window, the opening of my favorite chats and then the
apport's window with the crash of the telepathy-logger.
2) I have an AMD notebook that runs Natty i386 (more in my attachment
apport-retrace.txt)
3) I thought they were in the Dependencies.txt attachment anyway I added a
second attach with the result of the command dpkg -l *glib*

I hope my apport-retrace.txt contains a valid trace. I obtained it through
the apport-retrace command.
Thanks for your indications.

PS: I still haven't tried the PPA suggested by Omer

[Nicolas-dufresne (nicolas-dufresne)]

Omer Akram, sorry if that message was a little unclear, I meant correctly giving details to freedesktop.org bug next time.

I released 0.2.5 that should address a crasher similar to your issue, so please update.

[Omer Akram (om26er)]

telepathy-logger 0.2.5 is now in natty.