compiz crashed with signal 5 in Glib::exception_handlers_invoke() with flash player in firefox
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
compiz (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
iḿ playing a game in flash player when this occured... (sorry, but i don't speak english :P)
ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: compiz-core 1:0.9.7.
ProcVersionSign
Uname: Linux 3.2.0-18-generic i686
NonfreeKernelMo
.tmp.unity.
ApportVersion: 1.94.1-0ubuntu2
Architecture: i386
CompizPlugins: [core,bailer,
CompositorRunning: compiz
CrashCounter: 1
Date: Fri Mar 16 01:03:11 2012
DistUpgraded: Log time: 2012-02-20 08:44:55.720349
DistroCodename: precise
DistroVariant: ubuntu
ExecutablePath: /usr/bin/compiz
GraphicsCard:
Intel Corporation Mobile 4 Series Chipset Integrated Graphics Controller [8086:2a42] (rev 07) (prog-if 00 [VGA controller])
Subsystem: Dell Device [1028:02aa]
Subsystem: Dell Device [1028:02aa]
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Release i386 (20110427.1)
MachineType: Dell Inc. Inspiron 1545
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: Upgraded to precise on 2012-03-16 (0 days ago)
UserGroups: adm admin cdrom debian-tor dialout lp lpadmin plugdev sambashare vboxusers
dmi.bios.date: 05/13/2009
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A07
dmi.board.name: 0G848F
dmi.board.vendor: Dell Inc.
dmi.chassis.type: 8
dmi.chassis.vendor: Dell Inc.
dmi.modalias: dmi:bvnDellInc.
dmi.product.name: Inspiron 1545
dmi.sys.vendor: Dell 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.