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 got this crash when I run : unity --reset
This may be a duplicate of bug 737792
ProblemType: Crash
DistroRelease: Ubuntu 11.04
Package: compiz-core 1:0.9.4git20110
ProcVersionSign
Uname: Linux 2.6.38-7-generic i686
Architecture: i386
CompizPlugins: No value set for `/apps/
CompositorRunning: compiz
Date: Tue Mar 29 23:13:22 2011
DistUpgraded: Fresh install
DistroCodename: natty
DistroVariant: ubuntu
DkmsStatus: virtualbox-
ExecutablePath: /usr/bin/compiz
GraphicsCard: InnoTek Systemberatung GmbH VirtualBox Graphics Adapter [80ee:beef] (prog-if 00 [VGA controller])
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Alpha i386 (20110302)
InstallationMedia_: Ubuntu 11.04 "Natty Narwhal" - Alpha i386 (20110302)
Lsusb:
Bus 001 Device 002: ID 80ee:0021
Bus 001 Device 001: ID 1d6b:0001 Linux Foundation 1.1 root hub
MachineType: innotek GmbH VirtualBox
ProcCmdline: compiz --replace
ProcEnviron:
LANGUAGE=fr:en
LANG=fr_CA.UTF-8
LC_MESSAGES=
SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=
ProcVersionSign
Renderer: Software
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
dmi.bios.date: 12/01/2006
dmi.bios.vendor: innotek GmbH
dmi.bios.version: VirtualBox
dmi.modalias: dmi:bvninnotekG
dmi.product.name: VirtualBox
dmi.product.
dmi.sys.vendor: innotek GmbH
version.compiz: compiz 1:0.9.4git20110
version.libdrm2: libdrm2 2.4.23-1ubuntu5
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.