Bug#784687: still not working from remote machine

2015-07-18 Thread Bill Brelsford
On Sat Jul 18 2015 at 09:37 AM +0200, Dirk Griesbach wrote: > 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. That's my problem. I somehow missed it in the changelog. Adding the new "-listen tcp" fixes it. T

Bug#784687: still not working from remote machine

2015-07-18 Thread Dirk Griesbach
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 > :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.

Bug#784687: still not working from remote machine

2015-07-17 Thread Bill Brelsford
It also fails on the local machine if DISPLAY is specified as :0 or localhost:0 (rather than :0). Should I submit this as a separate bug? I assumed it was related. Bill -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble? Contact list

Bug#784687: still not working from remote machine

2015-07-01 Thread Bill Brelsford
Access is still denied to another machine. E.g., rsh from machine foo to bar (or ssh and change DISPLAY to foo:0) and open an xterm. Get "access denied". Worked before 1.17.1. Bill -- To UNSUBSCRIBE, email to debian-bugs-dist-requ...@lists.debian.org with a subject of "unsubscribe". Trouble?