Ubuntu
indicator-messages package

indicator-messages-service crashed with SIGSEGV in g_closure_invoke()

Bug #518547 reported by msieloff
212
This bug affects 18 people
Affects Status Importance Assigned to Milestone
indicator-messages (Ubuntu)
Fix Released
Medium
Unassigned

Bug Description

Binary package hint: indicator-messages

Crashed after start evolution.

ProblemType: Crash
Architecture: i386
Date: Sun Feb 7 22:12:17 2010
DistroRelease: Ubuntu 10.04
ExecutablePath: /usr/lib/indicator-messages/indicator-messages-service
InstallationMedia: Ubuntu 10.04 "Lucid Lynx" - Alpha i386 (20091209)
Package: indicator-messages 0.3.1-0ubuntu1
ProcCmdline: /usr/lib/indicator-messages/indicator-messages-service
ProcEnviron:
 SHELL=/bin/bash
 LANG=de_DE.utf8
ProcVersionSignature: Ubuntu 2.6.32-12.17-generic
SegvAnalysis:
 Segfault happened at: 0x804c4b6: mov 0x14(%edi),%eax
 PC (0x0804c4b6) ok
 source "0x14(%edi)" (0x00000014) not located in a known VMA region (needed readable region)!
 destination "%eax" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: indicator-messages
StacktraceTop:
 ?? ()
 ?? () from /usr/lib/libindicate.so.4
 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
Title: indicator-messages-service crashed with SIGSEGV in g_closure_invoke()
Uname: Linux 2.6.32-12-generic i686
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare vboxusers

Related branches

lp:ubuntu/lucid/indicator-messages
lp:~indicator-applet-developers/indicator-messages/ubuntu
Ken VanDine: Pending requested
Diff: 174 lines (+27/-55)
8 files modified
AUTHORS (+1/-0)
ChangeLog (+12/-0)
configure (+1/-1)
configure.ac (+1/-1)
debian/changelog (+8/-0)
debian/patches/lp_690668.patch (+0/-44)
debian/patches/series (+0/-1)
src/indicator-messages.c (+4/-8)
Revision history for this message
msieloff (m-sieloff-web) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 indicator_added (listener=0x941fc28, server=0x9444a20,
 _indicate_marshal_VOID__POINTER_POINTER (closure=0x941ea18,
 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

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 indicator-messages (Ubuntu):
importance: Undecided → Medium
tags: removed: need-i386-retrace
Sebastien Bacher (seb128)
visibility: private → public
visibility: public → private
visibility: private → public
Revision history for this message
Marien Zwart (marienz) wrote :

I tried to debug this. While I did not understand the attached gdb session (how can sl_item be NULL if serverentry and serverentry->data are not?) I did notice some suspicious code higher up: if serverentry *is* NULL a new *local* sl_item is created and then thrown away, leaving the sl_item in the outer scope NULL. After fixing that I have not crashed yet, but I'm not convinced I actually fixed it (I'm not sure it was 100% reproducable before this).

Revision history for this message
Marien Zwart (marienz) wrote :

This is the change I mentioned in my previous comment. Applying this might make sense even if it does not turn out to fix this crash.

Revision history for this message
Ted Gould (ted) wrote : Re: [Bug 518547] Re: indicator-messages-service crashed with SIGSEGV in g_closure_invoke()

On Tue, 2010-02-09 at 12:27 +0000, Marien Zwart wrote:
> This is the change I mentioned in my previous comment. Applying this
> might make sense even if it does not turn out to fix this crash.

Oh, bummer. I should read my bug mail more :( I came to the same
conclusion and fixed this in trunk. I'm sorry that I didn't notice your
patch. Thank you for taking the time to debug it, I'm pretty sure
that's the issue!

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

This bug was fixed in the package indicator-messages - 0.3.1-0ubuntu2

---------------
indicator-messages (0.3.1-0ubuntu2) lucid; urgency=low

  * Upstream Merge
    * Removing extra ref
    * Moving locally defined variable to use the one defined in
      the function to fix a NULL pointer. (lp: #518547)
 -- Ted Gould <email address hidden> Tue, 09 Feb 2010 09:30:10 -0600

Changed in indicator-messages (Ubuntu):
status: New → Fix Released
Revision history for this message
Sebastien Bacher (seb128) wrote :

the issue might be fixed in 0ubuntu2, could you try once the update is available after session restart to see if that's still an issue?

Changed in indicator-messages (Ubuntu):
status: Fix Released → Incomplete
Revision history for this message
Deactivated User (deactivated-user636007-deactivatedaccount) wrote :

Seems pretty stable after the upgrade.

Brian Murray (brian-murray)
tags: added: patch
Revision history for this message
Brian Murray (brian-murray) wrote :

Setting to Fix Released based on the last comment. In the event that this is not in fact fixed feel free to change the status back to New or Confirmed.

Changed in indicator-messages (Ubuntu):
status: Incomplete → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Duplicates of this bug

Subscribing...

Other bug subscribers

Remote bug watches

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