compiz.real crashed with SIGSEGV in eventLoop()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
compiz (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
Binary package hint: compiz
details included.
ProblemType: Crash
Architecture: i386
CompizPlugins: [core,move,
CrashCounter: 1
Date: Thu Oct 15 22:03:50 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/bin/
MachineType: Dell Inc. Latitude D610
Package: compiz-core 1:0.8.3+
PccardctlIdent:
Socket 0:
no product info available
PccardctlStatus:
Socket 0:
no card
PciDisplay: 00:02.0 VGA compatible controller [0300]: Intel Corporation Mobile 915GM/GMS/910GML Express Graphics Controller [8086:2592] (rev 03)
ProcCmdLine: root=UUID=
ProcCmdline: /usr/bin/
ProcEnviron:
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcVersionSign
RelatedPackageV
xserver-xorg 1:7.4+3ubuntu5
libgl1-mesa-glx 7.6.0-1ubuntu4
libdrm2 2.4.14-1ubuntu1
xserver-
xserver-
SegvAnalysis:
Segfault happened at: 0x8055bec: mov (%ebx),%ebx
PC (0x08055bec) ok
source "(%ebx)" (0x00000020) not located in a known VMA region (needed readable region)!
destination "%ebx" ok
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: compiz
StacktraceTop:
?? ()
eventLoop ()
main ()
Title: compiz.real crashed with SIGSEGV in eventLoop()
Uname: Linux 2.6.31-14-generic i686
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
dmi.bios.date: 10/02/2005
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A06
dmi.board.name: 0D4571
dmi.board.vendor: Dell Inc.
dmi.chassis.type: 8
dmi.chassis.vendor: Dell Inc.
dmi.modalias: dmi:bvnDellInc.
dmi.product.name: Latitude D610
dmi.sys.vendor: Dell Inc.
system: distro = Ubuntu, architecture = i686, kernel = 2.6.31-14-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 #440943, 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.