compiz crashed with SIGSEGV in malloc()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
compiz (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
ups
ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: compiz-core 1:0.9.7.4-0ubuntu3
ProcVersionSign
Uname: Linux 3.2.0-22-generic i686
NonfreeKernelMo
.proc.driver.
Fast Writes: Supported
SBA: Supported
AGP Rates: 4x 2x 1x
Registers: 0x1f000217:
.proc.driver.
Status: Enabled
Driver: AGPGART
AGP Rate: 4x
Fast Writes: Disabled
SBA: Disabled
.proc.driver.
.proc.driver.
.tmp.unity.
ApportVersion: 2.0-0ubuntu4
Architecture: i386
CompizPlugins: [core,composite
CompositorRunning: compiz
Date: Sun Apr 8 23:04:11 2012
DistUpgraded: 2012-01-15 20:30:00,682 DEBUG enabling apt cron job
DistroCodename: precise
DistroVariant: ubuntu
ExecutablePath: /usr/bin/compiz
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Beta i386 (20110901)
ProcCmdline: compiz
ProcKernelCmdLine: BOOT_IMAGE=
SegvReason: writing unknown VMA
Signal: 11
SourcePackage: compiz
Title: compiz crashed with SIGSEGV in malloc()
UpgradeStatus: Upgraded to precise on 2012-01-15 (84 days ago)
UserGroups: adm admin cdrom debian-tor dialout lpadmin plugdev sambashare
XorgConf:
Section "Device"
Identifier "Default Device"
Option "NoLogo" "True"
EndSection
dmi.bios.date: 08/14/2003
dmi.bios.vendor: Phoenix Technologies, LTD
dmi.bios.version: 6.00 PG
dmi.board.name: i845PE-W83627
dmi.chassis.type: 3
dmi.modalias: dmi:bvnPhoenixT
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 #969142, 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.