compiz crashed with SIGSEGV in g_closure_invoke()

Bug #751371 reported by jose ribeiro neto
12
This bug affects 1 person
Affects Status Importance Assigned to Milestone
compiz (Ubuntu)
New
Medium
Unassigned

Bug Description

Binary package hint: compiz

was using the so normally and suddenly as if somebody had accessed the machine work area closed and opened again

ProblemType: Crash
DistroRelease: Ubuntu 11.04
Package: compiz-core 1:0.9.4git20110322-0ubuntu5
ProcVersionSignature: Ubuntu 2.6.38-7.39-generic 2.6.38
Uname: Linux 2.6.38-7-generic x86_64
Architecture: amd64
Date: Tue Apr 5 10:20:33 2011
Disassembly: => 0x1: Não é possível acessar a memória no endereço 0x1
ExecutablePath: /usr/bin/compiz
InstallationMedia: Ubuntu 10.04.1 LTS "Lucid Lynx" - Release amd64 (20100816.1)
InstallationMedia_: Ubuntu 10.04.1 LTS "Lucid Lynx" - Release amd64 (20100816.1)
ProcCmdline: compiz
ProcEnviron:
 LANGUAGE=pt_BR:en
 LANG=pt_BR.UTF-8
 SHELL=/bin/bash
ProcVersionSignature_: Ubuntu 2.6.38-7.39-generic 2.6.38
SegvAnalysis:
 Segfault happened at: 0x1: Não é possível acessar a memória no endereço 0x1
 PC (0x00000001) not located in a known VMA region (needed executable region)!
 source "0x1" (0x00000001) not located in a known VMA region (needed readable region)!
SegvReason:
 executing NULL VMA
 reading NULL VMA
Signal: 11
SourcePackage: compiz
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
Title: compiz crashed with SIGSEGV in g_closure_invoke()
UpgradeStatus: Upgraded to natty on 2011-04-05 (0 days ago)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

Revision history for this message
jose ribeiro neto (hk-neto) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 ?? () at /usr/include/c++/4.5/bits/vector.tcc:295
 closure_invoke_notifiers (closure=0x2000000, return_value=0x0, n_param_values=4, param_values=0x7fd264499920, invocation_hint=0x7fff9c7d4cc0) at /build/buildd/glib2.0-2.28.5/./gobject/gclosure.c:289
 g_closure_invoke (closure=0x2000000, return_value=0x0, n_param_values=4, param_values=0x7fd264499920, invocation_hint=0x7fff9c7d4cc0) at /build/buildd/glib2.0-2.28.5/./gobject/gclosure.c:773
 signal_emit_unlocked_R (node=<value optimized out>, detail=0, instance=0x10d7d80, emission_return=0x0, instance_and_params=0x7fd264499920) at /build/buildd/glib2.0-2.28.5/./gobject/gsignal.c:3252
 g_signal_emit_valist (instance=<value optimized out>, signal_id=<value optimized out>, detail=<value optimized out>, var_args=<value optimized out>) at /build/buildd/glib2.0-2.28.5/./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 compiz (Ubuntu):
importance: Undecided → Medium
tags: removed: need-amd64-retrace
tags: added: compiz-0.9
security vulnerability: yes → no
visibility: private → public
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.