Vnc connect to display 01/4/2023 ![]() Is there something to be done about that?Īpparently, x11vnc has some magic when it comes to keyboard repeat, to work around problems with certain VNC clients. ![]() > Following your prescription works mostly well but has the consequence of > One solution which can be used with current TL versions is to run vncviewer It has the potential to use the graphics hardware more efficiently compared to drawing in Pbuffers and copy from there, and avoids the need to run vglrun for OpenGL binaries. #Vnc connect to display 0 software#In situations where one can reserve a graphics card for a single user, letting such software render in an actual framebuffer, using vendor graphics drivers, solves such compatibility problems. As we have seen, there exists software which does not play well with a vnc server, one example being the GNOME 3 desktop environment. The idea to add x11vcn functionality to the Xvnc binary sounds excellent. > profile selector, one of them being :0. This would make it possible to present different options in the > normal Xvnc binary, then allow it to switch to exporting another display at > crazy idea would be to actually add x11vnc/x0vncserver functionality to the > that we cannot use the profile selector to choose session type. > tl-xinit to launch x11vnc instead of Xvnc. > If we want to get rid of Xvnc+vncviewer, it would in principle be possible for Tl-console-connect - fixes problem with "password check failed" ![]() Updated tl-console-connect no longer depends on TLSESSIONDATA Tl-console-connect updated for ThinLinc 4.5.0 Xstartup.d/99-save-env.sh - for ThinLinc 4.2.0 and earlier Tl-in-session - wrapper to execute commands in the TL session from outside Console-profile.hconf - Profile selector snippet ![]()
0 Comments
Leave a Reply.AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |