compiz crashed with SIGSEGV in g_type_check_instance() from g_signal_emit_valist() from g_signal_emit() from ... from CcpScreen::timeout()

Bug #932382 reported by Manol Em
300
This bug affects 37 people
Affects Status Importance Assigned to Milestone
Compiz
Triaged
High
Unassigned
Compiz Configuration Library - GConf Backend
Triaged
High
Unassigned
compizconfig-backend-gconf (Ubuntu)
Triaged
High
Unassigned

Bug Description

CCSM compiz config settings manager crashed upon startup

ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: compiz-core 1:0.9.7.0~bzr2995-0ubuntu1
ProcVersionSignature: Ubuntu 3.2.0-15.24-generic 3.2.5
Uname: Linux 3.2.0-15-generic x86_64
ApportVersion: 1.91-0ubuntu1
Architecture: amd64
Date: Wed Feb 15 00:12:54 2012
DistroCodename: precise
DistroVariant: ubuntu
ExecutablePath: /usr/bin/compiz
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Alpha amd64 (20120201.1)
ProcCmdline: compiz
ProcEnviron:
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x7fe5c3505175 <g_type_check_instance+21>: mov (%rax),%rdi
 PC (0x7fe5c3505175) ok
 source "(%rax)" (0xffff0000) not located in a known VMA region (needed readable region)!
 destination "%rdi" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: compiz
StacktraceTop:
 g_type_check_instance () 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/x86_64-linux-gnu/libdbus-glib-1.so.2
 g_closure_invoke () from /usr/lib/x86_64-linux-gnu/libgobject-2.0.so.0
Title: compiz crashed with SIGSEGV in g_type_check_instance()
UpgradeStatus: Upgraded to precise on 2012-02-14 (0 days ago)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo

Revision history for this message
Manol Em (manolem) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 g_type_check_instance (type_instance=0x18cfdc0) at /build/buildd/glib2.0-2.31.16/./gobject/gtype.c:4072
 g_signal_emit_valist (instance=0x18cfdc0, signal_id=224, detail=0, var_args=0x7fff0feccc58) at /build/buildd/glib2.0-2.31.16/./gobject/gsignal.c:2966
 g_signal_emit (instance=<optimized out>, signal_id=<optimized out>, detail=<optimized out>) at /build/buildd/glib2.0-2.31.16/./gobject/gsignal.c:3090
 ?? ()
 ?? () from /tmp/tmp05lHgY/lib/x86_64-linux-gnu/libglib-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 compiz (Ubuntu):
importance: Undecided → Medium
tags: removed: need-amd64-retrace
tags: added: compiz-0.9
summary: - compiz crashed with SIGSEGV in g_type_check_instance()
+ compiz crashed with SIGSEGV in g_type_check_instance() from
+ g_signal_emit_valist() from g_signal_emit()
Revision history for this message
Launchpad Janitor (janitor) wrote : Re: compiz crashed with SIGSEGV in g_type_check_instance() from g_signal_emit_valist() from g_signal_emit()

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in compiz (Ubuntu):
status: New → Confirmed
Changed in compiz-core:
status: New → Confirmed
Changed in compiz (Ubuntu):
status: Confirmed → Triaged
visibility: private → public
Revision history for this message
Daniel van Vugt (vanvugt) wrote :

I think this might be fixed by the fix for bug 932125.

summary: compiz crashed with SIGSEGV in g_type_check_instance() from
- g_signal_emit_valist() from g_signal_emit()
+ g_signal_emit_valist() from g_signal_emit() from ... from
+ CcpScreen::timeout()
affects: compiz-core → compiz-compizconfig-gconf
affects: compiz (Ubuntu) → compizconfig-backend-gconf (Ubuntu)
Changed in compiz-compizconfig-gconf:
importance: Undecided → High
status: Confirmed → Triaged
Changed in compizconfig-backend-gconf (Ubuntu):
importance: Medium → High
Changed in compiz:
importance: Undecided → High
status: New → Triaged
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.