compiz.real crashed with SIGSEGV in eventLoop()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
compiz (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
Binary package hint: compiz
i am not sure what caused the crash
ProblemType: Crash
Architecture: i386
CheckboxSubmission: 71519a5e155620f
CheckboxSystem: 2abf16d4e86c450
CompizPlugins: [core,move,
Date: Thu Oct 8 00:15:48 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/bin/
MachineType: FUJITSU LifeBook P1630
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 4 Series Chipset Integrated Graphics Controller [8086:2a42] (rev 07)
ProcCmdLine: BOOT_IMAGE=
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~git200908
libdrm2 2.4.13-1ubuntu1
xserver-
xserver-
SegvAnalysis:
Segfault happened at: 0x8055bec: mov (%ebx),%ebx
PC (0x08055bec) ok
source "(%ebx)" (0x04a00022) not located in a known VMA region (needed readable region)!
destination "%ebx" ok
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: compiz
StacktraceTop:
?? ()
eventLoop ()
main ()
Title: compiz.real crashed with SIGSEGV in eventLoop()
Uname: Linux 2.6.31-12-generic i686
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
XorgConf: Error: [Errno 2] No such file or directory: '/etc/X11/
dmi.bios.date: 11/14/2008
dmi.bios.vendor: FUJITSU // Phoenix Technologies Ltd.
dmi.bios.version: Version 1.07
dmi.board.name: FJNB1F8
dmi.board.vendor: FUJITSU
dmi.chassis.type: 10
dmi.chassis.vendor: A322H10305301010
dmi.modalias: dmi:bvnFUJITSU/
dmi.product.name: LifeBook P1630
dmi.sys.vendor: FUJITSU
system: distro = Ubuntu, architecture = i686, kernel = 2.6.31-12-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.