Please do not reply to this email: if you want to comment on the bug, go to    
       
the URL shown below and enter yourcomments there.     
   
https://bugs.freedesktop.org/show_bug.cgi?id=9456          
     
           Summary: White screen issues with beryl and mesa 6.5.2 (no, not
                    glproto mismatch)
           Product: Mesa
           Version: 6.5
          Platform: PC
        OS/Version: Linux
            Status: NEW
          Severity: normal
          Priority: P2
         Component: Mesa core
        AssignedTo: mesa3d-dev@lists.sourceforge.net
        ReportedBy: [EMAIL PROTECTED]


Yesterday I updated these things in our distribution:
- mesa 6.5.2
- xorg-server 1.1.1 with patch to build with mesa 6.5.2 sources (taken from 
fedora)
- all drivers updated to include latest DRI drivers from mesa 6.5.2 and latest
2D drivers from xf86-video-* releases

With these updates, beryl redraws parts of the screen as white parts. Some, but
not all, shadows appear as white borders and some parts of the screen are
covered in white squares.

This problem is always reproducible, until I remove libGL.so which came with
mesa 6.5.2, and replace it with the libGL.so from our 6.5.1 package. At that
moment, all shadows are drawn fine, all redraws are fine and no white parts are
visible at the screen anymore. At that moment Xorg still uses 6.5.2 for AIGLX (I
didn't restart X after replacing the library), all drivers are still from 6.5.2
and the rest of mesa is also from 6.5.2.

When I run glxinfo with this older version of libGL, I get these errors:
DISPATCH ERROR! _glapi_add_dispatch failed to add glAreTexturesResident!
DISPATCH ERROR! _glapi_add_dispatch failed to add glGenTextures!
DISPATCH ERROR! _glapi_add_dispatch failed to add glIsTexture!
libGL warning: 3D driver claims to not support visual 0x4b

The last warning is the same I get with 6.5.2 libGL.so and is related to the
R200 drivers not implementing that, which doesn't have anything to do with this
bugreport.

My guess is that the above error messages could be a good pointer to find out
what's wrong. Looking at the name of the functions, it's plausible that textures
aren't initialized correctly with the new method used by mesa 6.5.2.          
     
     
--           
Configure bugmail: https://bugs.freedesktop.org/userprefs.cgi?tab=email         
     
------- You are receiving this mail because: -------
You are the assignee for the bug, or are watching the assignee.

-------------------------------------------------------------------------
Take Surveys. Earn Cash. Influence the Future of IT
Join SourceForge.net's Techsay panel and you'll get the chance to share your
opinions on IT & business topics through brief surveys - and earn cash
http://www.techsay.com/default.php?page=join.php&p=sourceforge&CID=DEVDEV
_______________________________________________
Mesa3d-dev mailing list
Mesa3d-dev@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mesa3d-dev

Reply via email to