Alasdair, I have followed this thread with interest since I work with Solaris machines and use VNC AND have the same problem with Solaris 8 (sparc) both with 4.1 and 4.1.1 versions of VNC. I have both Solaris 8 and Solaris 9 setup with inetd and the VNC connections work just fine on Solaris 9 but not on Solaris 8.
Some of the messages you have seen in /var/dt/Xerrors about fontpath errors occur because in the xsetup script (/usr/dt/config/Xsetup) an attempt is made to append non-existent fonts to the font path. If you look at Xsetup you can see what is going on but this is not the cause of the problem. After running both Solaris 8 and Solaris 9 dtlogin in debug mode I was no closer to the answer. This is a comparison of the two modules: -r-xr-xr-x 1 root bin 181532 Feb 17 07:45 dtlogin (sol8) -r-xr-xr-x 1 root bin 185396 Feb 17 13:36 dtlogin (sol9) Notice that the dtlogin module from Solaris 9 media is about 4K larger. I backed up the Solaris 8 version of dtlogin and then used the dtlogin from Solaris 9 on my Solaris 8 system. Both versions of dtlogin had all outstanding patches applied. Now when connecting via VNC on Solaris 8, I could successfully login to a CDE, OpenWindows or Failsafe Session. For some reason the extra code in the Solaris 9 dtlogin module will handle whatever is occurring and causing the Solaris 8 module to terminate. I realize that this is a workaround and not an answer. You may not have access to Solaris 9 or may not feel comfortable implementing a work-around such as this. I thought I would post my observations since they may help someone else with finding out what the real problem is. _______________________________________________ VNC-List mailing list [email protected] To remove yourself from the list visit: http://www.realvnc.com/mailman/listinfo/vnc-list
