compiz crashed with SIGSEGV in PrivateWindow::addWindowStackChanges()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
compiz (Ubuntu) |
New
|
Critical
|
Unassigned | ||
unity (Ubuntu) |
New
|
Critical
|
Unassigned |
Bug Description
Happened right after the first login into my old HP 32-bit notebook after upgrading from Natty to Oneiric.
ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: unity 4.18.0-0ubuntu1
ProcVersionSign
Uname: Linux 2.6.38-11-generic i686
ApportVersion: 1.23-0ubuntu2
Architecture: i386
Date: Thu Sep 29 12:12:02 2011
ExecutablePath: /usr/bin/compiz
ProcCmdline: compiz
ProcEnviron:
PATH=(custom, no user)
LANG=en_US.UTF-8
SHELL=/bin/bash
SegvAnalysis:
Segfault happened at: 0x808420a <_ZN13PrivateWi
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:
CompWindow:
CompScreen:
PrivateComposi
CompScreen:
Title: compiz crashed with SIGSEGV in PrivateWindow:
UpgradeStatus: Upgraded to oneiric on 2011-07-13 (77 days ago)
UserGroups: adm admin cdrom dialout dip fax floppy fuse lpadmin plugdev sambashare tape video
XsessionErrors:
(nautilus:2057): Gtk-CRITICAL **: gtk_action_
(nautilus:2057): Gtk-CRITICAL **: gtk_action_
visibility: | private → public |
Changed in compiz (Ubuntu): | |
importance: | Undecided → Critical |
Changed in unity (Ubuntu): | |
importance: | Undecided → Critical |
Changed in compiz (Ubuntu): | |
milestone: | none → ubuntu-11.10 |
Changed in unity (Ubuntu): | |
milestone: | none → ubuntu-11.10 |
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.