compiz.real crashed with SIGSEGV in handleEvent()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
compiz (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
Binary package hint: compiz
Session crashed when i was trying to do the systemtest.
ProblemType: Crash
Architecture: i386
CompizPlugins: [core,move,
CrashCounter: 1
Date: Wed Sep 30 12:02:06 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/bin/
MachineType: Acer Aspire 1360
NonfreeKernelMo
Package: compiz-core 1:0.8.3+
PccardctlIdent:
Socket 0:
no product info available
Socket 1:
no product info available
PccardctlStatus:
Socket 0:
no card
Socket 1:
no card
PciDisplay: 01:00.0 VGA compatible controller [0300]: nVidia Corporation NV34M [GeForce FX Go5200 64M] [10de:0324] (rev a1)
ProcCmdLine: root=UUID=
ProcCmdline: /usr/bin/
ProcEnviron:
LANG=de_DE.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: 0xd39661: mov 0xc(%ecx),%eax
PC (0x00d39661) 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-11-generic i686
UserGroups: adm admin cdrom dialout fuse lpadmin plugdev sambashare vboxusers voice
dmi.bios.date: 07/26/2005
dmi.bios.vendor: Phoenix
dmi.bios.version: V1.14
dmi.board.name: Aspire 1360
dmi.board.vendor: Acer
dmi.board.version: Rev.A
dmi.chassis.type: 1
dmi.chassis.vendor: N/A
dmi.chassis.
dmi.modalias: dmi:bvnPhoenix:
dmi.product.name: Aspire 1360
dmi.product.
dmi.sys.vendor: Acer
system: distro = Ubuntu, architecture = i686, kernel = 2.6.31-11-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.