To answer your other question, RE: testing this, I don't have any ideas
of what to test. I can't make the glXUseXFont() function fail in
TigerVNC using "toy" applications, so I'm not sure what Oasys Primer is
doing differently to make it fail. Can you test using the latest
version of VirtualGL (2
It's extremely odd that anything would work in TurboVNC and then fail in
TightVNC, since TurboVNC was originally based on TightVNC 1.3.10.
However, TurboVNC does have a lot of bug fixes relative to TightVNC,
since our code base has continued to evolve after TightVNC 1.3.x was
abandoned.
VirtualGL
I tried some more cases, running the application
on the local x server with VGL and running with TightVNC.
All X servers except TurboVNC gives
the same error when running the application with VGL.
The application works using the X servers
build in OGL implementation. Mesa in the case of the VNC se
It works fine with TurboVNC.
Thanks for the tip, I will try the TigerVNC
list.
--
Filip Gedell
Software Engineer
Gridcore AB
Aschebergsgatan 46
411 33 Göteborg
Phone: +46 31 18 21 60
Cell: +46 733 18 21 62
From:
DRC
To:
virtualgl-users@lists.sourceforge.net,
Date:
2011-1
Does it happen with TurboVNC as well? If not, then please forward to
tigervnc-users. If so, then is it possible to obtain a copy of the app
for testing?
On 12/7/11 2:09 AM, filip.ged...@gridcore.se wrote:
> Hi,
>
> We are trying to run Oasys Primer using TigerVNC and VGL.
>
> The application
Hi,
We are trying to run Oasys Primer using TigerVNC and VGL.
The application starts and the process is reading event data from the X
socket. The problem is that the ui is not updating and not responding to
any user input.
Enabling VGL_TRACE shows that a call to glXUseXFont seems to fail and