Ubuntu
unity package

compiz crashed with SIGSEGV in g_cclosure_marshal_VOID__VOID()

Bug #742280 reported by Embridioum
18
This bug affects 4 people
Affects Status Importance Assigned to Milestone
Unity
Fix Released
High
Unassigned
Unity 3.8.4
unity (Ubuntu)
Fix Released
High
Unassigned

Bug Description

Binary package hint: unity

I ran "sudo apt-get update && sudo apt-get -y upgrade && sudo apt-get -y dist-upgrade" at approx. GMT+1 07:50 while checking my Gmail in Firefox.
All windows and the panel disappeared for a few short seconds before they came back accompanied by Apport.
No harm done.

ProblemType: Crash
DistroRelease: Ubuntu 11.04
Package: unity 3.6.8-0ubuntu3
ProcVersionSignature: Ubuntu 2.6.38-7.38-generic 2.6.38
Uname: Linux 2.6.38-7-generic i686
Architecture: i386
CrashCounter: 1
Date: Fri Mar 25 07:42:41 2011
ExecutablePath: /usr/bin/compiz
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Alpha i386 (20110302)
ProcCmdline: compiz
ProcEnviron:
 LANGUAGE=sv_SE:en
 LANG=sv_SE.UTF-8
 SHELL=/bin/bash
Signal: 11
SourcePackage: unity
StacktraceTop:
 ?? () from /usr/lib/compiz/libunityshell.so
 g_cclosure_marshal_VOID__VOID () 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: compiz crashed with SIGSEGV in g_cclosure_marshal_VOID__VOID()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

Revision history for this message
Embridioum (embridioum) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 ?? () from /usr/lib/compiz/libunityshell.so
 g_cclosure_marshal_VOID__VOID (closure=0x8a87d20, return_value=0x0, n_param_values=1, param_values=0xb57cf430, invocation_hint=0xbf881780, marshal_data=0x0) at /build/buildd/glib2.0-2.28.4/./gobject/gmarshal.c:79
 g_closure_invoke (closure=0x8a87d20, return_value=0x0, n_param_values=1, param_values=0xb57cf430, invocation_hint=0xbf881780) at /build/buildd/glib2.0-2.28.4/./gobject/gclosure.c:767
 signal_emit_unlocked_R (node=0x8a98dd0, detail=0, instance=0x8705050, emission_return=0x0, instance_and_params=0xb57cf430) at /build/buildd/glib2.0-2.28.4/./gobject/gsignal.c:3252
 g_signal_emit_valist (instance=0x8705050, signal_id=182, detail=0, var_args=0xbf88193c "0\241\071\a\210\204:\265\210\204:\265h\031\210\277\313P\211\263\300+=\256\360\021=\256p\261q\263`Pp\b\030") 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 unity (Ubuntu):
importance: Undecided → Medium
tags: removed: need-i386-retrace
Sebastien Bacher (seb128)
visibility: private → public
Didier Roche-Tolomelli (didrocks)
Changed in unity:
status: New → Triaged
Changed in unity (Ubuntu):
status: New → Triaged
importance: Medium → High
Changed in unity:
importance: Undecided → High
milestone: none → 3.8.2
Didier Roche-Tolomelli (didrocks)
Changed in unity:
milestone: 3.8.2 → 3.8.4
Revision history for this message
Neil J. Patel (njpatel) wrote :

I believe this is fixed with the work done this week to correctly disconnect signals at destruction. Please re-open if this is still an issue with Unity 3.8.2, thanks.

Changed in unity:
status: Triaged → Fix Released
Changed in unity (Ubuntu):
status: Triaged → 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.