Problems accessing Xnested or Xephyr display from remote machine, Xauth issue?

Pipeline79 · 06-18-2019, 09:14 AM

OK,

I've been playing around with using a Linux laptop to remotely display applications from my Linux PC over X, both running Slackware. After a lot of trial and error, I've got the remote apps/clients from the PC to come up consistently on the same screen (:0.0) as my laptop desktop. This is with the 'vanilla' X11 forwarding which requires me to start my laptop xsession with the -listen tcp argument to open the X ports.

However, I'd like to open a screen with Xephyr/Xnest and put it on the next workspace and run a remote window manager like MWM on that and switch between the two.

The problem I'm having is that if I try and open anything from the remote host to put on screen [laptop.ip.address]:1.0 it just 'fails' to open that display.

When I run the Xephyr command, I use the -ac option, which should allow remote access.

The annoying thing is I had this working the other day, but I was getting all kinds of problems logging out and back into X on both computers because of something to do with the .Xauthority file in the home directory. .X0-lock files in /tmp and 'missing' .server#### in /home. Therefore, I deleted the .Xauthority file (which creates a clean one) and that's gone away.

If I use the "xauth list" command on my laptop, I now only have a magic cookie for the laptop itself, screen :0. So, I'm thinking that's the problem. But what is the correct way to deal with this? Of course, I could be completely wrong.

EDIT: I don't think it is xauth now, because I'm using the xhost +ipaddress command as well, which overrides the magic cookie check, and it still won't open the Xephyr display.

Sorry if that's a long rambling question, but I'm trying to give as much useful information as is relevant.

linuxgeex · 03-25-2020, 09:48 PM

I have the same issue and I get complaints that Xephyr doesn't implement the security extension.

What works:

Code:

$ LOCAL_IP=10.0.3.100
$ REMOTE_IP=10.0.3.135
$ X_DPY=:10

$ Xephyr $X_DPY -glamor -screen 1600x900x24 -listen TCP

$ DISPLAY=:10 xterm;

.. then at the xterm in the Xephyr X server:

Code:

$ compton &>/dev/null </dev/null &  # really helps with performance
$ xhost +$REMOTE_IP

... then at the remote host:

Code:

$ fluxbox $LOCAL_IP &>/dev/null </dev/null &

... after that you can close the xterm and launch remote apps from fluxbox

Bizzarely, if you issue that xhost command from anywhere other than a terminal running in Xephyr, it gets ignored. If you close that terminal, poof, you can no longer connect, unless you have a persistent connection from the remote already, which is the role fluxbox performs.

[GUMP]And that's all I have to say about that[/GUMP]