empathy crashed with SIGSEGV in tp_proxy_get_object_path()

Bug #528474 reported by Greg Grossmeier
52
This bug affects 10 people
Affects Status Importance Assigned to Milestone
empathy (Ubuntu)
Invalid
Medium
Unassigned

Bug Description

Binary package hint: empathy

After resuming from suspend, I tried to close out a chat window that contained 2 conversations of people who were no longer logged in.

ProblemType: Crash
Architecture: amd64
CheckboxSubmission: b503beacb1fcaa6399875cf210a9514e
CheckboxSystem: bb422ca46d02494cdbc459927a98bc2f
CrashCounter: 1
Date: Fri Feb 26 09:24:48 2010
DistroRelease: Ubuntu 10.04
EcryptfsInUse: Yes
ExecutablePath: /usr/bin/empathy
InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Alpha amd64 (20100113)
Package: empathy 2.29.91-1ubuntu1
ProcCmdline: empathy
ProcEnviron:
 SHELL=/bin/bash
 LANG=en_US.utf8
ProcVersionSignature: Ubuntu 2.6.32-14.20-generic
SegvAnalysis:
 Segfault happened at: 0x7fe3d2d75bc5 <tp_proxy_get_object_path+21>: mov 0x30(%rax),%rax
 PC (0x7fe3d2d75bc5) ok
 source "0x30(%rax)" (0x00000030) not located in a known VMA region (needed readable region)!
 destination "%rax" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: empathy
StacktraceTop:
 tp_proxy_get_object_path ()
 ?? ()
 ?? ()
 ?? ()
 ?? ()
Title: empathy crashed with SIGSEGV in tp_proxy_get_object_path()
Uname: Linux 2.6.32-14-generic x86_64
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

Revision history for this message
Greg Grossmeier (greg.grossmeier) wrote :
visibility: private → public
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 tp_proxy_get_object_path (self=<value optimized out>) at proxy.c:1157
 ?? ()
 log_store_empathy_get_dir (
 log_store_empathy_exists (self=0x0,
 empathy_log_manager_exists (

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-amd64-retrace
Revision history for this message
Nicolas DERIVE (kalon33) wrote :

having the same when starting empathy and mission-control-5 has crashed.

Revision history for this message
Noel Arzola (noel.arzola) wrote :

all i did was double click a name to open an im....

Revision history for this message
Omer Akram (om26er) wrote :

thanks for the bug report. is this still an issue?

Changed in empathy (Ubuntu):
status: New → Incomplete
Revision history for this message
John M (jwmwalrus) wrote :

Yes, it's still an issue. I get the crash every time I try to check the history of previous conversations.

$ lsb_release -rd && uname -srvmo

Description: Ubuntu maverick (development branch)
Release: 10.10
Linux 2.6.35-19-generic #28-Ubuntu SMP Sun Aug 29 06:34:38 UTC 2010 x86_64 GNU/Linux

$ apt-cache policy empathy
empathy:
  Installed: 2.31.90-1ubuntu1
  Candidate: 2.31.90-1ubuntu1
  Version table:
 *** 2.31.90-1ubuntu1 0
        500 http://us.archive.ubuntu.com/ubuntu/ maverick/main amd64 Packages
        100 /var/lib/dpkg/status

Revision history for this message
Brian Curtis (bcurtiswx) wrote :

@John M,

Do you have telepathy-logger installed?

Revision history for this message
John M (jwmwalrus) wrote :

Yes, telepathy-logger is installed:

$ apt-cache policy telepathy-logger
telepathy-logger:
  Installed: 0.1.5-1ubuntu1
  Candidate: 0.1.5-1ubuntu1
  Version table:
 *** 0.1.5-1ubuntu1 0
        500 http://us.archive.ubuntu.com/ubuntu/ maverick/main amd64 Packages
        100 /var/lib/dpkg/status

Revision history for this message
Brian Curtis (bcurtiswx) wrote :

@John M. Could you please give me the steps to reproduce so I can try to reproduce this issue with my computer.

Revision history for this message
John M (jwmwalrus) wrote :

With the newest empathy I don't get the crash. It seems that it was one of GNOME's usual upgrade inconsistencies. Not sure if the following is still relevant:

Before upgrade, I deleted everything GNOME-related, in my home directory, except for the following:
$XDG_*_HOME/telepathy
$XDG_*_HOME/Empathy
~/.gconf/apps/empathy
~/.gconf/apps/nautilus_actions
~/.gnome2/gedit
~/.gnome2/keyring
~/.gnome2/accelsgedit (file)
~/.gnome2/gedit-2 (file)
~/.gnome2/gedit-metadata.xml (file)
~/.gnome2/Vim (file)
~/.mission-control
~/.gtk-bookmarks (file)
~/.viminfo (file)
~.vimrc (file)

(I deleted any other directories/files not related to GNOME, except the following: $XDG_*_HOME/exaile, ~/.beagle, ~/.filezilla, ~/.mozilla, ~/.opera, ~/.Skype, ~/.ssh, ~/.thunderbird, ~/.VirtualBox, ~/.xine, ~/.bash*, ~/.pam_environment, ~/.profile)

I did a clean install on the / partition (my /home partition is separate). After the install, empathy worked, except that it always crashed whenever I tried to access the history of conversations. But after yesterday's update, I can no longer reproduce the crash.

$ apt-cache policy empathy telepathy-logger
empathy:
  Installed: 2.31.91.1-0ubuntu2
  Candidate: 2.31.91.1-0ubuntu2
  Version table:
 *** 2.31.91.1-0ubuntu2 0
        500 http://us.archive.ubuntu.com/ubuntu/ maverick/main amd64 Packages
        100 /var/lib/dpkg/status
telepathy-logger:
  Installed: 0.1.5-1ubuntu1
  Candidate: 0.1.5-1ubuntu1
  Version table:
 *** 0.1.5-1ubuntu1 0
        500 http://us.archive.ubuntu.com/ubuntu/ maverick/main amd64 Packages
        100 /var/lib/dpkg/status

Revision history for this message
Brian Curtis (bcurtiswx) wrote :

OK, thanks for the info. I am invalidating this bug. If you experience something in the future, please don't hesitate to report it.

Changed in empathy (Ubuntu):
status: Incomplete → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

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