compiz crashed with SIGSEGV in gdk_display_get_event()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
compiz (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
Compiz crash after computer wake up.
ProblemType: Crash
DistroRelease: Ubuntu 11.10
Package: compiz-core 1:0.9.6+
ProcVersionSign
Uname: Linux 3.0.0-12-generic i686
.tmp.unity.
ApportVersion: 1.23-0ubuntu2
Architecture: i386
CompizPlugins: [core,bailer,
CompositorRunning: compiz
CrashCounter: 1
Date: Sun Oct 2 16:41:16 2011
DistUpgraded: Fresh install
DistroCodename: oneiric
DistroVariant: ubuntu
ExecutablePath: /usr/bin/compiz
GraphicsCard:
Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0126] (rev 09) (prog-if 00 [VGA controller])
Subsystem: Lenovo Device [17aa:21da]
MachineType: LENOVO 4290RV5
ProcCmdline: compiz
ProcKernelCmdLine: BOOT_IMAGE=
SegvAnalysis:
Segfault happened at: 0x5e2dee: mov 0x8(%esi),%ebp
PC (0x005e2dee) ok
source "0x8(%esi)" (0x00000008) not located in a known VMA region (needed readable region)!
destination "%ebp" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: compiz
StacktraceTop:
?? () from /usr/lib/
?? () from /usr/lib/
?? () from /usr/lib/
?? () from /usr/lib/
gdk_display_
Title: compiz crashed with SIGSEGV in gdk_display_
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
dmi.bios.date: 07/01/2011
dmi.bios.vendor: LENOVO
dmi.bios.version: 8DET49WW (1.19 )
dmi.board.
dmi.board.name: 4290RV5
dmi.board.vendor: LENOVO
dmi.board.version: Not Available
dmi.chassis.
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.
dmi.modalias: dmi:bvnLENOVO:
dmi.product.name: 4290RV5
dmi.product.
dmi.sys.vendor: LENOVO
version.compiz: compiz 1:0.9.6+
version.libdrm2: libdrm2 2.4.26-1ubuntu1
version.
version.
version.
version.
version.
version.
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 #838407, 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.