compiz crashed with SIGSEGV in GLScreen::GLScreen()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
compiz (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
Crashed as soon as boots Ubuntu 12.10 beta 1.
ProblemType: Crash
DistroRelease: Ubuntu 12.10
Package: compiz-core 1:0.9.8.0-0ubuntu1
ProcVersionSign
Uname: Linux 3.5.0-14-generic i686
NonfreeKernelMo
ApportVersion: 2.5.2-0ubuntu1
Architecture: i386
Date: Mon Sep 17 14:48:29 2012
DistUpgraded: 2012-09-17 12:53:29,115 DEBUG enabling apt cron job
DistroCodename: quantal
DistroVariant: ubuntu
ExecutablePath: /usr/bin/compiz
ProcCmdline: Compiz
ProcEnviron:
LANGUAGE=en_GB:en
PATH=(custom, no user)
LANG=en_GB.UTF-8
SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=
SegvAnalysis:
Segfault happened at: 0xb7401946: movzbl 0x0(%ebp),%eax
PC (0xb7401946) ok
source "0x0(%ebp)" (0x00000000) not located in a known VMA region (needed readable region)!
destination "%eax" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: compiz
StacktraceTop:
?? () from /lib/i386-
GLScreen:
PluginClassHan
CompPlugin:
CompManager:
Title: compiz crashed with SIGSEGV in GLScreen:
UpgradeStatus: Upgraded to quantal on 2012-09-17 (0 days ago)
UserGroups:
dmi.bios.date: 01/31/2008
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 1.0.11
dmi.board.name: 0CU409
dmi.board.vendor: Dell Inc.
dmi.chassis.type: 3
dmi.chassis.vendor: Dell Inc.
dmi.chassis.
dmi.modalias: dmi:bvnDellInc.
dmi.product.name: Vostro 200
dmi.sys.vendor: Dell Inc.
version.compiz: compiz 1:0.9.8.0-0ubuntu1
version.libdrm2: libdrm2 2.4.39-0ubuntu1
version.
version.
version.
version.
version.
version.
version.
version.
Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #1051933, 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.