Bug#784687: still not working from remote machine

[Dirk Griesbach <spamthis@freenet.de>]

Am Fr, 17. Jul 2015 um 21:02:34 -0700 schrieb Bill Brelsford:
> It also fails on the local machine if DISPLAY is specified as
> <hostname>:0 or localhost:0 (rather than :0).

I guess in this case a TCP-connection will be used rather than the local
unix socket. With -nolisten tcp as default, this would fail. If I try to
specify DISPLAY with localhost or hostname, I get an error like "Error:
Can't open display: localhost:0.0".

Maybe the behaviour was changed and in previous versions localhost was
not resolved to a TCP-connection because, hey its local, lets fall back
to/use unix sockets and now the distinction is more strict. But as I
said, right now I'm just guessing.

> Should I submit this as a separate bug?  I assumed it was related.

Let's try a new bug. If they are the same they can be merged later on.
But you can mention this one.

Dirk