compiz crashed with SIGSEGV in Glib::Source::prepare_vfunc()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
compiz (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
crash
Referring to Bug #932125, this is the samt with ATI
ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: compiz-core 1:0.9.7.2-0ubuntu1
ProcVersionSign
Uname: Linux 3.2.0-20-generic x86_64
NonfreeKernelMo
.tmp.unity.
ApportVersion: 1.95-0ubuntu1
Architecture: amd64
CompizPlugins: [core,composite
CompositorRunning: compiz
CrashCounter: 1
Date: Sat Mar 24 13:57:15 2012
DistUpgraded: 2012-03-24 10:34:06,720 DEBUG enabling apt cron job
DistroCodename: precise
DistroVariant: ubuntu
ExecutablePath: /usr/bin/compiz
InstallationMedia: Ubuntu 10.10 "Maverick Meerkat" - Release amd64 (20101007)
MachineType: System manufacturer System Product Name
ProcCmdline: compiz --replace
ProcEnviron:
LANG=de_AT.UTF-8
SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=
SegvReason: reading NULL VMA
Signal: 11
SourcePackage: compiz
Title: compiz crashed with SIGSEGV in Glib::Source:
UpgradeStatus: Upgraded to precise on 2012-03-24 (0 days ago)
UserGroups: adm admin audio cdrom dialout fuse lpadmin netdev plugdev sambashare vboxusers video
dmi.bios.date: 08/20/2010
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 2511
dmi.board.
dmi.board.name: M4A78-E
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
version.compiz: compiz 1:0.9.7.2-0ubuntu1
version.
version.ia32-libs: ia32-libs 20090808ubuntu35
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 #932125, 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.