compiz crashed with SIGABRT in Glib::exception_handlers_invoke()
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
compiz (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
Binary package hint: compiz
I was just checking out the new changes in the Unity interface. I was clicking pretty fast and then it crashed.
ProblemType: Crash
DistroRelease: Ubuntu 11.04
Package: compiz-core 1:0.9.4+
ProcVersionSign
Uname: Linux 2.6.38-
Architecture: i386
CompizPlugins: [core,bailer,
CompositorRunning: compiz
Date: Sat Apr 16 17:35:07 2011
DistUpgraded: Fresh install
DistroCodename: natty
DistroVariant: ubuntu
ExecutablePath: /usr/bin/compiz
GraphicsCard:
nVidia Corporation G84 [Quadro FX 1700] [10de:040f] (rev a1) (prog-if 00 [VGA controller])
Subsystem: nVidia Corporation Device [10de:049a]
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Beta i386 (20110404)
InstallationMedia_: Ubuntu 11.04 "Natty Narwhal" - Beta i386 (20110404)
MachineType: Dell Inc. OptiPlex 745
ProcCmdline: compiz
ProcEnviron:
LANGUAGE=en_US:en
LANG=nl_NL.UTF-8
LC_MESSAGES=
SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=
ProcVersionSign
Renderer: Unknown
Signal: 6
SourcePackage: compiz
StacktraceTop:
Glib::
Glib::
g_main_
?? () from /lib/i386-
g_main_loop_run () from /lib/i386-
Title: compiz crashed with SIGABRT in Glib::exception
UpgradeStatus: No upgrade log present (probably fresh install)
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
XorgConf:
dmi.bios.date: 08/12/2008
dmi.bios.vendor: Dell Inc.
dmi.bios.version: 2.6.2
dmi.board.name: 0KW626
dmi.board.vendor: Dell Inc.
dmi.chassis.type: 6
dmi.chassis.vendor: Dell Inc.
dmi.modalias: dmi:bvnDellInc.
dmi.product.name: OptiPlex 745
dmi.sys.vendor: Dell Inc.
version.compiz: compiz 1:0.9.4+
version.libdrm2: libdrm2 2.4.23-1ubuntu6
version.
version.
version.
version.
version.
version.
version.
Thank you for taking the time to report this crash and helping to make Ubuntu better. This particular crash has already been reported and is a duplicate of bug #737792, 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.