compiz crashed with signal 5 in Glib::exception_handlers_invoke()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
compiz (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
Messing around with external projector hotplugging. Perhaps compiz didn't care for that.
ProblemType: Crash
DistroRelease: Ubuntu 12.04
Package: compiz-core 1:0.9.7.
ProcVersionSign
Uname: Linux 3.2.0-17-generic i686
.tmp.unity.
ApportVersion: 1.92-0ubuntu1
Architecture: i386
CompizPlugins: [core,bailer,
CompositorRunning: compiz
CrashCounter: 1
Date: Tue Feb 21 21:17:59 2012
DistUpgraded: Log time: 2011-11-21 15:01:21.669957
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:0432]
Subsystem: Dell Device [1028:0432]
InstallationMedia: Ubuntu 11.10 "Oneiric Ocelot" - Beta i386 (20110921.2)
MachineType: Dell Inc. Latitude 13
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 2011-11-29 (83 days ago)
UserGroups: adm admin cdrom dialout lpadmin plugdev root sambashare
dmi.bios.date: 01/06/2010
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A00
dmi.board.name: 02CTPP
dmi.board.vendor: Dell Inc.
dmi.chassis.type: 8
dmi.chassis.vendor: Dell Inc.
dmi.modalias: dmi:bvnDellInc.
dmi.product.name: Latitude 13
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.