telepathy-indicator crashed with SIGSEGV in handle_contacts_add_indicator_cb()

Bug #947590 reported by Marjeo Delfin on 2012-03-05
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Telepathy Indicator
Ken VanDine
telepathy-indicator (Ubuntu)

Bug Description

I am using Gnome 3.2 shell not unity. When I close a chat message in gnome-shell i got this crash report.

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: telepathy-indicator 0.2.0-0ubuntu1
ProcVersionSignature: Ubuntu 3.2.0-18.28-generic-pae 3.2.9
Uname: Linux 3.2.0-18-generic-pae i686
ApportVersion: 1.94-0ubuntu1
Architecture: i386
Date: Tue Mar 6 07:07:56 2012
ExecutablePath: /usr/bin/telepathy-indicator
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Beta i386 (20120301)
ProcCmdline: telepathy-indicator
 PATH=(custom, no user)
 Segfault happened at: 0x804c269: mov (%eax),%esi
 PC (0x0804c269) ok
 source "(%eax)" (0x00000000) not located in a known VMA region (needed readable region)!
 destination "%esi" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: telepathy-indicator
 ?? ()
 ?? () from /usr/lib/
 ?? () from /usr/lib/
 ?? () from /usr/lib/
 g_source_get_priority () from /lib/i386-linux-gnu/
Title: telepathy-indicator crashed with SIGSEGV in g_source_get_priority()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

Marjeo Delfin (oejramomi) wrote :

 handle_contacts_add_indicator_cb (connection=0x9dc7148, n_contacts=1, contacts=0x9dfd0a0, n_failed=0, failed=0x9e17ea0, err=0x0, user_data=0x9ea0468, weak_object=0x0) at indicator-approver.c:339
 contacts_context_continue (c=0x9ce3d08) at contact.c:1853
 contacts_context_continue (c=0x9ce3d08) at contact.c:1822
 contacts_context_continue (c=0x9ce3d08) at contact.c:1880
 contacts_context_continue (c=0x9ce3d08) at contact.c:1822

Changed in telepathy-indicator (Ubuntu):
importance: Undecided → Medium
summary: - telepathy-indicator crashed with SIGSEGV in g_source_get_priority()
+ telepathy-indicator crashed with SIGSEGV in
+ handle_contacts_add_indicator_cb()
tags: removed: need-i386-retrace
visibility: private → public
Changed in telepathy-indicator:
importance: Undecided → Medium
assignee: nobody → Ken VanDine (ken-vandine)
milestone: none → 0.2.1
status: New → In Progress
Changed in telepathy-indicator:
status: In Progress → Fix Committed
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package telepathy-indicator - 0.2.1-0ubuntu1

telepathy-indicator (0.2.1-0ubuntu1) precise; urgency=low

  * New upstream release
    - Bugs fixed:
      * shows my own nick name in chat notifications, not the one of the
        peer (LP: #926072)
      * Use IndicateInterests to determine if there are listeners, this will
        prevent crashers if telepathy-indicator gets run in gnome-shell or
        other environments without a messaging indicator (LP: #947590)
      * Only autostart in Unity and GNOME classic
      * SIGSEGV in g_file_get_path() (LP: #910785)
      * crashed with signal 5 in g_simple_async_result_complete() (LP: #925829)
      * SIGSEGV in handle_contacts_pending_add_indicator_cb() (LP: #929002)
 -- Ken VanDine <email address hidden> Thu, 22 Mar 2012 11:06:05 -0400

Changed in telepathy-indicator (Ubuntu):
status: New → Fix Released
Changed in telepathy-indicator:
status: Fix Committed → Fix Released
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers