compiz crashed with SIGSEGV in g_type_check_instance()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
compiz (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
I've also had a lot of trouble with Compiz in previous Ubuntu versions.
ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: compiz-core 1:0.9.7.2-0ubuntu4
ProcVersionSign
Uname: Linux 3.2.0-20-
.tmp.unity.
ApportVersion: 1.95-0ubuntu1
Architecture: i386
CheckboxSubmission: 23f9165fb526914
CheckboxSystem: edda5d4f616ca79
CompizPlugins: [core,composite
CompositorRunning: compiz
Date: Fri Mar 30 03:22:19 2012
DistUpgraded: 2012-03-30 03:19:18,676 DEBUG enabling apt cron job
DistroCodename: precise
DistroVariant: ubuntu
ExecutablePath: /usr/bin/compiz
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release i386 (20101007)
MachineType: HP Pavilion 061 PS500AA-ABA A824N
ProcCmdline: compiz --sm-client-id 1034b929b65e45a
ProcKernelCmdLine: BOOT_IMAGE=
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: compiz
Title: compiz crashed with SIGSEGV in g_type_
UpgradeStatus: Upgraded to precise on 2012-03-30 (0 days ago)
UserGroups: adm admin cdrom debian-tor dialout lpadmin plugdev sambashare vboxusers
dmi.bios.date: 02/16/2005
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 3.18
dmi.board.name: Goldfish2
dmi.board.vendor: ASUSTeK Computer INC.
dmi.board.version: 1.xx
dmi.chassis.
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.
dmi.modalias: dmi:bvnAmerican
dmi.product.name: PS500AA-ABA A824N
dmi.product.
dmi.sys.vendor: HP Pavilion 061
version.compiz: compiz 1:0.9.7.2-0ubuntu4
version.libdrm2: libdrm2 2.4.32-1ubuntu1
version.
version.
version.
version.
version.
version.
version.
version.
Thank you for taking the time to report this crash and helping to make this software better. This particular crash has already been reported and is a duplicate of bug #929976, 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.