Bug 8527

Summary:	compiz can't handle large textures
Product:	xorg	Reporter:	Ioannis <i.nousias>
Component:	App/compiz	Assignee:	David Reveman <reveman>
Status:	RESOLVED NOTOURBUG	QA Contact:
Severity:	normal
Priority:	high
Version:	7.1 (2006.05)
Hardware:	x86 (IA32)
OS:	Linux (All)
Whiteboard:
i915 platform:		i915 features:

Description Ioannis 2006-10-06 05:57:10 UTC

I invoke compiz using:
compiz --replace --use-cow gconf
or
compiz --replace --use-cow --indirect-rendering gconf

with the first command, the desktop appears black. Windows that are larger than
a given size become black (except the decoration). Resizing them to something
smaller, makes them whole again. The problem seems to be related with the total
size of textures handle at the time, since the more windows are opened (visible)
the smaller they need to be to prevent them from appearing black.

with the second command the background desktop picture is shown, but not the
icons. It generally exhibits similar behavior, only here the windows stop being
redrawn instead of becoming black.

compiz reports this error (not always though):
compiz: pixmap <hex-value-here> can't be bound to texture
compiz: Couldn't bind redirected window <hex-value-here> to texture

I use the latest compiz from git, Xorg 7.1 from the Fedora core 5.92 (FC6T3)
repositories and the nvidia beta drivers 9625 on a GeForce go 4200 (NV28)

appart from the default, my xorg.conf contains these lines in the "screen" section:
 Option "RenderAccel" "true"
 Option "DisableGLXRootClipping" "True"
 Option "AddARGBGLXVisuals" "True"
 Option "AllowGLXWithComposite" "True"

and also this:
Section "Extensions"
 Option      "Composite" "Enable"
EndSection

(I've tried several combination without a success)

glxinfo reports:
direct rendering: Yes
and I can see
GLX_EXT_texture_from_pixmap
and
GL_ARB_texture_rectangle

There are no warnings or errors in my Xorg.0.log file or any related messages in
dmesg. My /proc/driver/nvidia/agp/status states:
Status:          Enabled
Driver:          AGPGART
AGP Rate:        4x
Fast Writes:     Disabled
SBA:             Disabled

(I use the Fedora kernel, which has agpgart build-in)

and I have cairo with glitz enabled at compile time.

Any ideas?

regards

Comment 1 Ioannis 2006-10-07 06:07:07 UTC

and ldd `which compiz` return this:
	linux-gate.so.1 =>  (0x0011e000)
	libpng12.so.0 => /usr/lib/libpng12.so.0 (0x06946000)
	libXcomposite.so.1 => /usr/lib/libXcomposite.so.1 (0x00288000)
	libXdamage.so.1 => /usr/lib/libXdamage.so.1 (0x001b2000)
	libXfixes.so.3 => /usr/lib/libXfixes.so.3 (0x00df8000)
	libXrandr.so.2 => /usr/lib/libXrandr.so.2 (0x00112000)
	libXrender.so.1 => /usr/lib/libXrender.so.1 (0x00ddf000)
	libXinerama.so.1 => /usr/lib/libXinerama.so.1 (0x00101000)
	libXdmcp.so.6 => /usr/lib/libXdmcp.so.6 (0x00d7e000)
	libXau.so.6 => /usr/lib/libXau.so.6 (0x00c75000)
	libSM.so.6 => /usr/lib/libSM.so.6 (0x00dc9000)
	libICE.so.6 => /usr/lib/libICE.so.6 (0x00dad000)
	libstartup-notification-1.so.0 => /usr/lib/libstartup-notification-1.so.0
(0x00270000)
	libGL.so.1 => /usr/lib/libGL.so.1 (0x007d5000)
	libXext.so.6 => /usr/lib/libXext.so.6 (0x00d9b000)
	libX11.so.6 => /usr/lib/libX11.so.6 (0x00c7a000)
	libdl.so.2 => /lib/libdl.so.2 (0x00c56000)
	libm.so.6 => /lib/libm.so.6 (0x00c2d000)
	libc.so.6 => /lib/libc.so.6 (0x00aee000)
	libz.so.1 => /usr/lib/libz.so.1 (0x00d86000)
	libGLcore.so.1 => /usr/lib/libGLcore.so.1 (0x05335000)
	libnvidia-tls.so.1 => /usr/lib/tls/libnvidia-tls.so.1 (0x002ca000)
	/lib/ld-linux.so.2 (0x0011f000)

Comment 2 Ioannis 2006-10-07 06:36:18 UTC

It might be an nvidia driver issue. I found more reports for this problem

http://www.nvnews.net/vbulletin/showpost.php?p=1002699&postcount=207

the issue is explained better there. The person who posted the above, concludes
it is related to the size of the available video ram.

Comment 3 Ioannis 2006-10-24 17:37:05 UTC

This is an nvidia bug:

http://www.nvnews.net/vbulletin/showpost.php?p=1003304&postcount=4

I'm setting this to "NOTOURBUG".

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.