Compiz crashes randomly on Natty
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
compiz (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
Binary package hint: compiz
I'm running an up-to-date installation of Natty and Compiz keeps crashing randomly. I'm using the default settings.
When restarting compiz on tty1 with the command 'compiz --display :0' you'll see the following error message after Compiz crashed again:
terminate called after throwing an instance of 'boost:
what(): call to empty boost::function
The crash seems to happen only when manipulating tables in OpenOffice.org, but I haven't confirmed that fully yet. The document I'm using is a ODT file converted from OOXML's docx, containing table parts that were originally created in Microsoft Word 2007.
ProblemType: Bug
DistroRelease: Ubuntu 11.04
Package: compiz 1:0.9.2.
ProcVersionSign
Uname: Linux 2.6.37-3-generic x86_64
NonfreeKernelMo
Architecture: amd64
CompizPlugins: [core,ccp,
Date: Sun Nov 14 12:50:57 2010
MachineType: System manufacturer System Product Name
PackageArchitec
PciDisplay: 02:00.0 VGA compatible controller [0300]: nVidia Corporation G94 [GeForce 9600 GT] [10de:0622] (rev a1) (prog-if 00 [VGA controller])
ProcEnviron:
LANGUAGE=
LANG=nl_NL.utf8
SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=
RelatedPackageV
xserver-xorg 1:7.5+6ubuntu3
libgl1-mesa-glx 7.9~git20100924
libdrm2 2.4.22-2ubuntu1
xserver-
xserver-
SourcePackage: compiz
dmi.bios.date: 08/06/2008
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 0415
dmi.board.
dmi.board.name: M3N78-EH
dmi.board.vendor: ASUSTeK Computer INC.
dmi.board.version: Rev 1.xx
dmi.chassis.
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.
dmi.modalias: dmi:bvnAmerican
dmi.product.name: System Product Name
dmi.product.
dmi.sys.vendor: System manufacturer
system: distro = Ubuntu, architecture = x86_64, kernel = 2.6.37-3-generic
description: | updated |
This is happening to me too.
To workaround I use compiz --replace from a terminal.
I can confirm that OpenOffice.org is causing this issue.