GLX extension fails to initialize in Xvfb

[Dominik Röttsches]

I request to include the following patch from upstream
http://cgit.freedesktop.org/xorg/xserver/patch/?id=65642ccb78aa2d4c4e17b9ac42e4ef625c4a6e8b

From the ChangeLog:
Subject: vfb: Initialize the GLX extension again.

This should fix a regression in the 1.13.0 release: commit
5f5bbbe543f65c48ecbb5cce80116a86ca3fbe86 removed a code path used by Xvfb
and made it use the default one when initializing extensions. However, this
meant the GLX extension was not initialized anymore since it is not part of
the `staticExtensions' array.

Since it is not possible to just add it to that array after commit
aad428b8e21c77397c623b78706eb64b1fea77c9, adopt an approach similar to
xwin's and xquartz's and initialize the extension from vfb's `InitOutput'.

This has been merged into the mainline already and is bound to be release in 1.13.2 -

I kindly request inclusion into the 1.13.0 package on Ubuntu. We use xvfb for our testing scripts and we're dependent on GLX to function in it.

[Launchpad Janitor (janitor)]

Status changed to 'Confirmed' because the bug affects multiple users.

[Dominik Röttsches (drott)]

Original patch courtesy of Raphael Kubo da Costa.

[Timo Aaltonen (tjaalton)]

fixed in raring

[Dominik Röttsches (drott)]

Thanks Timo. I am trying to interpret the other status changes you edited - is this going to be fixed for Quantal as well?

[Timo Aaltonen (tjaalton)]

yes it is

[Dominik Röttsches (drott)]

Timo, can you give an estimate when there could be an updated package for Quantal? Thanks.

[Timo Aaltonen (tjaalton)]

quantal got EOL'd in the meantime, closing