[lsb-bugs] [Bug 2615] glXQueryServerString() returns NULL with lsb-Xvfb on Ubuntu 8.10
bugzilla-daemon at linux-foundation.org
bugzilla-daemon at linux-foundation.org
Wed Sep 8 15:41:59 PDT 2010
http://bugs.linuxbase.org/show_bug.cgi?id=2615
Stew Benedict <stewb at linux-foundation.org> changed:
What |Removed |Added
----------------------------------------------------------------------------
Target Milestone|4.1 |4.0
Severity|normal |major
--- Comment #2 from Stew Benedict <stewb at linux-foundation.org> 2010-09-08 15:41:58 PDT ---
Indeed, and not limited to Ubuntu.
2 Mandriva systems: 2009.0, 2010.1
2009.0:
[stew at pavilion ~]$ /opt/lsb/bin/Xvfb -ac -x GLX :2.0 &
[1] 4925
[stew at pavilion ~]$ _XSERVTransSocketOpenCOTSServer: Unable to open socket for
inet6
_XSERVTransOpen: transport open failed for inet6/pavilion.e-artisan.org:2
_XSERVTransMakeAllCOTSServerListeners: failed to open listener for inet6
[stew at pavilion ~]$ export DISPLAY=:2.0
[stew at pavilion ~]$ glxinfo
name of display: :2.0
display: :2 screen: 0
direct rendering: No (If you want to find out why, try setting
LIBGL_DEBUG=verbose)
server glx vendor string: SGI
server glx version string: 1.2
...
2010.1:
[stew at acer ~]$ /opt/lsb/bin/Xvfb -ac -x GLX :2.0 &
[1] 25676
[stew at acer ~]$ _XSERVTransSocketOpenCOTSServer: Unable to open socket for inet6
_XSERVTransOpen: transport open failed for inet6/acer.e-artisan.org:2
_XSERVTransMakeAllCOTSServerListeners: failed to open listener for inet6
[stew at acer ~]$ export DISPLAY=:2.0
[stew at acer ~]$ glxinfo
name of display: :2.0
Error: couldn't find RGB GLX visual or fbconfig
Simple test program confirms the original bug summary, that
glXQueryServerString() returns NULL in the second case.
For kicks, I tried lsb-moblin, which is based on newer Xorg sources. For that
build, I get glx support returned in both cases. But it leaves us in the
situation described in bug 2734, where a bunch of xts5 tests fail.
--
Configure bugmail: http://bugs.linuxbase.org/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.
More information about the lsb-bugs
mailing list