compiz crashed with SIGSEGV in Glib::Source::prepare_vfunc()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
compiz (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
Occurred immediately after login.
ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: compiz-core 1:0.9.7.2-0ubuntu4
ProcVersionSign
Uname: Linux 3.2.0-20-generic x86_64
.tmp.unity.
ApportVersion: 1.95-0ubuntu1
Architecture: amd64
CompizPlugins: [core,composite
CompositorRunning: compiz
CrashCounter: 1
Date: Mon Mar 26 22:20:48 2012
DistUpgraded: 2011-12-23 13:16:19,461 DEBUG enabling apt cron job
DistroCodename: precise
DistroVariant: ubuntu
ExecutablePath: /usr/bin/compiz
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Alpha amd64 (20110705.1)
MachineType: LENOVO 4294CTO
ProcCmdline: compiz
ProcEnviron:
LANG=en_US.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 2011-12-23 (94 days ago)
UserGroups: adm admin cdrom dialout libvirtd lpadmin plugdev sambashare vboxusers
dmi.bios.date: 12/01/2011
dmi.bios.vendor: LENOVO
dmi.bios.version: 8DET56WW (1.26 )
dmi.board.
dmi.board.name: 4294CTO
dmi.board.vendor: LENOVO
dmi.board.version: Not Available
dmi.chassis.
dmi.chassis.type: 10
dmi.chassis.vendor: LENOVO
dmi.chassis.
dmi.modalias: dmi:bvnLENOVO:
dmi.product.name: 4294CTO
dmi.product.
dmi.sys.vendor: LENOVO
version.compiz: compiz 1:0.9.7.2-0ubuntu4
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.