compiz.real crashed with SIGSEGV in handleEvent()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
compiz (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
Binary package hint: compiz
Something crashed on the graphical session, it got hanged... i got out to a text session, came back and found the crash report. Hope it helps...
Using Ubuntu Karmic Alpha
ProblemType: Crash
Architecture: i386
CompizPlugins: [core,move,
Date: Sat Sep 19 21:55:08 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/bin/
MachineType: eMachines EL1200
NonfreeKernelMo
Package: compiz-core 1:0.8.3+
PciDisplay: 00:0d.0 VGA compatible controller [0300]: nVidia Corporation C61 [GeForce 6150SE nForce 430] [10de:03d0] (rev a2)
ProcCmdLine: root=UUID=
ProcCmdline: /usr/bin/
ProcEnviron:
LANGUAGE=
LANG=es_ES.UTF-8
SHELL=/bin/bash
ProcVersionSign
RelatedPackageV
xserver-xorg 1:7.4+3ubuntu5
libgl1-mesa-glx 7.6.0~git200908
libdrm2 2.4.13-1ubuntu1
xserver-
xserver-
SegvAnalysis:
Segfault happened at: 0xbff661: mov 0xc(%ecx),%eax
PC (0x00bff661) ok
source "0xc(%ecx)" (0x0000000c) not located in a known VMA region (needed readable region)!
destination "%eax" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: compiz
StacktraceTop:
?? () from /usr/lib/
handleEvent ()
?? () from /usr/lib/
?? () from /usr/lib/
?? () from /usr/lib/
Title: compiz.real crashed with SIGSEGV in handleEvent()
Uname: Linux 2.6.31-10-generic i686
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
dmi.bios.date: 09/17/2008
dmi.bios.vendor: Phoenix Technologies, LTD
dmi.bios.version: R01-A0L
dmi.board.name: WMCP61M
dmi.board.vendor: eMachines
dmi.chassis.
dmi.chassis.type: 3
dmi.chassis.vendor: eMachines
dmi.modalias: dmi:bvnPhoenixT
dmi.product.name: EL1200
dmi.product.
dmi.sys.vendor: eMachines
system: distro = Ubuntu, architecture = i686, kernel = 2.6.31-10-generic
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 #430518, 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.