compiz crashed with SIGSEGV in g_type_check_instance()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
compiz (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
compiz window decorations disappear and screen becomes unresponsive
ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: compiz-core 1:0.9.7.4-0ubuntu3
ProcVersionSign
Uname: Linux 3.2.0-22-
NonfreeKernelMo
.proc.driver.
.proc.driver.
.tmp.unity.
ApportVersion: 2.0-0ubuntu4
Architecture: i386
CompizPlugins: [core,composite
CompositorRunning: compiz
Date: Sun Apr 8 17:47:47 2012
DistUpgraded: 2012-04-07 08:38:38,029 DEBUG enabling apt cron job
DistroCodename: precise
DistroVariant: ubuntu
ExecutablePath: /usr/bin/compiz
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Release i386 (20111012)
MachineType: FOXCONN M61PMV
ProcCmdline: compiz
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-04-07 (1 days ago)
UserGroups: adm admin cdrom dialout fuse lpadmin plugdev sambashare vboxusers
XorgConf:
Section "Device"
Identifier "Default Device"
Option "NoLogo" "True"
EndSection
dmi.bios.date: 07/01/2010
dmi.bios.vendor: Phoenix Technologies, LTD
dmi.bios.version: P10
dmi.board.name: M61PMV
dmi.board.vendor: FOXCONN
dmi.board.version: FAB 1.1
dmi.chassis.
dmi.chassis.type: 3
dmi.chassis.vendor: FOXCONN
dmi.modalias: dmi:bvnPhoenixT
dmi.product.name: M61PMV
dmi.product.
dmi.sys.vendor: FOXCONN
version.compiz: compiz 1:0.9.7.4-0ubuntu3
version.libdrm2: libdrm2 2.4.32-1ubuntu1
version.
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 #930575, 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.