compiz crashed with signal 5 in Glib::exception_handlers_invoke()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
compiz (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
it's happend on unity descktop every time after right clik mouse on any why
ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: compiz-core 1:0.9.7.
ProcVersionSign
Uname: Linux 3.2.0-20-generic x86_64
NonfreeKernelMo
.tmp.unity.
ApportVersion: 1.95-0ubuntu1
Architecture: amd64
CheckboxSubmission: e72bc25120489d4
CheckboxSystem: d00f84de8a55581
CompizPlugins: [core,composite
CompositorRunning: compiz
CrashCounter: 1
Date: Fri Mar 23 17:59:47 2012
DistUpgraded: 2012-03-06 18:19:38,929 DEBUG enabling apt cron job
DistroCodename: precise
DistroVariant: ubuntu
ExecutablePath: /usr/bin/compiz
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release amd64 (20110427.1)
MachineType: Dell Inc. Inspiron N5010
ProcCmdline: compiz
ProcKernelCmdLine: BOOT_IMAGE=
Signal: 5
SourcePackage: compiz
Title: compiz crashed with signal 5 in Glib::exception
UpgradeStatus: Upgraded to precise on 2012-03-06 (16 days ago)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
dmi.bios.date: 07/26/2010
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A07
dmi.board.name: 0YXXJJ
dmi.board.vendor: Dell Inc.
dmi.board.version: A07
dmi.chassis.type: 8
dmi.chassis.vendor: Dell Inc.
dmi.chassis.
dmi.modalias: dmi:bvnDellInc.
dmi.product.name: Inspiron N5010
dmi.product.
dmi.sys.vendor: Dell Inc.
version.compiz: compiz 1:0.9.7.
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 #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.