TurboVNC error after rebooting server

[Wei Liu]

I recently upgrade my client side from windows 7 to windows 10, and suddenly the vnc session that I created with TurboVNC stop working. Here is the error that I got when running TurboVNC viewer on new Windows 10 ( the TurboVNC version is 2.1.1): 

===== begin error =====

...

QPainter::begin: Paint device returned engine == 0, type: 3
QPainter::setPen: Painter not active
QPainter::setFont: Painter not active
QPainter::begin: Paint device returned engine == 0, type: 3
QPainter::setPen: Painter not active
QPainter::setFont: Painter not active
QOpenGLShaderProgram: could not create shader program
QOpenGLShader: could not create shader
Could not link shader program:
 ""
[VGL] ERROR: OpenGL error 0x0502
[VGL] ERROR: in readPixels--
[VGL]    454: Could not Read Pixels

===== end of error =======

Any one has seen this before? Any insights? This tool is now critical to me. (I just verified that other people has same issue, so it's not my new Windows 10's problem, but something on server side. I rebooted the server recently)

Thank you very much. 

[Wei Liu]

hmm. Right after I sent the message, I fixed it by re-run vglserver_config. No idea why I need to re-run it after reboot, but now I can have 3D application working. 

Thanks!

[DRC]

OK, glad it's working. The only time I've ever seen 0x0502 is when the
3D X server was non-headless and someone switched to a different virtual
console on the server, thus effectively disconnecting the GPU from the
physical display. However, I suppose that error could also occur if the
framebuffer device permissions were incorrect, and running
vglserver_config would definitely fix that. It may not be clear in the
documentation, but it's always a good idea to re-run vglserver_config
after updating the nVidia or AMD proprietary drivers, because those
driver installers may change some of the device permissions.