Compiz crashes when trying to enable desktop effects.
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
compiz (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
Binary package hint: compiz
Using Karmic alpha 5, Compiz package version 1:0.8.2-0ubuntu16, Xorg 1.6.3 and version 185 of the proprietary Nvidia driver, Compiz crashes shortly after launch, preventing desktop effects from being enabled. This is occurring on a Dell Inspiron 1520 with a 2GHz Core 2 Duo T7250, 4GB of RAM, and GeForce 8400M GS with 128MB VRAM.
ProblemType: Crash
Architecture: i386
AssertionMessage: *** glibc detected *** /usr/bin/
CompizPlugins: [core,ccp,
CrashCounter: 1
Date: Fri Sep 4 12:45:23 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/bin/
MachineType: Dell Inc. Inspiron 1520
NonfreeKernelMo
Package: compiz-core 1:0.8.2-0ubuntu16
PccardctlIdent:
PccardctlStatus:
PciDisplay: 01:00.0 VGA compatible controller [0300]: nVidia Corporation G86 [GeForce 8400M GS] [10de:0427] (rev a1)
ProcCmdLine: root=UUID=
ProcCmdline: /usr/bin/
ProcEnviron:
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcVersionSign
RelatedPackageV
xserver-xorg 1:7.4+3ubuntu5
libgl1-mesa-glx 7.6.0~git200908
libdrm2 2.4.12+
xserver-
xserver-
Signal: 6
SourcePackage: compiz
StacktraceTop:
__kernel_vsyscall ()
raise () from /lib/tls/
abort () from /lib/tls/
?? () from /lib/tls/
?? () from /lib/tls/
Title: compiz.real assert failure: *** glibc detected *** /usr/bin/
Uname: Linux 2.6.31-9-generic i686
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
dmi.bios.date: 07/11/2008
dmi.bios.vendor: Dell Inc.
dmi.bios.version: A09
dmi.board.name: 0KY768
dmi.board.vendor: Dell Inc.
dmi.chassis.type: 8
dmi.chassis.vendor: Dell Inc.
dmi.modalias: dmi:bvnDellInc.
dmi.product.name: Inspiron 1520
dmi.sys.vendor: Dell Inc.
system: distro = Ubuntu, architecture = i686, kernel = 2.6.31-9-generic
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 #422391, 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.