unity-panel-service crashed with SIGSEGV in g_closure_invoke()

Bug #809865 reported by Alessandro Losavio
302
This bug affects 143 people
Affects Status Importance Assigned to Milestone
Indicator Display Objects
Fix Released
Critical
Robert Carr
Unity
Fix Released
Critical
Robert Carr
unity (Ubuntu)
Fix Released
Critical
Robert Carr

Bug Description

- Ubuntu 11.10 amd64

When sending an e-mail with Thunderbird, I was with the pointer on the bar Unity and immediately appeared to me a crash

ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: unity-services 4.2.0-0ubuntu2
ProcVersionSignature: Ubuntu 3.0-3.4-generic 3.0.0-rc5
Uname: Linux 3.0-3-generic x86_64
Architecture: amd64
CrashCounter: 1
Date: Wed Jul 13 15:01:27 2011
ExecutablePath: /usr/lib/unity/unity-panel-service
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Alpha amd64 (20110705.1)
ProcCmdline: /usr/lib/unity/unity-panel-service
ProcEnviron:
 SHELL=/bin/bash
 LANG=it_IT.UTF-8
SegvAnalysis:
 Segfault happened at: 0x7ff0e0153d57 <g_closure_invoke+39>: callq 0x7ff0e0153470 <g_closure_ref>
 PC (0x7ff0e0153d57) ok
 source "0x7ff0e0153470" (0x7ff0e0153470) ok
 destination "(%rsp)" (0x7fff52cc2000) not located in a known VMA region (needed writable region)!
 Stack memory exhausted (SP below stack segment)
SegvReason: writing unknown VMA
Signal: 11
SourcePackage: unity
StacktraceTop:
 g_closure_invoke () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 ?? () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 g_signal_emit_valist () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 g_signal_emit () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
 ?? () from /usr/lib/libgtk-3.so.0
Title: unity-panel-service crashed with SIGSEGV in g_closure_invoke()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

Revision history for this message
Alessandro Losavio (alo21) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 g_closure_invoke (closure=0x17d0f40, return_value=0x0, n_param_values=2, param_values=0x683ff60, invocation_hint=0x7fff52cc2140) at /build/buildd/glib2.0-2.29.10/./gobject/gclosure.c:751
 signal_emit_unlocked_R (node=<value optimized out>, detail=0, instance=0x1bb2010, emission_return=0x0, instance_and_params=0x683ff60) at /build/buildd/glib2.0-2.29.10/./gobject/gsignal.c:3186
 g_signal_emit_valist (instance=<value optimized out>, signal_id=<value optimized out>, detail=<value optimized out>, var_args=0x7fff52cc2328) at /build/buildd/glib2.0-2.29.10/./gobject/gsignal.c:2987
 g_signal_emit (instance=<value optimized out>, signal_id=<value optimized out>, detail=<value optimized out>) at /build/buildd/glib2.0-2.29.10/./gobject/gsignal.c:3044
 gtk_grab_notify_foreach (child=0x1bb2010, data=0x7fff52cc25e0) at /build/buildd/gtk+3.0-3.1.8/./gtk/gtkmain.c:2098

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 unity (Ubuntu):
importance: Undecided → Medium
tags: removed: need-amd64-retrace
visibility: private → public
Changed in unity (Ubuntu):
importance: Medium → Critical
Changed in unity (Ubuntu):
status: New → Confirmed
Changed in unity:
status: New → Confirmed
Revision history for this message
Kody Ivan McCarthy (kodykodiak) wrote :

Also occurred for me when clicking Insert in the LibreOffice Calc global menu bar. Program and Unity frozen temporarily, then kicked back the crash report.

Revision history for this message
Clint Byrum (clint-fewbar) wrote :

this happens constantly to me, seemingly at random, in unity-2d and regular unity.

tags: removed: amd64
Neil J. Patel (njpatel)
tags: added: rls-mgr-o-tracking
tags: added: iso-testing
Changed in unity (Ubuntu):
milestone: none → ubuntu-11.10-beta-2
Neil J. Patel (njpatel)
Changed in unity:
importance: Undecided → Critical
assignee: nobody → Robert Carr (robertcarr)
Changed in unity (Ubuntu):
assignee: nobody → Robert Carr (robertcarr)
Changed in ido:
assignee: nobody → Robert Carr (robertcarr)
importance: Undecided → Critical
status: New → Triaged
status: Triaged → Confirmed
Revision history for this message
Robert Carr (robertcarr) wrote :

This should be fixed with the next ido release and the retooling of the idorange code.

Changed in ido:
status: Confirmed → Fix Committed
Changed in unity:
status: Confirmed → Fix Committed
Changed in unity (Ubuntu):
status: Confirmed → Fix Committed
Robert Carr (robertcarr)
Changed in ido:
status: Fix Committed → Fix Released
Changed in unity (Ubuntu):
status: Fix Committed → Fix Released
Changed in unity:
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.