I've uploaded some screenshots as an example: http://www.botchco.com/alex/2048-error/
the new version of xscreensaver displays a separate instance on each head of a xinerama desktop. so in this case only the context running up again the 2048 limit (the right side) shows the error. When I turn off xinerama or run an older version of xscreensaver the corruption shown on the right side of the above images shows across the entire screen. Looks like a clearing problem. you can see there seems to be remnants of old whales and glxgears overlayed on the new scene. Alex --- Michel Dänzer <[EMAIL PROTECTED]> wrote: ... > > I downloaded the newest version of xscreensaver last night. the > new > > behavior is to create 2 instances of the GL hack based on the > xinerama > > info and display one on head head. the hack running on the first > head > > displays fine; the one running on the second head shows the > corruption. > > So it seems to have something to do with 2048. > > It wouldn't be as simple as clears not working (properly) >= 2048, > would > it? Can you capture the problem in screenshots? > > __________________________________ Do you Yahoo!? The New Yahoo! Shopping - with improved product search http://shopping.yahoo.com ------------------------------------------------------- This SF.net email is sponsored by: SF.net Giveback Program. SourceForge.net hosts over 70,000 Open Source Projects. See the people who have HELPED US provide better services: Click here: http://sourceforge.net/supporters.php _______________________________________________ Dri-devel mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/dri-devel
