empathy crashed with SIGSEGV in g_closure_invoke()

Bug #435216 reported by khaschuluu
454
This bug affects 115 people
Affects Status Importance Assigned to Milestone
empathy (Ubuntu)
Fix Released
Medium
Ken VanDine
libindicate (Ubuntu)
Invalid
Medium
Ken VanDine

Bug Description

Binary package hint: empathy

empathy crashed with SIGSEGV in g_closure_invoke()

ProblemType: Crash
Architecture: i386
Date: Wed Sep 23 19:42:45 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/bin/empathy
Package: empathy 2.28.0-0ubuntu1
ProcCmdline: empathy
ProcEnviron:
 SHELL=/bin/bash
 LANG=en_US.UTF-8
ProcVersionSignature: Ubuntu 2.6.31-10.35-generic
SegvAnalysis:
 Segfault happened at: 0x806e0e5: jmp *%edx
 PC (0x0806e0e5) ok
 source "*%edx" ok
 Reason could not be automatically determined.
Signal: 11
SourcePackage: empathy
StacktraceTop:
 ?? ()
 g_closure_invoke () from /usr/lib/libgobject-2.0.so.0
 ?? () from /usr/lib/libgobject-2.0.so.0
 g_signal_emit_valist () from /usr/lib/libgobject-2.0.so.0
 g_signal_emit () from /usr/lib/libgobject-2.0.so.0
Title: empathy crashed with SIGSEGV in g_closure_invoke()
Uname: Linux 2.6.31-10-generic i686
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

Revision history for this message
khaschuluu (khaschuluu) wrote :
Revision history for this message
Apport retracing service (apport) wrote : Stacktrace.txt (retraced)

StacktraceTop:empathy_event_activate (event_public=0x9061140)
g_closure_invoke () from /usr/lib/libgobject-2.0.so.0
?? () from /usr/lib/libgobject-2.0.so.0
g_signal_emit_valist () from /usr/lib/libgobject-2.0.so.0
g_signal_emit () from /usr/lib/libgobject-2.0.so.0

Revision history for this message
Apport retracing service (apport) wrote : ThreadStacktrace.txt (retraced)
Changed in empathy (Ubuntu):
importance: Undecided → Medium
tags: removed: need-i386-retrace
security vulnerability: yes → no
visibility: private → public
Revision history for this message
Laurent Bigonville (bigon) wrote :

Looks like a libindicate (or libindicate patch) issue

Revision history for this message
Mikael Frykholm (mikael) wrote :

I got a feeling that this occurs when undocking my laptop.

Revision history for this message
Jeroen Hoek (mail-jeroenhoek) wrote :

This crash happens a lot to me after clicking on the Empathy message indication in Indicator-Applet.

Revision history for this message
Laryllan (laryllan) wrote :

This happend as i tried to rename a logged in account.

Revision history for this message
Pedro Villavicencio (pedro) wrote :

crash due to libindicate, rejecting empathy task.

Changed in libindicate (Ubuntu):
importance: Undecided → Medium
Changed in empathy (Ubuntu):
status: New → Invalid
Changed in libindicate (Ubuntu):
status: New → Confirmed
Changed in libindicate (Ubuntu):
assignee: nobody → Ken VanDine (ken-vandine)
Revision history for this message
liamdawe (liamdawe) wrote :

I can confirm this bug, i tried closing and window, and it will still in the notification list, went to click on it and all hell broke lose.

Revision history for this message
Pete Graner (pgraner) wrote :

Attaching empathy log gathered with: EMPATHY_LOGFILE=/tmp/empathy.log EMPATHY_DEBUG=all NICE_DEBUG=all empathy

Last two lines are right before the segfault

Revision history for this message
Michael (michaeljt) wrote :

Me too, trying to open an IRC nickserv window.

Revision history for this message
Mark A. Hershberger (hexmode) wrote :

Just got this after clicking the indicator

Revision history for this message
Naresh V (nareshov) wrote : Re: [Bug 435216] Re: empathy crashed with SIGSEGV in g_closure_invoke()

2009/10/7 Mark A. Hershberger <email address hidden>:
> Just got this after clicking the indicator
>

Me too. After clicking on the nick that wants our attention in the
indicator-applet.

Revision history for this message
Sokolov Sergey (cleversokol-deactivatedaccount) wrote :

Confirm this bug on amd64

Revision history for this message
Ken VanDine (ken-vandine) wrote :

Fixed patch pushed to lp:~ubuntu-desktop/empathy/ubuntu

Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package empathy - 2.28.0.1-1ubuntu3

---------------
empathy (2.28.0.1-1ubuntu3) karmic; urgency=low

  * debian/patches/20_libindicate.patch
    - Fixed a crasher caused by not properly removing
      indicators. When comparing events, we shouldn't compare
      the message content. (LP: #435216)

 -- Ken VanDine <email address hidden> Wed, 07 Oct 2009 17:19:48 -0400

Changed in empathy (Ubuntu):
status: Invalid → Fix Released
Changed in libindicate (Ubuntu):
status: Confirmed → Invalid
Changed in empathy (Ubuntu):
status: Fix Released → Fix Committed
Changed in empathy (Ubuntu):
assignee: nobody → Ken VanDine (ken-vandine)
status: Fix Committed → Fix Released
tags: added: iso-testing
Revision history for this message
tmsbrdrs (tmsbrdrs) wrote :

just encountered this bug after updating packages on amd64 ubuntu lucid lynx.

Revision history for this message
Tiede (marcarthur) wrote :

I am not sure if the fix is there...
I noticed this bug today, by clicking on the notification area applet while using a chat window. Apparently, the indicator applet was warning me about a new IM message, which in itself was strange, since I had the IM window focused, and it is my understanding that this would make the messages not "new" anymore...
Thinking maybe I must have missed something, I clicked on the applet, selected the conversation (which was already opened, mind you), and banm! crash.
I have not yet been able to reproduce it.
Current empathy version: 2.30.2

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.