On Fri, 2010-05-14 at 10:14 +0200, Jo-Erlend Schinstad wrote:

I've been playing with x2go for a couple of days, and the only thing that comes to mind, is «wow». I've been using FreeNX for a long time, and one of the things I've been struggling with, is two-way audio. Using x2goserver-one, it just worked. I've only tried with Ubuntu on both client and server and I hope it works well with Windows and OS X clients too. If that's the case, then I'm definitely sold.

One question: is it possible to deactivate the magic pixel functionality in the upper-right corner and instead use a command to switch to the client OS? That would be awesome. <snip> I've also been wowed by X2Go. The audio works very well on Windows. I haven't played with audio on OSX yet. There are some tricks to getting sound to work consistently. I keep promising documentation but have been up to my eyeballs sorting our first major deployment. For example, setting Firefox/IceWeasel to use esd, setting KDE to use paplay for sounds.

One of the things I miss about the NoMachine implementation is the <CTL><ALT><T> sequence as a complement to the magic pixel. I find that, if a session mangles in full screen mode in X2Go, it is nearly impossible to get it back. We are tracking a problem where x2goagent shoots to 100% CPU utilization. When that happens, the session does not timeout but it is completely unresponsive. The only way to recover when in full screen mode appears to be to either restart X or restart the local desktop computer - neither of which are pretty if there are X apps running on the local desktop. Good luck and welcome - John