empathy crashed with SIGSEGV in g_object_unref()

Bug #556977 reported by Cristian Aravena Romero
92
This bug affects 21 people
Affects Status Importance Assigned to Milestone
Empathy
Fix Released
Medium
empathy (Ubuntu)
Fix Released
Medium
Ken VanDine

Bug Description

Binary package hint: empathy

Work with empathy and crash.

ProblemType: Crash
DistroRelease: Ubuntu 10.04
Package: empathy 2.30.0-0ubuntu4
ProcVersionSignature: Ubuntu 2.6.32-19.28-generic 2.6.32.10+drm33.1
Uname: Linux 2.6.32-19-generic i686
Architecture: i386
Date: Tue Apr 6 21:11:17 2010
ExecutablePath: /usr/bin/empathy
InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Alpha i386 (20100224.1)
ProcCmdline: empathy
ProcEnviron:
 LANG=es_CL.utf8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x97f23e <g_object_unref+30>: mov (%eax),%eax
 PC (0x0097f23e) ok
 source "(%eax)" (0x00000033) not located in a known VMA region (needed readable region)!
 destination "%eax" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: empathy
StacktraceTop:
 g_object_unref () from /usr/lib/libgobject-2.0.so.0
 free_notification_data (data=0xa332348)
 chat_window_notification_closed_cb (notify=0xa433ad0,
 g_cclosure_marshal_VOID__VOID ()
 g_closure_invoke () from /usr/lib/libgobject-2.0.so.0
Title: empathy crashed with SIGSEGV in g_object_unref()
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
XsessionErrors: (polkit-gnome-authentication-agent-1:1338): GLib-CRITICAL **: g_once_init_leave: assertion `initialization_value != 0' failed

Revision history for this message
Cristian Aravena Romero (caravena) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 g_object_unref () from /usr/lib/libgobject-2.0.so.0
 free_notification_data (data=0xa332348)
 chat_window_notification_closed_cb (notify=0xa433ad0,
 g_cclosure_marshal_VOID__VOID ()
 g_closure_invoke () from /usr/lib/libgobject-2.0.so.0

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
Revision history for this message
Omer Akram (om26er) wrote :

empathy 2.30.0.1 fixes this which should hit lucid soon

Changed in empathy (Ubuntu):
status: New → Fix Committed
visibility: private → public
Changed in empathy (Ubuntu):
assignee: nobody → Ken VanDine (ken-vandine)
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package empathy - 2.30.0.1-0ubuntu1

---------------
empathy (2.30.0.1-0ubuntu1) lucid; urgency=low

  * New upstream version
    - empathy crashed with SIGSEGV in g_closure_invoke() (LP: #527296)
    - contact list is empty for a jabber account with a lot of
      contacts (LP: #539023)
    - Join room should be greyed out for AIM (LP: #540525)
    - Previous/Next Tab menu items aren't disabled if at the first/last tab
      and gtk-keynav-wrap-around is 0
    - empathy incorrectly updates our own IRC nick for /me
    - Shouldn't request RoomList channel if not supported by connection
    - account-chooser crashes when setting a filter and has-all-option to TRUE
    - empathy crashed with SIGSEGV in g_object_unref() (LP: #556977)
    - Wrong account name when using the assistant
    - Empathy fails to initiate a audio/video call over XMPP
  * debian/patches/20_libindicate.patch
    - Ported patch to remove NotificationData, removed upstream
  * debian/patches/32_append_notifications.patch
    - Ported patch to remove NotificationData, removed upstream
  * debian/patches/21_login_indicators.patch
    - Only display indicator for signon events if the preference
      is set (LP: #533857)
 -- Ken VanDine <email address hidden> Fri, 09 Apr 2010 15:07:58 -0400

Changed in empathy (Ubuntu):
status: Fix Committed → Fix Released
Changed in empathy:
status: Unknown → Fix Released
Changed in empathy:
importance: Unknown → Medium
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.