compiz crashed with SIGSEGV in CompWindow::id()

Bug #888854 reported by Harold Porter
18
This bug affects 3 people
Affects Status Importance Assigned to Milestone
Compiz
New
Medium
Unassigned
Unity
Confirmed
Medium
Unassigned
compiz (Ubuntu)
Confirmed
Medium
Unassigned

Bug Description

This 'crash' occurred during the first hour I have spent with Linux. I don't know what happened. I didn't even know that it had crashed except that it told me that it had crashed. Sorry, I'm not much help.

ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: unity 4.24.0-0ubuntu2b1
ProcVersionSignature: Ubuntu 3.0.0-12.20-generic-pae 3.0.4
Uname: Linux 3.0.0-12-generic-pae i686
ApportVersion: 1.23-0ubuntu4
Architecture: i386
CasperVersion: 1.287
Date: Thu Nov 10 19:39:35 2011
ExecutablePath: /usr/bin/compiz
LiveMediaBuild: Ubuntu 11.10 "Oneiric Ocelot" - Release i386 (20111012)
ProcCmdline: compiz
ProcEnviron:
 PATH=(custom, no user)
 LANG=en_US.UTF-8
 SHELL=/bin/bash
SegvAnalysis:
 Segfault happened at: 0x8083a27 <_ZN10CompWindow2idEv+7>: mov 0x10(%eax),%eax
 PC (0x08083a27) ok
 source "0x10(%eax)" (0x05a00010) not located in a known VMA region (needed readable region)!
 destination "%eax" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: unity
StacktraceTop:
 CompWindow::id() ()
 UnityWindow::glPaint(GLWindowPaintAttrib const&, GLMatrix const&, CompRegion const&, unsigned int) () from /usr/lib/compiz/libunityshell.so
 GLWindow::glPaint(GLWindowPaintAttrib const&, GLMatrix const&, CompRegion const&, unsigned int) () from /usr/lib/compiz/libopengl.so
 PrivateGLScreen::paintOutputRegion(GLMatrix const&, CompRegion const&, CompOutput*, unsigned int) () from /usr/lib/compiz/libopengl.so
 GLScreen::glPaintOutput(GLScreenPaintAttrib const&, GLMatrix const&, CompRegion const&, CompOutput*, unsigned int) () from /usr/lib/compiz/libopengl.so
Title: compiz crashed with SIGSEGV in CompWindow::id()
UpgradeStatus: Upgraded to oneiric on 2011-11-11 (0 days ago)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare

Revision history for this message
Harold Porter (hporter-d) wrote :
Revision history for this message
Apport retracing service (apport) wrote :

StacktraceTop:
 CompWindow::id (this=0xb03c02e8) at /build/buildd/compiz-0.9.6+bzr20110929/src/window.cpp:5590
 getPaintMask (this=<optimized out>) at /build/buildd/unity-4.24.0/plugins/unityshell/src/compizminimizedwindowhandler.h:276
 UnityWindow::glPaint (this=0xb0040f90, attrib=..., matrix=..., region=..., mask=2) at /build/buildd/unity-4.24.0/plugins/unityshell/src/unityshell.cpp:1594
 GLWindow::glDraw (this=0xb0044368, transform=..., fragment=..., region=..., mask=<optimized out>) at /build/buildd/compiz-0.9.6+bzr20110929/plugins/opengl/src/paint.cpp:1175
 PrivateGLScreen::paintOutputRegion (this=0x8c8c1a0, transform=..., region=..., output=0x8c11340, mask=11) at /build/buildd/compiz-0.9.6+bzr20110929/plugins/opengl/src/paint.cpp:249

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
visibility: private → public
Changed in unity (Ubuntu):
importance: Medium → Critical
Changed in unity:
status: New → Confirmed
Changed in unity (Ubuntu):
status: New → Confirmed
Changed in unity:
importance: Undecided → High
Omer Akram (om26er)
affects: unity (Ubuntu) → compiz (Ubuntu)
Changed in compiz (Ubuntu):
importance: Critical → High
Changed in compiz-core:
importance: Undecided → High
Changed in compiz:
importance: Undecided → High
Omer Akram (om26er)
no longer affects: compiz-core
Changed in compiz (Ubuntu):
importance: High → Medium
Changed in unity:
importance: High → Medium
Changed in compiz:
importance: High → Medium
Revision history for this message
Daniel van Vugt (vanvugt) wrote :

Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 851982, so it is being marked as such. Please look at the other bug report to see if there is any missing information that you can provide, or to see if there is a workaround for the bug. Additionally, any further discussion regarding the bug should occur in the other report. Feel free to continue to report any other bugs you may find.

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.