Bug#548211: pygtk FTBFS bug

[Daniel Schepler]

I'm not sure that the "extension RANDR missing" messages are necessarily the 
actual cause of the test failures.  I looked at an older build log on my 
machine where the build succeeded, and those messages are there as well but 
didn't prevent the tests from passing.

Old log:
make[2]: Entering directory `/tmp/buildd/pygtk-2.16.0/build-2.5/tests'
/usr/bin/make  check-local
make[3]: Entering directory `/tmp/buildd/pygtk-2.16.0/build-2.5/tests'
Xlib:  extension "RANDR" missing on display ":99.0".
.........................Xlib:  extension "RANDR" missing on display ":99.0".
Xlib:  extension "RANDR" missing on display ":99.0".
.........................................................................
----------------------------------------------------------------------
Ran 98 tests in 0.720s

OK
make[3]: Leaving directory `/tmp/buildd/pygtk-2.16.0/build-2.5/tests'

Recent log:
make[2]: Entering directory `/tmp/buildd/pygtk-2.16.0/build-2.5/tests'
/usr/bin/make  check-local
make[3]: Entering directory `/tmp/buildd/pygtk-2.16.0/build-2.5/tests'
Xlib:  extension "RANDR" missing on display ":99.0".
.........................Xlib:  extension "RANDR" missing on display ":99.0".
Xlib:  extension "RANDR" missing on display ":99.0".
..
Gdk-CRITICAL **: _gdk_drawable_get_source_drawable: assertion `GDK_IS_DRAWABLE 
(drawable)' failed
aborting...
make[3]: *** [check-local] Aborted
make[3]: Leaving directory `/tmp/buildd/pygtk-2.16.0/build-2.5/tests'
-- 
Daniel Schepler