compiz crashed with SIGSEGV in g_type_check_instance()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
compiz (Ubuntu) |
New
|
Medium
|
Unassigned |
Bug Description
compiz crashed when I was playing with images loading in compiz-config
ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: compiz-core 1:0.9.7.4-0ubuntu3
ProcVersionSign
Uname: Linux 3.2.0-21-generic x86_64
.tmp.unity.
ApportVersion: 2.0-0ubuntu4
Architecture: amd64
CompizPlugins: [core,composite
CompositorRunning: compiz
CrashCounter: 1
Date: Tue Apr 10 13:00:13 2012
DistUpgraded: Fresh install
DistroCodename: precise
DistroVariant: ubuntu
ExecutablePath: /usr/bin/compiz
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Beta amd64+mac (20120328)
MachineType: Sony Corporation VGN-SZ640N
PccardctlIdent:
Socket 0:
no product info available
PccardctlStatus:
Socket 0:
no card
ProcCmdline: compiz
ProcKernelCmdLine: BOOT_IMAGE=
SegvReason: reading unknown VMA
Signal: 11
SourcePackage: compiz
Title: compiz crashed with SIGSEGV in g_type_
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
dmi.bios.date: 04/04/2008
dmi.bios.vendor: Phoenix Technologies LTD
dmi.bios.version: R0122S5
dmi.board.
dmi.board.name: VAIO
dmi.board.vendor: Sony Corporation
dmi.board.version: N/A
dmi.chassis.type: 10
dmi.chassis.vendor: Sony Corporation
dmi.chassis.
dmi.modalias: dmi:bvnPhoenixT
dmi.product.name: VGN-SZ640N
dmi.product.
dmi.sys.vendor: Sony Corporation
version.compiz: compiz 1:0.9.7.4-0ubuntu3
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.32-1ubuntu1
version.
version.
version.
version.
version.
version.
version.
version.
Thank you for taking the time to report this bug and helping to make Ubuntu better. This particular bug has already been reported and is a duplicate of bug 932382, so it 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. Feel free to continue to report any other bugs you may find.