empathy crashed with SIGSEGV in tp_proxy_get_object_path()

Bug #766936 reported by Nguyen Phuc Nguyen
18
This bug affects 2 people
Affects Status Importance Assigned to Milestone
Empathy
Invalid
Undecided
Unassigned
folks
Fix Released
Critical
folks (Ubuntu)
Fix Released
Medium
Unassigned
Declined for Natty by Jeremy Bícha

Bug Description

Binary package hint: empathy

suddenly crashed

ProblemType: Crash
DistroRelease: Ubuntu 11.04
Package: empathy 2.34.0-0ubuntu3
ProcVersionSignature: Ubuntu 2.6.38-8.42-generic 2.6.38.2
Uname: Linux 2.6.38-8-generic i686
Architecture: i386
Date: Wed Apr 20 15:32:23 2011
ExecutablePath: /usr/bin/empathy
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release i386 (20101007)
ProcCmdline: empathy
ProcEnviron:
 SHELL=/bin/bash
 LANGUAGE=en_US:en
 LANG=en_US.UTF-8
SegvAnalysis:
 Segfault happened at: 0x677596 <tp_proxy_get_object_path+38>: mov 0x18(%eax),%eax
 PC (0x00677596) ok
 source "0x18(%eax)" (0x00000018) not located in a known VMA region (needed readable region)!
 destination "%eax" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: empathy
StacktraceTop:
 tp_proxy_get_object_path () from /usr/lib/libtelepathy-glib.so.0
 ?? ()
 ?? ()
 ?? () from /usr/lib/libgtk-x11-2.0.so.0
 gtk_tree_store_insert_with_values () from /usr/lib/libgtk-x11-2.0.so.0
Title: empathy crashed with SIGSEGV in tp_proxy_get_object_path()
UpgradeStatus: Upgraded to natty on 2011-04-05 (14 days ago)
UserGroups: adm admin cdrom dialout libvirtd lpadmin plugdev sambashare

Revision history for this message
Nguyen Phuc Nguyen (nguyennp) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 tp_proxy_get_object_path (self=0x0) at proxy.c:1338
 individual_store_contact_sort (individual_a=0xb1cc79e0, individual_b=0xaa6b760) at empathy-individual-store.c:1380
 individual_store_state_sort_func (model=0xa1da818, iter_a=0xbfa36e0c, iter_b=0xbfa36c90, user_data=0xa1da818) at empathy-individual-store.c:1447
 gtk_tree_store_sort_iter_changed (tree_store=<value optimized out>, iter=0xbfa36e0c, column=5, emit_signal=0) at /build/buildd/gtk+2.0-2.24.4/gtk/gtktreestore.c:3019
 IA__gtk_tree_store_insert_with_values (tree_store=0xa1da818, iter=0xbfa36e0c, parent=0xbfa36dfc, position=0) at /build/buildd/gtk+2.0-2.24.4/gtk/gtktreestore.c:1453

Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt
Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt
Changed in empathy (Ubuntu):
importance: Undecided → Medium
tags: removed: need-i386-retrace
Omer Akram (om26er)
visibility: private → public
Revision history for this message
Omer Akram (om26er) wrote :

Thank you for your bug report. This bug has been reported to the developers of the software. You can track it and make comments at: https://bugzilla.gnome.org/show_bug.cgi?id=648847

Changed in empathy (Ubuntu):
status: New → Triaged
Changed in empathy:
importance: Unknown → Medium
status: Unknown → New
Revision history for this message
Omer Akram (om26er) wrote :
Changed in empathy:
importance: Medium → Unknown
status: New → Unknown
affects: empathy (Ubuntu) → folks (Ubuntu)
Changed in folks (Ubuntu):
assignee: nobody → Omer Akram (om26er)
status: Triaged → Confirmed
Changed in empathy:
importance: Unknown → Undecided
status: Unknown → New
status: New → Invalid
Changed in folks:
importance: Unknown → Critical
status: Unknown → Fix Released
Revision history for this message
Omer Akram (om26er) wrote :

unassigning myself as it seem folks fails to build with these two branches applied.

Changed in folks (Ubuntu):
assignee: Omer Akram (om26er) → nobody
Jeremy Bícha (jbicha)
Changed in folks (Ubuntu):
status: Confirmed → Fix Released
Revision history for this message
Jeremy Bícha (jbicha) wrote :

This has been fixed in folks 0.4.3 and newer which means it is now fixed in all supported versions of Ubuntu.

See this document for currently supported Ubuntu releases: https://wiki.ubuntu.com/Releases

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.