http://bugs.winehq.org/show_bug.cgi?id=15636
--- Comment #6 from Jörg Höhle hoehle@users.sourceforge.net 2008-12-10 12:52:12 ---
I've observed that versions of Wine around 1.0..1.1.2 manage to display *some* background (i.e. grey rectangles)
More precisely, the change between 1.1.2 and 1.1.3 14b24058d69d73ebf6b70bc36c8aa62993351079 is first bad commit commit 14b24058d69d73ebf6b70bc36c8aa62993351079 Author: Stefan Dösinger stefan@codeweavers.com Date: Mon Jul 28 11:41:02 2008 -0500 wined3d: GL_ARB_fragment_program ffp implementation. broke the rendering of grey building rectangles.
Very old versions of wine, e.g. 0.9.57, behave much like 1.1.3-1.1.10: no background is drawn at all. Sadly, I cannot identify what commit enabled the greyscale rectangles, as I too often get crashes during regression testing. It happened somewhere between 0.9.57 and 1.0-rc1.
I thought that the missing background might be some hardware driver issue. So I tried and switched to software rendering instead, using a recent enough version of XOrg/Mesa, as found in Ubuntu Intrepid (previous tests were with Ubuntu Hardy).
LIBGL_ALWAYS_SOFTWARE=yes changes nothing to rendering (except it's dog slow) LIBGL_ALWAYS_INDIRECT=yes crashes the Xorg server (version 1.5.2, Ubuntu Intrepid)
Do the identical results with LIBGL_ALWAYS_SOFTWARE eliminate the possibility of a bug in the Intel XOrg driver? Does *_ALWAYS_SOFTWARE act like a portable, hardware-independent display driver so one could "prove" bugs must be somewhere else?