Re: X forwarding problem with SSH.

[Dan Christensen <jdc@uwo.ca>]

In message <[🔎] Pine.GSO.4.10.10109051329350.27175-100000@miris.lcs.mit.edu>
"C. Scott Ananian" <cananian@lesser-magoo.lcs.mit.edu> writes:

> I installed a machine from debian unstable a few weeks ago, and I've been
> utterly unable to get X forwarding to work when logging into the machine
> remotely. 

I'm having what sounds like the same problem.  See bug #96709

  http://bugs.debian.org/cgi-bin/bugreport.cgi?bug=96709&repeatmerged=yes

Additional information for the BTS:

  ssh to scratchy.  Then:
  
  jdc@scratchy:~$ echo $DISPLAY
  scratchy:10.0
  jdc@scratchy:~$ xauth list
  192.168.1.1:0  MIT-MAGIC-COOKIE-1  
  scratchy/unix:0  MIT-MAGIC-COOKIE-1 
  192.168.1.1:0  XDM-AUTHORIZATION-1      (this column deleted)
  scratchy/unix:0  XDM-AUTHORIZATION-1 
  hs240-108.onemeg.uwo.ca:0  MIT-MAGIC-COOKIE-1 
  hs240-108.onemeg.uwo.ca:0  XDM-AUTHORIZATION-1 
  hs240-230.onemeg.uwo.ca:0  MIT-MAGIC-COOKIE-1  
  hs240-230.onemeg.uwo.ca:0  XDM-AUTHORIZATION-1 
  jdc@scratchy:~$ env | grep -i xauth
  jdc@scratchy:~$ ls -l .Xauthority 
  -rw-------    1 jdc      jdc           404 Sep  2 23:16 .Xauthority

My machine uses pppoe to connect to the outside world, so its official
hostname changes from time to time.  Could this be related?

Adam McDaniel <adamm@psynch.com> writes:

> With the xserver running run the command in an shell prompt:
> $ xhost +
>
> That'll disable X security while you debug the issue.

This doesn't help me.

Dan