telepathy-indicator crashed with SIGSEGV in g_file_get_path()

Bug #910785 reported by Johan Sandelin on 2012-01-02
This bug affects 2 people
Affects Status Importance Assigned to Milestone
Telepathy Indicator
Ken VanDine
telepathy-indicator (Ubuntu)
Ken VanDine

Bug Description

The crash occurrs when starting empathy.

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: telepathy-indicator 0.1.0-0ubuntu1
ProcVersionSignature: Ubuntu 3.2.0-7.13-generic-pae 3.2.0-rc7
Uname: Linux 3.2.0-7-generic-pae i686
ApportVersion: 1.90-0ubuntu1
Architecture: i386
CrashCounter: 1
Date: Mon Jan 2 11:35:17 2012
ExecutablePath: /usr/bin/telepathy-indicator
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Alpha i386 (20111226)
ProcCmdline: telepathy-indicator
 Segfault happened at: 0xb73a639d <g_file_get_path+45>: mov (%esi),%edi
 PC (0xb73a639d) ok
 source "(%esi)" (0x6b736564) not located in a known VMA region (needed readable region)!
 destination "%edi" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: telepathy-indicator
 g_file_get_path () from /usr/lib/i386-linux-gnu/
 ?? ()
 ?? () from /usr/lib/
 ?? () from /usr/lib/
 ?? () from /usr/lib/
Title: telepathy-indicator crashed with SIGSEGV in g_file_get_path()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

 g_file_get_path (file=0x6b736564) at /build/buildd/glib2.0-2.31.4.tested/./gio/gfile.c:452
 handle_contacts_add_indicator_cb (connection=0x8c7d0b0, n_contacts=0, contacts=0x8c80660, n_failed=1, failed=0x8c761c0, err=0x0, user_data=0x8c81920, weak_object=0x0) at indicator-approver.c:158
 contacts_context_continue (c=0x8c56f88) at contact.c:1851
 contacts_context_continue (c=0x8c56f88) at contact.c:1820
 contacts_got_attributes (user_data=0x8c56f88, attributes=0x8c8eea8, connection=0x8c7d0b0, error=<optimized out>, weak_object=<optimized out>) at contact.c:3841

Changed in telepathy-indicator (Ubuntu):
importance: Undecided → Medium
tags: removed: need-i386-retrace
Bilal Shahid (s9iper1) on 2012-02-29
visibility: private → public
Bilal Shahid (s9iper1) wrote :

assigning to kenvandine as he said to me

Changed in telepathy-indicator (Ubuntu):
assignee: nobody → Ken VanDine (ken-vandine)
status: New → Triaged
Ken VanDine (ken-vandine) wrote :
Changed in telepathy-indicator:
assignee: nobody → Ken VanDine (ken-vandine)
status: New → In Progress
milestone: none → 0.2.1
importance: Undecided → Medium
Changed in telepathy-indicator:
status: In Progress → Fix Committed
Changed in telepathy-indicator:
status: Fix Committed → Fix Released
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: Triaged → Fix Released
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers