Re: Can't use any display name other than :0.0

From: Dances With Crows (danSPANceswitTRAPhcrows_at_gmail.com)
Date: 03/18/05


Date: 18 Mar 2005 14:45:31 GMT

On Fri, 18 Mar 2005 14:14:57 GMT, Paul Coene staggered into the Black
Sun and said:
> I'm relatively new to linux, but I'm an old hand (20+) years with Unix
> in general and I've used alot of X windows. Recently, I've started
>
> %xterm
> it brings up an xterm as one might expect.
>
> If I type:
> %xterm -display "localhost:0"
> xterm Xt error: Can't open display: localhost:0

Yep. X is trying to use TCP/IP to connect to localhost. This may not
work. If you do "ps auxw | grep X", you'll probably see a line like so:

root 9492 0.1 4.6 19652 17976 ? S Mar17 1:00
/usr/X11R6/bin/X -nolisten tcp -auth /var/run/xauth/A:0-ZMuEvo vt7

...note the "-nolisten tcp". That makes it so that X won't listen for
TCP of any type. This makes it impossible to use the "normal" xhost
+foo method, or to use X-over-TCP at all.

> The same occurs with any display other than ":0.0"...
> I have xhost + set, so that should not be the problem.

AAAAH! Don't do that. Use "xhost +machine" or better yet, use ssh -X.

> I have three systems. Two of the 3 behave this way.

Find the ?dm config file where X is started. Mine's in
/usr/kde/3.3/share/config/kdm/Xservers since I'm using kdm on KDE 3.3.
gdm is probably /etc/X11/gdm/gdm.conf . Find the line where X is
started, delete the "-nolisten tcp" part of it. For gdm, make sure
"DisallowTCP=true" is commented out. Restart X and things should work
better.

On a local network, it's OK to use xhost and X-over-TCP. Over the wide
Net, use ssh -X (or ssh -Y) so your X traffic is encrypted. If you take
out the "-nolisten tcp" on the machines on your LAN, you might want to
block TCP 6000 at your gateway, just in case. HTH,

-- 
Matt G|There is no Darkness in Eternity/But only Light too dim for us to see
Brainbench MVP for Linux Admin /    mail: TRAP + SPAN don't belong
http://www.brainbench.com     /                Hire me! 
-----------------------------/ http://crow202.dyndns.org/~mhgraham/resume


Relevant Pages

  • Dog slow TCP on 100 megabit/s LAN
    ... I'm having some TCP connectivity problems involving a WinXP box, ... and a router to share internet access and have a LAN for those two machines. ... DHCP server disabled (I use fixed IP on WinXP & Linux) ...
    (comp.os.linux.networking)
  • Dog slow TCP on 100 megabit/s LAN
    ... I'm having some TCP connectivity problems involving a WinXP box, ... and a router to share internet access and have a LAN for those two machines. ... DHCP server disabled (I use fixed IP on WinXP & Linux) ...
    (comp.os.linux.setup)
  • Re: TOE brain dump
    ... > When they've sorted out these problems, regular TCP has caught ... The Linux net stack just isn't built to be offloaded. ... TOE engines will ... NIC across the PCI bus using jumbo-ethernet-like data frames. ...
    (Linux-Kernel)
  • Re: TOE brain dump
    ... >> When they've sorted out these problems, regular TCP has caught ... > The Linux net stack just isn't built to be offloaded. ... TOE engines will ...
    (Linux-Kernel)
  • Re: Dog slow TCP on 100 megabit/s LAN
    ... How much buffer you have on the linux box ?. ... Maximum thruput at TCP level is ... > and a router to share internet access and have a LAN for those two ... > similar performance when running WinXP on the AMD Duron box. ...
    (comp.os.linux.networking)