On Jan 10, 12:52 am, Alex Holkner [EMAIL PROTECTED] wrote:
On Jan 10, 2008 8:22 AM, mdboom [EMAIL PROTECTED] wrote:
glxgears seems to run fine. I have a nVidia Quadro FX 550 EPCI card.
I have attached the output of glxinfo.
I don't have many ideas.. it looks very much like an issue
[I'm resending this from the Google groups interface as my original e-
mail didn't seem to go through to the list].
glxgears seems to run fine. I have a nVidia Quadro FX 550 EPCI card.
I have attached the output of glxinfo.
Thanks for your help,
Mike
name of display: :0.0
display: :0 screen:
On Jan 10, 2008 8:22 AM, mdboom [EMAIL PROTECTED] wrote:
[I'm resending this from the Google groups interface as my original e-
mail didn't seem to go through to the list].
glxgears seems to run fine. I have a nVidia Quadro FX 550 EPCI card.
I have attached the output of glxinfo.
I don't
After installing pyglet, the first test fails with a segfault on RHEL4
(with a locally-compiled Python 2.5). Running in gdb gives the
traceback below. It seems to be segfaulting in libGL.so. The version
I have came with x.org 6.8.2-1.EL.33:
rpm -qf /usr/X11R6/lib/libGL.so
On 1/5/08, Alex Holkner [EMAIL PROTECTED] wrote:
On 1/5/08, mdboom [EMAIL PROTECTED] wrote:
After installing pyglet, the first test fails with a segfault on RHEL4
(with a locally-compiled Python 2.5). Running in gdb gives the
traceback below. It seems to be segfaulting in libGL.so.
