compiz crashed with signal 5 in Glib::exception_handlers_invoke()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
compiz (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
SPONTANEOUS
ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: compiz-core 1:0.9.7.
ProcVersionSign
Uname: Linux 3.2.0-17-
.tmp.unity.
ApportVersion: 1.93-0ubuntu2
Architecture: i386
CompizPlugins: [core,composite
CompositorRunning: compiz
CrashCounter: 1
Date: Thu Mar 1 19:45:46 2012
DistUpgraded: Fresh install
DistroCodename: precise
DistroVariant: ubuntu
ExecutablePath: /usr/bin/compiz
GraphicsCard:
Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0106] (rev 09) (prog-if 00 [VGA controller])
Subsystem: ASUSTeK Computer Inc. Device [1043:13c7]
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Alpha i386 (20120211)
MachineType: ASUSTeK Computer Inc. K54L
ProcCmdline: compiz
ProcKernelCmdLine: BOOT_IMAGE=
Signal: 5
SourcePackage: compiz
StacktraceTop:
Glib::
Glib::
g_main_
?? () from /lib/i386-
g_main_loop_run () from /lib/i386-
Title: compiz crashed with signal 5 in Glib::exception
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo
dmi.bios.date: 08/12/2011
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: K54L.206
dmi.board.
dmi.board.name: K54L
dmi.board.vendor: ASUSTeK Computer Inc.
dmi.board.version: 1.0
dmi.chassis.
dmi.chassis.type: 10
dmi.chassis.vendor: ASUSTeK Computer Inc.
dmi.chassis.
dmi.modalias: dmi:bvnAmerican
dmi.product.name: K54L
dmi.product.
dmi.sys.vendor: ASUSTeK Computer Inc.
version.compiz: compiz 1:0.9.7.
version.libdrm2: libdrm2 2.4.30-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 #808007, 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.