bad display name

[jonathan kean]

Christian,

 I ran into the same problem on SuSE 6.1, kernel 2.2.9.

 You need to specify the server number that you want to use on the command
line, i.e. 'vncserver :2' or whatever is an available X display number.  Do
that and everything seems to work OK, a bit slow if you are using the KDE
environment, but OK.

 I believe that vncserver is supposed to automagically detect the next
available display number and start Xvnc accordingly if run with no arguments. I
haven't been able to figure out why it doesn't under SuSE, maybe an environment
variable is being set differently?

jon

> -----Original Message-----
> From: owner-vnc-list "at" uk.research.att.com
> [mailto:owner-vnc-list "at" uk.research.att.com]On Behalf Of Christian
> Rogalla
> Sent: Tuesday, June 29, 1999 17:29
> To: vnc-list "at" uk.research.att.com
> Subject: bad display name
>
>
> Hi,
> using suse 6.1, with kernel 2.2.5 on a intel based platform
> and install vncserver version 3.3.2.
> When starting vncserver I get the following message
>
> anduin:~ # vncserver
> xauth: (argv):1:  bad display name "anduin:" in "add" command
> xauth: (argv):1:  bad display name "anduin/unix:" in "add" command
>
> New 'X' desktop is anduin:
>
> Starting applications specified in /root/.vnc/xstartup
> Log file is /root/.vnc/anduin:.log
>
>
> the logfile looks like
>
> 29/06/99 14:44:36 Xvnc version 3.3.2r3
> 29/06/99 14:44:36 Copyright (C) 1997-8 Olivetti & Oracle Research
> Laboratory
> 29/06/99 14:44:36 See http://www.orl.co.uk/vnc for information about VNC
>
> 29/06/99 14:44:36 Desktop name 'X' (anduin:)
> 29/06/99 14:44:36 Protocol version supported 3.3
> 29/06/99 14:44:36 Listening for VNC connections on TCP port 5900
> 29/06/99 14:44:36 Listening for HTTP connections on TCP port 5800
> 29/06/99 14:44:36   URL http://anduin:5800
> xrdb: Can't open display 'anduin:'
> xsetroot:  unable to open display 'anduin:'
> Warning: This program is an suid-root program or is being run by the
> root user.
> The full text of the error or warning message cannot be safely formatted
>
> in this environment. You may get a more descriptive message by running
> the
> program as a non-root user or by removing the suid bit on the
> executable.
> xterm Xt error: Can't open display: %s
> twm:  unable to open display "anduin:"
>
>
> An established connection over http port 5800 is possible, but only the
> grey startup screen of X appears and I can't start any other session.
>
> Starting the kde session will be terminated with the message
>
> cannot connect to X Server
>
>
> Does anybody know whats wrong here ?
>
> Christian
>
>
> ---
>
> ---------------------------------------------------------------------
> The VNC mailing list - see http://www.uk.research.att.com/vnc/intouch.html
> ---------------------------------------------------------------------
>


---------------------------------------------------------------------
The VNC mailing list - see http://www.uk.research.att.com/vnc/intouch.html
---------------------------------------------------------------------