Bug 6371

Summary: Compiz: MaxTextureSize Bug with xorg-radeon-driver
Product: xorg Reporter: Erik Vetters <evetters>
Component: App/compizAssignee: David Reveman <reveman>
Status: CLOSED FIXED QA Contact:
Severity: normal    
Priority: high CC: erik.andren
Version: 7.0.0   
Hardware: x86 (IA32)   
OS: Linux (All)   
Whiteboard:
i915 platform: i915 features:

Description Erik Vetters 2006-03-24 10:56:41 UTC 
Hi,

I discoverd the following bug in compiz with radeon xorg driver since version
0.0.3 and later I can't maximize windows more than 600x600 neither with the
maximize button nor manually by mouse.

I discoverd that when I remove all the code that contains maxSize from
src/window.c, that I don't have the problems. See [1] for diff ( line 88 and 143).

I have read that all "Display" Stuff in XGL are textures. Maybe the compinition
of radeon-xorg-driver/Xgl/compiz causes that the maxTexturesSize
is not correct detect. Do not know if it is a Xgl or compiz problem. 
But it does no happen with fglrx.

It is not only me, some people at ubuntuforums.org have same problems.


System:
- Ubuntu up2date Dapper Drake.
- ATI Technologies Inc Radeon R250 Lf [FireGL 9000] (rev 02)
- Xorg 7.0.0 
- ATI driver (version 6.5.7)


Many thx for compiz .... :-)

Erik 

[1] http://webcvs.freedesktop.org/xorg/app/compiz/src/window.c?r1=1.4&r2=1.5
Comment 1 Erik Andren 2006-04-06 17:51:36 UTC 
Do you still expereience this problem?
(Assigning to David Reveman)
Comment 2 Erik Vetters 2006-04-07 02:04:10 UTC 
(In reply to comment #1)
> Do you still expereience this problem?
> (Assigning to David Reveman)

I switched back to normal xorg since it was a little frustrating. Will compile
latest cvs version this evening and cross my fingers ;-)


erik
Comment 3 Erik Vetters 2006-04-07 19:18:03 UTC 
Wow ... it is gone. Chapeau !

Working now with latest cvs version of xorg and compiz 0.0.8. 

Many thx 
Erik

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.