non-obvious Error: Can't open display: unix:1.0
tex "at" off.org
Fri Jul 26 02:20:02 2002
Answered my own question. Apparently some apps need to be told the
explicit hostname in $DISPLAY, not just :1 or unix:1. It worked after
$DISPLAY was set to hostname:1. Not sure why that is. Maybe it's an app
On Tue, Jul 23, 2002 at 10:10:27PM -0700, Austin Schutz wrote:
> Running a commercial app, I get 'Error: Can't open display: unix:1.0'.
> It looks like possibly the app is using libxt? I get the following in
> truss output:
> 2901: stat("/tmp/.X11-pipe/X1", 0xFFBEDBC8) Err#2 ENOENT
> 2901: open("/export/src/X11/lib/X11/XtErrorDB", O_RDONLY) Err#2 ENOENT
> right before it writes the error message and quits. I am running:
> VNC viewer version 3.3.3r1 with SSH tunneling support
> on a linux 2.4 machine, X ver. 4.something. Server is solaris
> 8, same vnc version. Connection is made via an ssh tunnel.
> The app is spawned from a shell in an xterm window inside vncviewer.
> Other apps, such as xterm, _have no problems whatsoever_ being spawned
> thusly, and pop up in the vncviewer window just as one would expect.
> There are no interesting messages in .vnc/$DISPLAY.log, AFAICT.
> I tried symlinking /tmp/.X11-pipe to /tmp/.X11-unix. That didn't
> seem to have any effect. the 'stat("/tmp/.X11-pipe/X1"...)' would succeed
> but the app would still croak with the "Error: Can't open display: unix:1.0"
> I have browsed/searched the list archives and FAQ but not seen anything
> Thanks for any help/pointers!
> P.S. VNC Rocks! 10x faster than X direct over a cable modem connection!
> VNC-List mailing list
> VNC-List "at" realvnc.com