compiz crashed with SIGSEGV in CompWindow::id()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
compiz (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
Binary package hint: compiz
This was supposedly fixed but a quick and very very simple test shows it is not fixed and still crashing.
ProblemType: Crash
DistroRelease: Ubuntu 11.04
Package: compiz-core 1:0.9.4git20110
ProcVersionSign
Uname: Linux 2.6.38-7-generic x86_64
NonfreeKernelMo
Architecture: amd64
Date: Fri Apr 1 17:36:20 2011
DistroCodename: natty
DistroVariant: ubuntu
ExecutablePath: /usr/bin/compiz
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Alpha amd64 (20110302)
InstallationMedia_: Ubuntu 11.04 "Natty Narwhal" - Alpha amd64 (20110302)
ProcCmdline: /usr/bin/compiz
ProcEnviron:
LANGUAGE=en_US:en
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcVersionSign
SegvAnalysis:
Segfault happened at: 0x43bef0 <CompWindow::id()>: mov 0x58(%rdi),%rax
PC (0x0043bef0) ok
source "0x58(%rdi)" (0x00000058) not located in a known VMA region (needed readable region)!
destination "%rax" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: compiz
StacktraceTop:
CompWindow::id (this=0x0) at /build/
CompScreen:
PrivateComposi
CompScreen:
PrivateGLScree
Title: compiz crashed with SIGSEGV in CompWindow::id()
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm admin cdrom dialout lp lpadmin plugdev sambashare
XsessionErrors:
(nautilus:1754): Gtk-WARNING **: Change Desktop Background: missing action Change Desktop Background
(nautilus:1754): Gtk-WARNING **: Ubuntu Documentation: missing action Ubuntu Documentation
(nautilus:1754): Gtk-WARNING **: Change Desktop Background: missing action Change Desktop Background
(nautilus:1754): Gtk-WARNING **: Ubuntu Documentation: missing action Ubuntu Documentation
(npviewer.
version.
version.
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 #747439, 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.