compiz crashed with signal 5 in Glib::exception_handlers_invoke()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
compiz (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
Not sure what caused this, I was just using my computer normally.
ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: compiz-core 1:0.9.7.
ProcVersionSign
Uname: Linux 3.2.0-16-generic x86_64
.tmp.unity.
ApportVersion: 1.91-0ubuntu1
Architecture: amd64
CompizPlugins: [core,bailer,
CompositorRunning: compiz
CrashCounter: 1
Date: Fri Feb 17 20:32:57 2012
DistUpgraded: Log time: 2012-02-11 12:41:05.499786
DistroCodename: precise
DistroVariant: ubuntu
EcryptfsInUse: Yes
ExecutablePath: /usr/bin/compiz
GraphicsCard:
Intel Corporation 2nd Generation Core Processor Family Integrated Graphics Controller [8086:0126] (rev 09) (prog-if 00 [VGA controller])
Subsystem: Lenovo Device [17aa:21dd]
InstallationMedia: Ubuntu 12.04 LTS "Precise Pangolin" - Alpha amd64 (20120209)
MachineType: LENOVO 7859CTO
ProcCmdline: compiz
ProcKernelCmdLine: BOOT_IMAGE=
Signal: 5
SourcePackage: compiz
StacktraceTop:
Glib::
Glib::
g_main_
?? () from /lib/x86_
g_main_loop_run () from /lib/x86_
Title: compiz crashed with signal 5 in Glib::exception
UpgradeStatus: Upgraded to precise on 2012-02-13 (3 days ago)
UserGroups: adm cdrom dip lpadmin plugdev sambashare sudo www-data
dmi.bios.date: 11/04/2011
dmi.bios.vendor: LENOVO
dmi.bios.version: 8GET38WW (1.15 )
dmi.board.name: 7859CTO
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: 7859CTO
dmi.product.
dmi.sys.vendor: LENOVO
version.compiz: compiz 1:0.9.7.
version.ia32-libs: ia32-libs N/A
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.