tsclient should recognize Xephyr for XDMCP login

[Pat Double]

Binary package hint: tsclient

Please forgive my ignorance if I am mistaken, but I believe Xephyr is a superior alternative to Xnest. I think tsclient should recognize Xephyr for XDMCP logins in addition to Xnest. I installed xserver-xephyr but tsclient did not recognize it. Unfortunately the arguments to Xnest and Xephyr are not the same.

[LCID Fire (lcid-fire)]

I second that. This would resolve my bug #228977

[juicemansam (juicemansam)]

I'd prefer the detection by tsclient, but this can be easily solved by making a link to Xephyr (ie. ln -s Xephyr Xnest).

[Pat Double (patdouble)]

Did you try making the link? I tried that at the time of the bug report and it did not work because the arguments to Xephyr and Xnest are different. See my initial comments.

[Onno Benschop (onno-itmaze)]

The arguments for Xephyr and Xnest appear to be mostly the same.

The call that tsclient makes is:
 Xnest :1 -once -geometry 1024x768 -query 127.0.0.1

The equivalent Xephyr call is:
 Xephyr :1 -once -screen 1024x768 -query 127.0.0.1

I'd not be surprised if there are other parameters that tsclient sends with different options. I've created a tiny bash script which substitutes geometry with screen.

To make this work, place the script in /usr/bin as Xnest (making sure you rename Xnest first (I use Xnest.bin)

[David Ayers (ayers)]

It seems that a newer upstream release (2.0.1) may support Xephyr yet I haven't been able to build it yet on Lucid:

http://sourceforge.net/projects/tsclient/

[AtesComp (atescomp)]

Here is a patch to use Xephyr. It worked well for me on Ubuntu 9.10. Not much to it.

[AtesComp (atescomp)]

Here is an updated patch for Maverick.
Apply all patches (tsclient/debian/patches/) in order to the Maverick branch, then this one.

[Andrea Corbellini (andrea.corbellini)]

Closing this bug as tsclient is no longer in the Ubuntu archives (starting from Oneiric).
The default remote desktop client in Ubuntu is now Remmina.