compiz crashed with signal 5 in Glib::exception_handlers_invoke()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
compiz (Ubuntu) |
Won't Fix
|
Medium
|
Unassigned |
Bug Description
This looks similar to the following bug:
https:/
However, I'm seeing the crash with the latest version of compiz in 12.04 LTS amd64. I didn't see this problem last week but started to see the problem since about 3~4 days ago I updated the system.
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
.tmp.unity.
ApportVersion: 1.95-0ubuntu1
Architecture: amd64
CompizPlugins: [core,bailer,
CompositorRunning: compiz
Date: Sun Mar 25 12:38:35 2012
DistUpgraded: 2012-03-20 20:31:28,524 DEBUG enabling apt cron job
DistroCodename: precise
DistroVariant: ubuntu
ExecutablePath: /usr/bin/compiz
MachineType: Apple Inc. MacBookPro8,1
ProcCmdline: compiz
ProcEnviron:
LANGUAGE=en_US:en
PATH=(custom, user)
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=
Signal: 5
SourcePackage: compiz
Title: compiz crashed with signal 5 in Glib::exception
UpgradeStatus: Upgraded to precise on 2012-03-20 (4 days ago)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
dmi.bios.date: 01/24/12
dmi.bios.vendor: Apple Inc.
dmi.bios.version: MBP81.88Z.
dmi.board.
dmi.board.name: Mac-94245B3640C
dmi.board.vendor: Apple Inc.
dmi.board.version: MacBookPro8,1
dmi.chassis.type: 10
dmi.chassis.vendor: Apple Inc.
dmi.chassis.
dmi.modalias: dmi:bvnAppleInc
dmi.product.name: MacBookPro8,1
dmi.product.
dmi.sys.vendor: Apple Inc.
version.compiz: compiz 1:0.9.7.2-0ubuntu1
version.ia32-libs: ia32-libs N/A
version.libdrm2: libdrm2 2.4.32-1ubuntu1
version.
version.
version.
version.
version.
version.
version.
version.
tags: | added: quantal running-unity |
tags: | added: raring |
tags: | added: bugpattern-needed |
information type: | Private → Public |
tags: | added: saucy |
This crash has the same stack trace characteristics as bug #808007. However, the latter was already fixed in an earlier package version than the one in this report. This might be a regression or because the problem is in a dependent package.