compiz.real assert failure: compiz.real: ../../src/xcb_io.c:542: _XRead: Assertion `dpy->xcb->reply_data != ((void *)0)' failed.
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
compiz (Ubuntu) |
New
|
Undecided
|
Unassigned |
Bug Description
Binary package hint: compiz
help, fix it, I love Ubuntu, I love you.
ProblemType: Crash
Architecture: i386
AssertionMessage: compiz.real: ../../src/
CompizPlugins: [core,move,
Date: Sat Oct 31 23:43:27 2009
DistroRelease: Ubuntu 9.10
ExecutablePath: /usr/bin/
MachineType: System manufacturer P5QL PRO
NonfreeKernelMo
Package: compiz-core 1:0.8.4-0ubuntu2
PciDisplay: 01:00.0 VGA compatible controller [0300]: ATI Technologies Inc RV730XT [Radeon HD 4670] [1002:9490]
ProcCmdLine: root=UUID=
ProcCmdline: /usr/bin/
ProcCwd: /home/guest
ProcEnviron:
LANG=en_US.UTF-8
SHELL=/bin/bash
ProcVersionSign
RelatedPackageV
xserver-xorg 1:7.4+3ubuntu7
libgl1-mesa-glx 7.6.0-1ubuntu4
libdrm2 2.4.14-1ubuntu1
xserver-
xserver-
Signal: 6
SourcePackage: compiz
StacktraceTop:
__kernel_vsyscall ()
raise () from /lib/tls/
abort () from /lib/tls/
__assert_fail () from /lib/tls/
_XRead () from /usr/lib/
Title: compiz.real assert failure: compiz.real: ../../src/
Uname: Linux 2.6.31-
UserGroups: adm admin audio cdrom dialout dip floppy fuse lpadmin netdev plugdev sambashare tape users video
dmi.bios.date: 03/12/2009
dmi.bios.vendor: American Megatrends Inc.
dmi.bios.version: 1001
dmi.board.
dmi.board.name: P5QL PRO
dmi.board.vendor: ASUSTeK Computer INC.
dmi.board.version: Rev 1.xx
dmi.chassis.
dmi.chassis.type: 3
dmi.chassis.vendor: Chassis Manufacture
dmi.chassis.
dmi.modalias: dmi:bvnAmerican
dmi.product.name: P5QL PRO
dmi.product.
dmi.sys.vendor: System manufacturer
system: distro = Ubuntu, architecture = i686, kernel = 2.6.31-
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 #431155, 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.