Ubuntu
indicator-messages package

indicator-applet crashed with SIGSEGV in g_closure_invoke()

Bug #352881 reported by BukvA
82
This bug affects 15 people
Affects Status Importance Assigned to Milestone
indicator-messages (Ubuntu)
Fix Released
Medium
Unassigned

Bug Description

Binary package hint: indicator-applet

Description: Ubuntu jaunty (development branch)
Release: 9.04
version: 0.1.4-0ubuntu1

ProblemType: Crash
Architecture: amd64
DistroRelease: Ubuntu 9.04
ExecutablePath: /usr/lib/indicator-applet/indicator-applet
NonfreeKernelModules: nvidia
Package: indicator-applet 0.1.4-0ubuntu1
ProcCmdline: /usr/lib/indicator-applet/indicator-applet --oaf-activate-iid=OAFIID:GNOME_IndicatorApplet_Factory --oaf-ior-fd=42
ProcEnviron:
 LANG=ru_RU.UTF-8
 PATH=(custom, user)
 SHELL=/bin/bash
Signal: 11
SourcePackage: indicator-applet
StacktraceTop:
 ?? () from /usr/lib/libglib-2.0.so.0
 ?? () from /usr/lib/indicators/1/libmessaging.so
 g_closure_invoke ()
 ?? () from /usr/lib/libgobject-2.0.so.0
 g_signal_emit_valist ()
Title: indicator-applet crashed with SIGSEGV in g_closure_invoke()
Uname: Linux 2.6.28-11-generic x86_64
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

Revision history for this message
BukvA (bukva) wrote :
Revision history for this message
Apport retracing service (apport) wrote : Symbolic stack trace

StacktraceTop:g_list_sort_real (list=0x20, compare_func=0x7fbe4afca690 <imList_sort>,
im_time_changed (imitem=0xb37090,
IA__g_closure_invoke (closure=0x8db300,
signal_emit_unlocked_R (node=0x8fcba0, detail=0,
IA__g_signal_emit_valist (instance=0xb37090,

Revision history for this message
Apport retracing service (apport) wrote : Symbolic threaded stack trace
Revision history for this message
Apport retracing service (apport) wrote : Stack trace with source code
Sebastien Bacher (seb128)
visibility: private → public
Changed in indicator-applet (Ubuntu):
importance: Undecided → Medium
Revision history for this message
Jouston Huang (jouston-huang) wrote :

Can confirmed here. I was just disconnected from a 3.5G network(HSDPA) and reconnected to 802.11G network with WPA. Both Pidgin and indicator-applet crashed. They expected to be there but all dead.

Changed in indicator-applet (Ubuntu):
status: New → Confirmed
Ted Gould (ted)
affects: indicator-applet (Ubuntu) → indicator-messages (Ubuntu)
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package indicator-messages - 0.1.5-0ubuntu1

---------------
indicator-messages (0.1.5-0ubuntu1) jaunty; urgency=low

  * New upstream version
    * Fixes the lifecycle of the various structures tracking the messages
      and applications. Fixing bugs like (LP: #355616) (LP: #352881)
    * Fixes the visual appearance by setting the widget name to grab the
      style settings from the main applet. (LP: #351979)
  * debian/control: Upgrading dependency on libindicate-dev to 0.1.5 or
    higher as the new version requires that.

 -- Ted Gould <email address hidden> Fri, 03 Apr 2009 16:32:49 -0500

Changed in indicator-messages (Ubuntu):
status: Confirmed → Fix Released
Revision history for this message
robin0800 (robin-linux-hotmail) wrote :

This bug is still effecting me, but at a guess the culprit is the new revised Konversation which uses Knotify I believe, to talk to this applet.
 So it might be just this combination that causes the crash.

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

Other bug subscribers

Remote bug watches

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