[Date Prev][Date Next] [Thread Prev][Thread Next] [Date Index] [Thread Index]

xmove problems, it should NOT be this hard!!!



    Ok, here's the problem I'm trying to solve.  I have a laptop on which I am
running Debian pretty much 24/7.  It is my "work machine" in that I try to
keep all productive work on that machine so if I ever need to travel I can pop
it out of it's dock, pack it up, and everything goes with me.  Thinderbird,
gaim, a few other applications are running on it constantly.  It is a Dell
Latitude CPx w/PIII-667Mhz processor and 256Mb of RAM.

    My main desktop is my "game" machine.  I use it mainly for games and
access the other machines as required.  As such it runs Win2k almost
exclusively.  However recently I installed Debian onto it so I could use it
for more productive uses as the needs and desires arise.  It is a homebuilt
with an AMD 2500+XP and 1Gb of RAM.

    So, slower, low-RAM laptop with cheap keyboard, mouse and 15" monitor on
it.  Faster desktop w/nice keyboard, mouse and 19" monitor on it.  Is it any
wonder then I want to use the desktop?  :)

    Problem is every time that I fire up Debian on the dekstop I don't want to
have to shutdown TBird, gaim, et al. just to pipe them through SSH to my
dekstop.  No way in hell am I messing with xauth manually!  I thought, "Well,
if there was something like screen for X I could just detach from one machine,
display to another!"  Enter xmove!  xmove is just that, "screen" for X instead
of ttys.

    So I fire up xmove and it dutifully tells me it is ready to work.  Great!
 I adjust my DISPLAY environment variable and have TBird point to xmove.  It
connects to xmove and displays on the laptop's screen.  Perfect!  I use
xmovectrl to tell xmove to now display to my desktop's screen.  It chokes.
The error message is that it cannot connect to the host.

    Ok, not a problem.  I do some Googling and come up with xauth.  Fine,
xauth list on the desktop, grab the cookie, xauth add onto the laptop.  So now
the laptop has the cookie needed to connect to the desktop's screen, right?
Give xmovectrl a try.  Cannot connect to host.  Not a problem!

    More Googling.  Hey, xhost!  I can just tell my desktop "screw
authorization, let connections from this machine through already!"  xhost
+[laptop's IP].  Try xmovectrl.  Cannot connect to host.  Fine.  Both the
desktop and laptop are behind my firewall on a private network.  If anyone is
behind the firewall I have more to worry about than my X session.  xhost +,
IE, let everyone into X!  Cannot connect to host.   ^%@#!!!!

    Fine, fine, fine.  I can create an SSH tunnel.  Perfect, really, as that
will let me script moving the program's display around.  SSH in to run the
command to moveall attach programs to the current display.  So ssh -X into the
laptop from the desktop and then tell xmove to display to the SSH tunnel and
get this from SSH (-v enabled): debug1: client_input_channel_open: ctype x11
rchan 3 win 65536 max 16384
debug1: client_request_x11: request from 127.0.0.1 39125
debug1: channel 1: new [x11]
debug1: confirm x11
X11 connection rejected because of wrong authentication.
debug1: channel 1: free: x11, nchannels 2

    Ok....  wrong authentication!?  What't the hell's going on now?  The
laptop's got the desktop's xauth cookie.  The desktop has xhost wide open to
the entire world.  The SSH tunnel is up and running fine; I'm using it right
now to write this!  So what bloody freakin' authentication does it freakin'
need!?  HELP!!!!  :D

-- 
         Steve C. Lamb         | I'm your priest, I'm your shrink, I'm your
       PGP Key: 8B6E99C5       | main connection to the switchboard of souls.
-------------------------------+---------------------------------------------

Attachment: signature.asc
Description: OpenPGP digital signature


Reply to: