On Sat, Sep 10, 2011 at 9:43 PM, Kevin Van Workum <v...@sabalcore.com>wrote:
>
>> The roundabout way is: Set the environment variable LIBGL_ALWAYS_INDIRECT
>> to "yes" in the shell you run the graphics application from.
>>
>
> That does't have any effect for me.
> $ rpm -q mesa-libGL
> mesa-libGL-6.5.1-7.7.el5
>
>
>> The permanent way is: On linux, you need replace mesa-glx with mesa-swx,
>> on Ubuntu thats 'libgl1-mesa-swx' package which replaces 'libgl1-mesa
>> -glx'.
>>
>
> I'm on Centos 5 and don't seem to have mesa-glx nor can I find it or
> mesa-swx in the standard repos. Any suggestions?
>
>
its either $ export LIBGL_ALWAYS_INDIRECT=yes
or
$ export LIBGL_ALWAYS_SOFTWARE=1
Although Im pretty sure they mean same thing, and yes | 1 | true are
interchangeable values.
What are your symptoms? blank screen/window? If so, then maybe try "vglrun
-d $DISPLAY app_name" even though you've got turbovnc on the right display,
the mesa is rendering to another display and vglrun may help getting it onto
the vnc one...
Shanon
------------------------------------------------------------------------------
Malware Security Report: Protecting Your Business, Customers, and the
Bottom Line. Protect your business and customers by understanding the
threat from malware and how it can impact your online business.
http://www.accelacomm.com/jaw/sfnl/114/51427462/
_______________________________________________
VirtualGL-Users mailing list
VirtualGL-Users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/virtualgl-users