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 any functions except GLX functions.
Can you send me a VGL trace of the application along with a list of the window handles (obtainable with xwininfo) from the window that is on display :1 and the window that is on display :0? On 5/20/14 4:37 PM, Paul Melis wrote: > 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 VNC session, but the rendering window ends up on > DISPLAY :0, i.e. outside the VNC session. I can't tell if the rendering > window starts out on :1 and then gets moved to :0 or if it is created on > :0 in the first place. > > It's a single-process app written with what looks like FLTK, so I would > expect both windows to just get created on the same X display. Is it > possible that VirtualGL causes the different displays to be used? > > Regards, > Paul ------------------------------------------------------------------------------ "Accelerate Dev Cycles with Automated Cross-Browser Testing - For FREE Instantly run your Selenium tests across 300+ browser/OS combos. Get unparalleled scalability from the best Selenium testing platform available Simple to use. Nothing to install. Get started now for free." http://p.sf.net/sfu/SauceLabs _______________________________________________ VirtualGL-Users mailing list VirtualGL-Users@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/virtualgl-users
