[Chimera-users] Fwd: Re: GLXBadRenderRequest

Greg Couch gregc at cgl.ucsf.edu
Thu Oct 21 14:44:09 PDT 2010

(Forgot to reply to list.)

-------- Original Message --------




On 10/18/2010 01:56 PM, Gough, Erik S wrote:
> Hello,
> I am receiving the following error when I try and open a structure 
> running chimera with Mesa 7.0 on Debian 5.
> X Error of failed request:  GLXBadRenderRequest
>   Major opcode of failed request:  148 (GLX)
>   Minor opcode of failed request:  1 (X_GLXRender)
>   Serial number of failed request:  5334
>   Current serial number in output stream:  5336
> I am assuming that this is related to running an older version of the 
> Mesa driver, but I do not have root on the system and the 
> administrators are hesitant of upgrading the Mesa package in /usr/lib 
> to anything beyond the stable release.   The servers do not have 
> access to any hardware based video so doing an updated hardware based 
> driver install won't help either.   I am limited to what I can do and 
> only have access to my home directory.  Would it be possible for me to 
> compile a newer version of the Mesa driver in my home directory and 
> then compile chimera to use that version of the driver instead of the 
> default in /usr/lib?
> Thanks!

If the Debian 5 system is a server, I would remote mount my home 
directory on my workstation with the hardware graphics driver, and run 
chimera locally.  Or you might be able to copy libGL.so from your 
workstation to a directory in your home directory on the server and set 
the LD_LIBRARY_PATH environment variable to that directory.

If the Debian 5 system is supposed to be a workstation, I would be very 
tempted to reboot it with a Ubuntu Live CD and when done, reboot it back 
to Debian 5, or maybe the administrators would be willing to make it a 
dual-boot system.  Your idea, of compiling a software-only version of 
Mesa, should work if you set the LD_LIBRARY_PATH environment variable 

In the LD_LIBRARY_PATH cases above you would need to start chimera from 
the command line after setting up the environment or start chimera after 
editing the CHIMERA/bin/chimera shell script.

     Hope this helps,


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://plato.cgl.ucsf.edu/pipermail/chimera-users/attachments/20101021/8488b3ca/attachment.html>

More information about the Chimera-users mailing list