On 10/20/15 2:29 PM, Brian Hinz wrote: > I did a major re-write of the clipboard handler in the TigerVNC Java > viewer a while back, so this is an area where the TurboVNC viewer will > be significantly different. The best thing I can say is to try the > TigerVNC client and see. > > Issue #20 was fixed, but to be honest what Brett is describing sounds an > awful lot like issues that we struggled with in my customer's > environment for a long time. What I finally found was that there is an > undocumented '-poll' option to vncconfig that seemed to help > tremendously. I forget what we set this to, 100 IIRC. I have also > found that a lot of clipboard related problems seem to stem from having > multiple copies of vncconfig running. In our case, people were starting > it via their .login (or worse, .cshrc...). We've since moved to using > the /etc/xdg facility to auto-start a single copy on login and it's > worked great.
Good to know. I'll look at integrating your patches. TurboVNC runs vncconfig from within the vncserver script, so it shouldn't be starting multiple copies unless, like you said, someone is doing something "creative" like starting it themselves. One possible enhancement to that program would be for it to set a root window property saying that it's running, so that other copies can print an error message if you try to launch them on the same display (but there would be a "-force" option to override this.) Also, tvncconfig doesn't implement -poll, so that would be a good thing to do if it turns out that it helps. ------------------------------------------------------------------------------ _______________________________________________ TurboVNC-Users mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/turbovnc-users
