Cool. Problems that solve themselves are my favorite kind. :)
> On May 28, 2014, at 4:01 AM, Paul Melis wrote:
>
> Okay, we figured out what was going on, the application in question
> created a new GLUT window explictly on :0.0. So VGL was not to blame...
>
> Paul
>
>> On 21-05-14 14:28, Pau
Okay, we figured out what was going on, the application in question
created a new GLUT window explictly on :0.0. So VGL was not to blame...
Paul
On 21-05-14 14:28, Paul Melis wrote:
> Here's a trace and the two pieces of xwininfo output (gui.info = :1,
> viewer.info = :0). I see an XCreateWindow
I've learned never to say that anything is impossible, because I usually
end up being proven wrong, but let's just say that if VirtualGL is
causing this, it is by way of an as-yet-undiscovered mechanism that I
can't at the present moment fathom. VirtualGL doesn't modify the
display argument of
Hi DRC,
I'm afraid sharing the app is a bit difficult...
I did some more testing on my home machine, using a TigerVNC server and
VirtualGL 2.3.3. What seems to be happening is that when I start the app
with vglrun within the VNC session the GUI window indeed ends up on
DISPLAY :1 in side the V
Unfortunately not. Is this something that could be readily reproduced
without using your cluster? That is, on a regular PC? Is the app
something I could download and test?
On 5/16/14 9:18 AM, Paul Melis wrote:
> Hi all,
>
> I'm trying to run a 32-bit application on a 64-bit Linux cluster und
