vnc Solaris 2.6 CDE (strange error message)

2001-03-31 Thread Tor Bye Andersen

I am currently trying to make VNC work under Solaris 2.6, using CDE. I've
searched the mailing lists for clues,
but haven't found anything directly related to my particular problem.

Having performed
the basic  tasks mentioned in the README file of the installation tar-file, I
start the server
without arguments. (vncserver) on the machine ypch12.
This yields lines on standard out : (omitting the password part)

Nex 'X' desktop is ypch12:1
Starting applications specified in /export/home/tba/7.55/.vnc/xstartup
Log  file is /export/home/tba/7.55/.vnc/ypch12:1.log

So far so good.
But the log file is not so happy :

31/03/01   09:08:21  Xvnc version 3.3.3r2
31/03/01   09:08:21  Copyright (C) AT&T Laboratories Cambridge.
31/03/01   09:08:21  All righs reserved
31/03/01   09:08:21  See http:/www.uk...
31/03/01   09:08:21  Desktop name 'X' (ypch12:1)
31/03/01   09:08:21  Protocol version supported 3.3
31:03:01   09:08:21  Listening for VNC connections on TCP port 5901
31:03:01   09:08:21  Listening for HTTP connections on TCP port 5801
31:03:01   09:08:21  URL http://ypch12:5801
xrdb: No such file or directory
xrdb: can't open display ':1'
xsetroot: unable to open display "1"
xterm Xt error : Can't open display: ":1"
twm: unable to open display ":1"


The funny thing is, I had this part working the first time I tried it out, but
now I'm stuck.
Can it be related to some of my experiments with the vncserver wrapper script
(which is
now the default one) ? I removed all the vnc files, unpacked the tar file
again, and changed the
vncserver script as follows :
 1) perl path changed to /usr/local/bin/perl
2) $vncClasses is changed to /export/home/tba/Macro/classes

And of course, I moved the contents of the classes directory to the
$vncClasses path.

I have disable access control for  both local and remote users (only for this
purpose)
"xhost" yields :

'access control disabled, clients can connect from any host'
INET:localhost
INET:ypch12
LOCAL:

'which xrdb'   yields

/usr/openwin/bin/xrdb
(so the $PATH settings should be OK)

Any help would be greatly appreciated.

regards
Tor Bye Andersen

mailto:[EMAIL PROTECTED]  www.stibo-ds.com
-
To unsubscribe, send a message with the line: unsubscribe vnc-list
to [EMAIL PROTECTED]
See also: http://www.uk.research.att.com/vnc/intouch.html
-



RE: vnc Solaris 2.6 CDE (strange error message)

2001-04-01 Thread Tor Bye Andersen

Thanks a lot. It helped. !
Of course I've run into other problems, but I think 
it's better to post it in a separate thread, after I've
searched the mailing lists for similar problem solutions.

regards
Tor

-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
Sent: 31. marts 2001 17:13
To: [EMAIL PROTECTED]
Cc: [EMAIL PROTECTED]; Tor Andersen
Subject: Re: vnc Solaris 2.6 CDE (strange error message)


   >From: "Tor Bye Andersen" <[EMAIL PROTECTED]>
   >Date: Sat Mar 31 2001  4:49am
   >To:   <[EMAIL PROTECTED]>
   >Cc: "Tor Andersen" <[EMAIL PROTECTED]>
   >Subj: vnc Solaris 2.6 CDE (strange error message)
   >
   >I am currently trying to make VNC work under Solaris 2.6, using CDE. I've
   >searched the mailing lists for clues,
   >but haven't found anything directly related to my particular problem.
   >
   >Having performed
   >the basic  tasks mentioned in the README file of the installation tar-file, I
   >start the server
   >without arguments. (vncserver) on the machine ypch12.
   >This yields lines on standard out : (omitting the password part)
   >
   >Nex 'X' desktop is ypch12:1
   >Starting applications specified in /export/home/tba/7.55/.vnc/xstartup
   >Log  file is /export/home/tba/7.55/.vnc/ypch12:1.log
   >
   >So far so good.
   >But the log file is not so happy :
   >
   >31/03/01   09:08:21  Xvnc version 3.3.3r2
   >31/03/01   09:08:21  Copyright (C) AT&T Laboratories Cambridge.
   >31/03/01   09:08:21  All righs reserved
   >31/03/01   09:08:21  See http:/www.uk...
   >31/03/01   09:08:21  Desktop name 'X' (ypch12:1)
   >31/03/01   09:08:21  Protocol version supported 3.3
   >31:03:01   09:08:21  Listening for VNC connections on TCP port 5901
   >31:03:01   09:08:21  Listening for HTTP connections on TCP port 5801
   >31:03:01   09:08:21  URL http://ypch12:5801
   >xrdb: No such file or directory
   >xrdb: can't open display ':1'
   >xsetroot: unable to open display "1"
   >xterm Xt error : Can't open display: ":1"
   >twm: unable to open display ":1"
   >

===
Known Problems in version 3.3.3R2
There is a known bug with this release, which fortunately has an
easy workaround: Before you start the VNC server you need to insert
these two lines in your startup file ($HOME/.vnc/xstartup), right
after the first line in the file:

DISPLAY=unix${DISPLAY}
export DISPLAY
===

Freddy
-
To unsubscribe, send a message with the line: unsubscribe vnc-list
to [EMAIL PROTECTED]
See also: http://www.uk.research.att.com/vnc/intouch.html
-



Cannot load Xfont helvb12

2001-04-02 Thread Tor Bye Andersen

I am running VNCserver on a solaris box (2.6) using CDE. When I try to launch
an application from a
PC based VNC viewer, I get
the following error :

-cannot load Xfont 

This error message comes from our proprietary application, so it shouldn't be
recognizable
for others.
But it originates from a call to XLoadQueryFont(Xio.DspPtr, "helvb12")

I have tried with various font paths;
{/usr/openwin/lib/X1/fonts/}[F3,F3bitmaps,Type1, Speedo, misc,75dpi, 100dpi]
but to no avail.
I have also tried having a font server running on my solaris box (xfs on port
6100), in which case I
defined my font path in the vncserver wrapper script:
$cmd .= "-fp tcp/localhost:6100";

It seems that no request is being made to the server, because I have
configured it with an error log, which
remains empty, regardless how many times I try to launch the application.

If I launch the same application from a native window on the solaris box, the
font problem vanishes.

Any clues ? Your help will be appreciated.

Tor


Tor Bye Andersen

mailto:[EMAIL PROTECTED]  www.stibo-ds.com
-
To unsubscribe, send a message with the line: unsubscribe vnc-list
to [EMAIL PROTECTED]
See also: http://www.uk.research.att.com/vnc/intouch.html
-