Description of problem:
sympy tests are failing when they try to import pyglet.window. This is reproduced by the following simplified test case:
$ xvfb-run -a python -c 'import pyglet.window'
libGL error: No matching fbConfigs or visuals found
libGL error: failed to load driver: swrast
Traceback (most recent call last):
File "<string>", line 1, in <module>
File "/usr/lib/python2.7/site-packages/pyglet/window/__init__.py", line 1817, in <module>
File "/usr/lib/python2.7/site-packages/pyglet/gl/__init__.py", line 205, in _create_shadow_window
_shadow_window = Window(width=1, height=1, visible=False)
File "/usr/lib/python2.7/site-packages/pyglet/window/xlib/__init__.py", line 163, in __init__
super(XlibWindow, self).__init__(*args, **kwargs)
File "/usr/lib/python2.7/site-packages/pyglet/window/__init__.py", line 510, in __init__
raise NoSuchConfigException('No standard config is available.')
pyglet.window.NoSuchConfigException: No standard config is available.
I'm not really sure if this is a pyglet bug, feel free to reassign as appropriate. This appears only to happen when the software rasterizer
is used, on a "real" system, this command works just fine.
Version-Release number of selected component (if applicable):
https://bugzilla.redhat.com/show_bug.cgi?id=904851#c5 seems to work-around the problem. Should xvfb-run do that by default?
Relevant quotes from that bug:
> If you don't specify, Xvfb starts at 8bpp, and there's no GLX support for 8bpp anymore.
> So apparently, `xvfb-run -s "-screen 0 640x480x24" glxinfo` runs fine, but doesn't work in mock.
The bug is in interaction between xvfb-run and GLX. The bug report there was closed "NOTABUG", and there's not much Pyglet can do about this, unforunately.
If you want to discuss changing xvfb-run defaults, I suggest filing a new bug: I don't think a Python backtrace would be useful to X devs.
*** This bug has been marked as a duplicate of bug 904851 ***