compiz crashed with SIGSEGV in GridScreen::handleEvent()

[Luigi Maselli]

crash after restarting lightdm

ProblemType: Crash
DistroRelease: Ubuntu 12.10
Package: compiz-core 1:0.9.8.4-0ubuntu1
ProcVersionSignature: Ubuntu 3.5.0-17.27-generic 3.5.5
Uname: Linux 3.5.0-17-generic i686
ApportVersion: 2.6.1-0ubuntu1
Architecture: i386
CasperVersion: 1.327
CompizPlugins: No value set for `/apps/compiz-1/general/screen0/options/active_plugins'
CompositorRunning: compiz
Date: Tue Oct 9 23:48:20 2012
DistUpgraded: Fresh install
DistroCodename: quantal
DistroVariant: ubuntu
DkmsStatus: fglrx, 9.000, 3.5.0-17-generic, i686: installed
ExecutablePath: /usr/bin/compiz
GraphicsCard:
 Advanced Micro Devices [AMD] nee ATI RV770 [Radeon HD 4850] [1002:9442] (prog-if 00 [VGA controller])
   Subsystem: Advanced Micro Devices [AMD] nee ATI MSI R4850-T2D512 [1002:0502]
LiveMediaBuild: Ubuntu 12.10 "Quantal Quetzal" - Beta i386 (20121009)
MachineType: System manufacturer P5Q
ProcCmdline: compiz
ProcEnviron:
 PATH=(custom, no user)
 XDG_RUNTIME_DIR=<set>
 LANG=en_US.UTF-8
 SHELL=/bin/bash
ProcKernelCmdLine: initrd=/casper/initrd.lz file=/cdrom/preseed/username.seed boot=casper quiet splash -- BOOT_IMAGE=/casper/vmlinuz
SegvAnalysis:
 Segfault happened at: 0xb49bb9ba <_ZN10GridScreen11handleEventEP7_XEvent+1786>: mov 0x28(%edx),%eax
 PC (0xb49bb9ba) ok
 source "0x28(%edx)" (0x00000028) not located in a known VMA region (needed readable region)!
 destination "%eax" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: compiz
StacktraceTop:
 GridScreen::handleEvent(_XEvent*) () from /usr/lib/compiz/libgrid.so
 CompScreen::handleEvent(_XEvent*) () from /usr/lib/libcompiz_core.so.ABI-20120927
 RegexScreen::handleEvent(_XEvent*) () from /usr/lib/compiz/libregex.so
 CompScreen::handleEvent(_XEvent*) () from /usr/lib/libcompiz_core.so.ABI-20120927
 SessionScreen::handleEvent(_XEvent*) () from /usr/lib/compiz/libsession.so
Title: compiz crashed with SIGSEGV in GridScreen::handleEvent()
UnitySupportTest:
 Error: command ['/usr/lib/nux/unity_support_test', '-p', '-f'] failed with exit code 1: X Error of failed request: BadRequest (invalid request code or no such operation)
   Major opcode of failed request: 154 (GLX)
   Minor opcode of failed request: 19 (X_GLXQueryServerString)
   Serial number of failed request: 22
   Current serial number in output stream: 22
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
dmi.bios.date: 02/25/2010
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 2208
dmi.board.asset.tag: To Be Filled By O.E.M.
dmi.board.name: P5Q
dmi.board.vendor: ASUSTeK Computer INC.
dmi.board.version: Rev 1.xx
dmi.chassis.asset.tag: Asset-1234567890
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.version: Chassis Version
dmi.modalias: dmi:bvnAmericanMegatrendsInc.:bvr2208:bd02/25/2010:svnSystemmanufacturer:pnP5Q:pvrSystemVersion:rvnASUSTeKComputerINC.:rnP5Q:rvrRev1.xx:cvnChassisManufacture:ct3:cvrChassisVersion:
dmi.product.name: P5Q
dmi.product.version: System Version
dmi.sys.vendor: System manufacturer
version.compiz: compiz 1:0.9.8.4-0ubuntu1
version.libdrm2: libdrm2 2.4.39-0ubuntu1
version.libgl1-mesa-dri: libgl1-mesa-dri 9.0~git20121004.b2048c5e-0ubuntu1
version.libgl1-mesa-dri-experimental: libgl1-mesa-dri-experimental N/A
version.libgl1-mesa-glx: libgl1-mesa-glx 9.0~git20121004.b2048c5e-0ubuntu1
version.xserver-xorg-core: xserver-xorg-core 2:1.13.0-0ubuntu6
version.xserver-xorg-input-evdev: xserver-xorg-input-evdev 1:2.7.3-0ubuntu1
version.xserver-xorg-video-ati: xserver-xorg-video-ati 1:6.99.99~git20120913.8637f772-0ubuntu1
version.xserver-xorg-video-intel: xserver-xorg-video-intel 2:2.20.9-0ubuntu2
version.xserver-xorg-video-nouveau: xserver-xorg-video-nouveau 1:1.0.2-0ubuntu3

[Apport retracing service (apport)]

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 #1054049, 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.