indicator-applet-complete crashed with SIGSEGV in g_cclosure_marshal_VOID__POINTER()

Bug #745115 reported by Ivan
146
This bug affects 35 people
Affects Status Importance Assigned to Milestone
Indicator Applet
Fix Released
High
Unassigned
Unity Foundations
Fix Released
Medium
Michael Terry
indicator-applet (Ubuntu)
Fix Released
Medium
Michael Terry
Natty
Fix Released
Medium
Michael Terry

Bug Description

Binary package hint: indicator-applet

indicator-applet-complete crashed with SIGSEGV in g_cclosure_marshal_VOID__POINTER()

ProblemType: Crash
DistroRelease: Ubuntu 11.04
Package: indicator-applet 0.4.10-0ubuntu1
ProcVersionSignature: Ubuntu 2.6.38-7.39-generic-pae 2.6.38
Uname: Linux 2.6.38-7-generic-pae i686
Architecture: i386
Date: Tue Mar 29 21:20:51 2011
ExecutablePath: /usr/lib/indicator-applet/indicator-applet-complete
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Beta 1 i386 (20110329.1)
ProcCmdline: /usr/lib/indicator-applet/indicator-applet-complete
ProcEnviron:
 SHELL=/bin/bash
 LANGUAGE=ru_RU:en
 LANG=ru_RU.UTF-8
SegvAnalysis:
 Segfault happened at: 0x804bba1: cmp %eax,(%edx)
 PC (0x0804bba1) ok
 source "%eax" ok
 destination "(%edx)" (0x00000018) not located in a known VMA region (needed writable region)!
SegvReason: writing NULL VMA
Signal: 11
SourcePackage: indicator-applet
StacktraceTop:
 ?? ()
 g_cclosure_marshal_VOID__POINTER () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0
 g_closure_invoke () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0
 ?? () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0
 g_signal_emit_valist () from /usr/lib/i386-linux-gnu/libgobject-2.0.so.0
Title: indicator-applet-complete crashed with SIGSEGV in g_cclosure_marshal_VOID__POINTER()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

Related branches

Revision history for this message
Ivan (v-evrei) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 ?? ()
 g_cclosure_marshal_VOID__POINTER (closure=0x9fabd10, return_value=0x0, n_param_values=2, param_values=0x9ed92f0, invocation_hint=0xbfceb480, marshal_data=0x0) at /build/buildd/glib2.0-2.28.4/./gobject/gmarshal.c:603
 g_closure_invoke (closure=0x9fabd10, return_value=0x0, n_param_values=2, param_values=0x9ed92f0, invocation_hint=0xbfceb480) at /build/buildd/glib2.0-2.28.4/./gobject/gclosure.c:767
 signal_emit_unlocked_R (node=0x9f13e78, detail=0, instance=0x9ef8520, emission_return=0x0, instance_and_params=0x9ed92f0) at /build/buildd/glib2.0-2.28.4/./gobject/gsignal.c:3252
 g_signal_emit_valist (instance=0x9ef8520, signal_id=225, detail=0, var_args=0xbfceb640 "\001") at /build/buildd/glib2.0-2.28.4/./gobject/gsignal.c:2983

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-applet (Ubuntu):
importance: Undecided → Medium
tags: removed: need-i386-retrace
Revision history for this message
Sebastien Bacher (seb128) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. Please try to obtain a backtrace following the instructions at http://wiki.ubuntu.com/DebuggingProgramCrash and upload the backtrace (as an attachment) to the bug report. This will greatly help us in tracking down your problem.

security vulnerability: yes → no
visibility: private → public
Changed in indicator-applet (Ubuntu):
importance: Medium → Low
status: New → Incomplete
affects: indicator-applet (Ubuntu) → indicator-application (Ubuntu)
Changed in indicator-application (Ubuntu):
status: Incomplete → Confirmed
importance: Low → High
Changed in indicator-application:
importance: Undecided → High
status: New → Confirmed
Changed in indicator-application (Ubuntu Natty):
assignee: nobody → Michael Terry (mterry)
Revision history for this message
Michael Terry (mterry) wrote :

Well, this looks like a crash in entry_added in indicator-applet as a result of indicator-application sending a INDICATOR_OBJECT_SIGNAL_ENTRY_ADDED signal. Not sure who's at fault yet. The fact that the top frame of the stack trace is missing is bad because it's hard to tell where in entry_added we crashed.

Martin Pitt (pitti)
Changed in indicator-application (Ubuntu Natty):
importance: High → Medium
Revision history for this message
Sebastien Bacher (seb128) wrote :

the bug has recent duplicates but they lack the first frame as well for some reason

David Barth (dbarth)
Changed in unity-foundations:
milestone: none → unity-3.8.6
importance: Undecided → Medium
assignee: nobody → Michael Terry (mterry)
status: New → Confirmed
Revision history for this message
Michael Terry (mterry) wrote :

These traces are uniform but bizarre. They all seem to be during the processing of an ApplicationIconChanged signal, but the stack trace shows the local variables as if it were handling a ApplicationLabelChanged signal, and even shows a application_label_changed() call (with the wrong function signature) in the stack.

But the variable contents and the signal name itself point to ApplicationIconChanged being the actual signal. I think I trust those data points slightly more than I trust gdb's after-the-fact processing of the stack. That combined with the bottom frame always missing points to some stack corruption. It's just odd that it's so uniform across the duplicates.

Revision history for this message
Michael Terry (mterry) wrote :

Progress, I think. Noting that all the crashes are only in classic GNOME and that the signal may really be IconChanged, I looked at what we send on to the indicator-applet when that happens. And I found code that *could* crash, once an appicon goes away and a second appicon changes its icon. I'll file a merge request and claim this is fixed, but the proof will be once we stop getting bug reports about it.

Ted Gould (ted)
affects: indicator-application → indicator-applet
affects: indicator-application (Ubuntu Natty) → indicator-applet (Ubuntu Natty)
Changed in indicator-applet:
status: Confirmed → Fix Committed
milestone: none → 0.4.11
Ted Gould (ted)
Changed in indicator-applet:
status: Fix Committed → Fix Released
Changed in indicator-applet (Ubuntu Natty):
status: Confirmed → Fix Committed
Changed in unity-foundations:
status: Confirmed → Fix Committed
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package indicator-applet - 0.4.12-0ubuntu1

---------------
indicator-applet (0.4.12-0ubuntu1) natty; urgency=low

  * New upstream release.
    * Adding in translations from Launchpad (LP: #760680)
    ∘ Handle updating accessible descriptions globally rather than
      once per entry (LP: #745115)
 -- Ted Gould <email address hidden> Thu, 14 Apr 2011 21:49:24 -0500

Changed in indicator-applet (Ubuntu Natty):
status: Fix Committed → Fix Released
Changed in unity-foundations:
status: Fix Committed → Fix Released
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.