compiz.real crashed with SIGSEGV in handleEvent() ; while seeing a video
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
compiz (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
Binary package hint: compiz
I think that it crashed while I was seeing a video, with Totem, inside Firefox. The url of the video is http://
ProblemType: Crash
Architecture: amd64
CompizPlugins: [core,move,
CrashCounter: 1
Date: Wed Sep 23 16:34:21 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/bin/
MachineType: Acer Aspire 5520
NonfreeKernelMo
Package: compiz-core 1:0.8.3+
PciDisplay: 00:12.0 VGA compatible controller [0300]: nVidia Corporation C67 [GeForce 7000M / nForce 610M] [10de:0533] (rev a2)
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: 0x7f41437a95cb: mov 0x18(%r12),%rdi
PC (0x7f41437a95cb) ok
source "0x18(%r12)" (0x00000018) not located in a known VMA region (needed readable region)!
destination "%rdi" 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 x86_64
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
dmi.bios.date: 01/09/2008
dmi.bios.vendor: Acer
dmi.bios.version: V1.31
dmi.board.name: Fuquene
dmi.board.vendor: Acer
dmi.board.version: N/A
dmi.chassis.type: 10
dmi.chassis.vendor: Acer
dmi.chassis.
dmi.modalias: dmi:bvnAcer:
dmi.product.name: Aspire 5520
dmi.product.
dmi.sys.vendor: Acer
system: distro = Ubuntu, architecture = x86_64, 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.