compiz assert failure: compiz: main/mipmap.c:43: bytes_per_pixel: Assertion `b >= 0' failed.
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
compiz (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
Binary package hint: compiz
Further information:
ProblemType: Crash
DistroRelease: Ubuntu 11.04
Package: compiz-core 1:0.9.2.
ProcVersionSign
Uname: Linux 2.6.37-12-generic i686
Architecture: i386
AssertionMessage: compiz: main/mipmap.c:43: bytes_per_pixel: Assertion `b >= 0' failed.
CompizPlugins: No value set for `/apps/
Date: Wed Jan 12 04:01:12 2011
ExecutablePath: /usr/bin/compiz
InstallationMedia: Ubuntu 11.04 "Natty Narwhal" - Alpha i386 (20101202)
MachineType: TOSHIBA Satellite L500
PciDisplay: 01:00.0 VGA compatible controller [0300]: ATI Technologies Inc M92 [Mobility Radeon HD 4500 Series] [1002:9553] (prog-if 00 [VGA controller])
ProcCmdline: /usr/bin/compiz
ProcEnviron:
LANGUAGE=en_AU:en
LANG=en_NZ.UTF-8
LC_MESSAGES=
SHELL=/bin/bash
ProcKernelCmdLine: BOOT_IMAGE=
RelatedPackageV
xserver-xorg 1:7.5+6ubuntu6
libgl1-mesa-glx 7.9+repack-1ubuntu3
libdrm2 2.4.22-2ubuntu1
xserver-
xserver-
Signal: 6
SourcePackage: compiz
StacktraceTop:
__kernel_vsyscall ()
raise () from /lib/libc.so.6
abort () from /lib/libc.so.6
__assert_fail () from /lib/libc.so.6
?? () from /usr/lib/
Title: compiz assert failure: compiz: main/mipmap.c:43: bytes_per_pixel: Assertion `b >= 0' failed.
UserGroups: adm admin cdrom dialout lpadmin plugdev sambashare
XorgConf: Error: [Errno 2] No such file or directory: '/etc/X11/
dmi.bios.date: 03/23/2010
dmi.bios.vendor: TOSHIBA
dmi.bios.version: V2.00
dmi.board.name: KSWAA
dmi.board.vendor: TOSHIBA
dmi.board.version: 1.00
dmi.chassis.
dmi.chassis.type: 10
dmi.chassis.vendor: TOSHIBA
dmi.chassis.
dmi.modalias: dmi:bvnTOSHIBA:
dmi.product.name: Satellite L500
dmi.product.
dmi.sys.vendor: TOSHIBA
system: distro = Ubuntu, architecture = i686, kernel = 2.6.37-12-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 #684745, 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.