Did you try my suggestions? Even if they worked, I need to know so I can document the issue.
On Friday, June 1, 2018 at 10:35:40 AM UTC-5, DRC wrote: > > VGL servers do not have to be headless, but logging in and logging out of > the 3D X server could cause problems in the following ways: > > 1. In many cases, logging in at the server console causes the permissions > on the framebuffer device to be reassigned to whichever account is logging > in. vglserver_config is supposed to modify the system appropriately to > ensure that members of the vglusers group or all local users (depending on > which option you selected when running vglserver_config) retain permission > to the framebuffer device, but perhaps this is not working on your system > for some reason. The OpenGL 0x502 error could be caused by inappropriate > access to the framebuffer device. If you can reproduce the error reliably, > double check the framebuffer device permissions when it occurs. If they are > somehow being set incorrectly, then I can investigate that. > > 2. When you log in and back out of the 3D X server, this will change the > cookie that VGL uses to access the 3D X server > (/etc/opt/VirtualGL/vgl_xauth_key). Since that cookie is normally merged > into a user’s ~/.Xauthority file when vglrun is executed, it’s possible > that logging in and back out of the 3D X server could cause 3D applications > that are already running to lose access to the 3D X server. VGL makes a > connection to the 3D X server only when it needs to— generally whenever the > application makes a GLX call for the first time. It seems unlikely that you > would be logging in to the 3D X server during the brief period between the > application starting and VGL making the necessary connection to the 3D X > server, but perhaps VGL is unable to make that connection while you are > logged in. That is also something I can investigate. > > As far as the LXDE problem, that sounds like more of a TurboVNC problem. > The first thing I’d try to remedy that issue is to start the TurboVNC > Server session with /opt/TurboVNC/bin/vncserver -composite. If that works, > I’ll make a note of it in the TurboVNC Window Manager Compatibility Report. > If not, I’ll have to investigate further. > > -- You received this message because you are subscribed to the Google Groups "VirtualGL User Discussion/Support" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/virtualgl-users/6d50d8ca-bc94-4518-a2ca-358666e87360%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
