compiz crashed with SIGSEGV in PrivateWindow::addWindowStackChanges()

Bug #861967 reported by Colin Church
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
unity (Ubuntu)
New
Undecided
Unassigned

Bug Description

Compiz crashed straight after log-in
This is the 11.10 version

ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: unity 4.18.0-0ubuntu1
ProcVersionSignature: Ubuntu 3.0.0-12.19-generic 3.0.4
Uname: Linux 3.0.0-12-generic i686
NonfreeKernelModules: nvidia
ApportVersion: 1.23-0ubuntu2
Architecture: i386
CrashCounter: 1
Date: Thu Sep 29 10:41:09 2011
ExecutablePath: /usr/bin/compiz
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release i386 (20110427.1)
ProcCmdline: compiz --sm-client-id 10593f42d64460e212131710634781907200000013720053
SegvAnalysis:
 Segfault happened at: 0x808420a <_ZN13PrivateWindow21addWindowStackChangesEP14XWindowChangesP10CompWindow+42>: mov 0x34(%edx),%ebx
 PC (0x0808420a) ok
 source "0x34(%edx)" (0x00000034) not located in a known VMA region (needed readable region)!
 destination "%ebx" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: unity
StacktraceTop:
 PrivateWindow::addWindowStackChanges(XWindowChanges*, CompWindow*) ()
 CompWindow::lower() ()
 CompScreen::handleEvent(_XEvent*) ()
 PrivateCompositeScreen::handleEvent(_XEvent*) () from /usr/lib/compiz/libcomposite.so
 CompScreen::handleEvent(_XEvent*) ()
Title: compiz crashed with SIGSEGV in PrivateWindow::addWindowStackChanges()
UpgradeStatus: Upgraded to oneiric on 2011-09-27 (1 days ago)
UserGroups: adm admin audio cdrom daemon dialout dip fax floppy fuse games lp lpadmin mail messagebus mysql netdev operator plugdev root sambashare sudo users video

Revision history for this message
Colin Church (colnton3) wrote :
Revision history for this message
Apport retracing service (apport) wrote : This bug is a duplicate

Thank you for taking the time to report this crash and helping to make Ubuntu better. This particular crash has already been reported and is a duplicate of bug #861542, so 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. Please continue to report any other bugs you may find.

visibility: private → public
visibility: private → public
tags: removed: need-i386-retrace
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.