Hi,
I have VNC working with Solaris 7 and CDE and have attached the xstartup script from 
~/.vnc and the Xvnc startup script called vncserver.
Take a look at the lines after the comment:-
#Add font path and color database stuff here


Hope this helps.

Cheers
Richard.

-----Original Message-----
From: David Saez Padros [mailto:[EMAIL PROTECTED]]
Sent: 17 January 2001 08:30
To: [EMAIL PROTECTED]
Subject: Re: Solaris 8 CDE


Hi !!

> The vnc startup script I've got working (Solaris 2.6) is as follows:
>
> #!/bin/sh
>
> xrdb $HOME/.Xresources
> xsetroot -solid black
> xterm -geometry 80x24+10+10 -ls -title "$VNCDESKTOP Desktop" &
> /usr/dt/bin/Xsession &
>
> xsetroot was a workaround for the fact that the X desktop always came up
> with an awful grey colour that wouldn't sync right on my PC's monitor.
>
> (1) Do you have the xrdb setting in there? (don't know what it does!)

mmm ... I'm logging as root and /.Xresources does not exist, altough I'm able
to
log phisically on the machine as root without any problem. I tried to xrdb
/usr/dt/config/es/Xresources but it does not make any difference.

> (2) has the user run X 'natively' to the graphical terminal before (logged
> in, used the desktop etc)

Yes, a lot of times.

> (3) do they have the following directory (not $HOME/.xt as I previously
> suggested)
>
> $HOME/.dt

Yes.

> (4) are the X directories were in the users path (check against a user that
> works OK to the graphics terminal on the host) That might explain why you
> can't find key files. I found running X 'natively' set the users up
> correctly, I then give them an Xvnc session.

PATH is fine.

> (5) Once the VNC session is running without a window manager, run a window
> manager direct from the xterm that's in VNC session - full path name etc (I
> suggest dtwm, I know it works) I've had to kill my window manager on
> occasion, and restart it, and it recovers flawlessly.

I just check if dtwm was running, but it's not running. I have this on
/.dt/startlog

--- martes, 16 de enero de 2001, 16:09:10 CET
--- /usr/dt/bin/Xsession starting...
--- Xsession started by
--- setting font path...
--- starting /usr/dt/bin/dtsession_res -load -system
--- sourcing //.dtprofile...
--- sourcing /usr/dt/config/Xsession.d/0010.dtpaths...
--- sourcing /usr/dt/config/Xsession.d/0015.sun.env...
--- sourcing /usr/dt/config/Xsession.d/0020.dtims...
--- sourcing /usr/dt/config/Xsession.d/0030.dttmpdir...
--- sourcing /usr/dt/config/Xsession.d/0040.xmbind...
--- sourcing /usr/dt/config/Xsession.d/1000.solregis...
--- could not read //.profile
--- starting /usr/dt/bin/dthello &
--- starting /usr/dt/bin/dtsearchpath
/usr/dt/bin/dthello: display unix:1.0 doesn't know font -dt-interface
system-medium-r-normal-l*-*-*-*-*-*-*-*-*
"/usr/dt/bin/dthello: display unix:1.0 doesn't know font fixed
"--- starting /usr/dt/bin/dtappgather &
--- starting /usr/dt/bin/dsdm &
--- session log file is /dev/null
--- DTSOURCEPROFILE is 'true' (see //.dtprofile)
--- execing /usr/dt/bin/dtsession with a /sbin/sh login shell ...
--- starting desktop on /dev/pts/4
Sun Microsystems Inc.   SunOS 5.8       Generic February 2000
/usr/dt/bin/ttsession[14086]: iniciando
X connection to unix:1.0 broken (explicit kill or server shutdown).
/usr/dt/bin/Xsession[749]: 14073 Sistema colgado

It seems that dthello refuses to start and thus dtwm is also not started.
I also tried to start it following instructions provided by Maeda Atusi:

> Solaris Xsession script cheks whether it is invoked by a dtlogin command.
> If not, Xsession initializes font paths and key codes (to *wrong* values,
> at leaset in my environment).
>
> An easy way to prevent this is to make a shell script with name
> `dtlogin' and invoke Xsession from the script after setting font paths.
>
> for i in `locate fonts.alias | grep /ja/`; do xset fp+ `dirname $i`; done
>
> In your own dtlogin:
>
> #!/bin/sh
> for i in <spanish-font-dirs>; do xset fp+ $i; done
> LANG=es DTXSERVERLOCATION=remote /usr/dt/bin/Xsession
>
> In your ~/.vnc/xstartup
>
> #!/bin/sh
> exec <somewhere>/dtlogin

If I do that I get 4 errors from Xsession like this ones:

/usr/openwin/bin/xset:  bad font path element (#37), possible causes are:
    Directory does not exist or has wrong permissions
    Directory missing fonts.dir
    Incorrect font server address or syntax

If I change DTXSERVERLOCATION to local then

--- miircoles, 17 de enero de 2001, 09:15:09 CET
--- /usr/dt/bin/Xsession starting...
--- Xsession started by init
--- setting font path...
--- starting /usr/dt/bin/dtsession_res -load -system
--- sourcing //.dtprofile...
--- sourcing /usr/dt/config/Xsession.d/0010.dtpaths...
--- sourcing /usr/dt/config/Xsession.d/0015.sun.env...
--- sourcing /usr/dt/config/Xsession.d/0020.dtims...
--- sourcing /usr/dt/config/Xsession.d/0030.dttmpdir...
--- sourcing /usr/dt/config/Xsession.d/0040.xmbind...
--- sourcing /usr/dt/config/Xsession.d/1000.solregis...
--- could not read //.profile
--- starting /usr/dt/bin/dthello &
--- starting /usr/dt/bin/dtsearchpath
/usr/dt/bin/dthello: display unix:1.0 doesn't know font -dt-interface
system-med
ium-r-normal-l*-*-*-*-*-*-*-*-*
"/usr/dt/bin/dthello: display unix:1.0 doesn't know font fixed
"--- starting /usr/dt/bin/dtappgather &
--- starting /usr/dt/bin/dsdm &
--- session log file is /dev/null
--- DTSOURCEPROFILE is 'true' (see //.dtprofile)
--- execing /usr/dt/bin/dtsession with a /sbin/sh login shell ...
--- starting desktop on /dev/pts/4
Sun Microsystems Inc.   SunOS 5.8       Generic February 2000
/usr/dt/bin/ttsession[20116]: iniciando

But every try to lauch a dt* application dumps core (the same way as if
DTXSERVERLOCATION=remote)

> Finally, errors like the following happen every time I send X programs on
> other unix servers to my VNC session.
>
> >Warning: Missing charsets in String to FontSet conversion
> >Warning: Cannot convert string "-dt-interface
> >system-medium-r-normal-l*-*-*-*-*-*-*-*-*" to type FontSet
> >Warning: Missing charsets in String to FontSet conversion
>
> It would make perfect sense that the window manager would generate them as
> well.

If I just start without twm and then start dtwm it doees nothing, maybe the
problem seems to be that dtwm does not find the fonts that it requires for
some reason (-dt-interface-***). I aslo tried to xset all font paths that
contains -dt-interface fonts is /usr/openwin/lib/locale/*/fonts/* but does
not make any difference.

--
Thanx & best regards ....

----------------------------------------------------------------
     David Saez Padros                  e-mail  [EMAIL PROTECTED]
     On-Line Services 2000 S.L.
     Trafalgar 78 2: 2* B               voice   +34 93 315 15 93
     08010 Barcelona (Spain)            movil   +34 670 35 27 53
     http://www.ols.es                  fax     +34 93 268 35 90
     http://www.ols.es/~david/
----------------------------------------------------------------
---------------------------------------------------------------------
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
---------------------------------------------------------------------

[demime 0.97b removed an attachment of type application/octet-stream which had a name 
of xstartup]

[demime 0.97b removed an attachment of type application/octet-stream which had a name 
of vncserver]
---------------------------------------------------------------------
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
---------------------------------------------------------------------

Reply via email to