Re: [CentOS] Missing fonts for tightvnc
On Mon, Aug 18, 2008 at 6:37 PM, Filipe Brandenburger <[EMAIL PROTECTED]> wrote: > Hi, > > On Mon, Aug 18, 2008 at 16:42, Robert Moskowitz <[EMAIL PROTECTED]> wrote: >> vncserver: The USER environment variable is not set. > > So, is it set or not? > > It's usually set by /etc/profile, so if it's not set, that might > indicate you have an issue with your setup. > Indeed, looking at my /etc/profile I see the following: if [ -x /usr/bin/id ]; then USER="`id -un`" LOGNAME=$USER MAIL="/var/spool/mail/$USER" fi Is there anything else needed to help Robert debug this? I have this working on CentOS 5.2 and "Xvnc -version" shows: Xvnc version TightVNC-1.3.9 ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] vncserver on IPv6
On Tue, Aug 12, 2008 at 10:57 AM, Robert Moskowitz <[EMAIL PROTECTED]> wrote: > > > Rob Lockhart wrote: >> >>In /etc/sysconfig/vncservers I have something like this: >> >>VNCSERVERS="1:myusername" >>VNCSERVERARGS[1]="-geometry 1400x1050 -depth 16 -localhost" >> >>(so I can only use localhost, which means I only allow >>connections over ssh or from the local machine). >> >>Yours might be something like this: >> >>VNCSERVERS="1:robert" >>VNCSERVERARGS[1]="-geometry 1400x1050 -depth 16 >>InTransports=IPv6,IPv4" >> >> >>Well first my line has [2]. I changed that to [1] and tried all >>sorts of variants to the above, including putting a - infront of >>InTransports (like other options), and replacing the = with a >>space. No listening on IPv6. >> >>I have foudn the RealVNC support mailing list and sent a question >>there, hopefully to get answers. But if anyone has anything to >>suggest here, please do. >> >> I recently reinstalled VNC - actually "TightVNC" as it's better than VNC >> for bandwidth. If you type "Xvnc -h" you'll see all the parameters >> supported. I didn't see any options for IPv6 in my version. But yours >> might indeed have more options. > > Using this method, I don't either, though the help is -help, not -h, but > there is -multicast for IPv6 multicast for XDMCP >> >> I noticed that the default /etc/init.d/vncserver script seemed to be >> ignoring my parameters for VNCSERVERARGS as in the log file, it showed >> listening for all hosts (not just local hosts). This was confirmed by >> connecting directly from another machine to the VNC server port (:1 which is >> port 5901). I had an older version of the vncserver script, and I overwrote >> the one from the repository with that one, and it took my parameters. >> However, the parameters I can confirm are working are: "-nolisten tcp >> -localhost -desktop RobHome -geometry 1280x1024". >> >> First, verify via "Xvnc -h" that the parmeters for IPv6 are supported >> (InTransports). > > BTW, I note in the -help messages that parameters are case insensitive. Or > that is the claim. >> >> Next, could it be possible the ip6tables is blocking you? My network >> doesn't use IPv6 so I don't think I could retrace your steps. > > No. Port 5902 is specifically accepted in both iptables and ip6tables. And > I have tested this using another app that I have bound to that port (but is > not running when I try out vncserver). > > And no answer on the vnc support list Going to google, "tightvnc IPv6": http://www.tightvnc.com/related.html which then points (at the bottom): http://jungla.dit.upm.es/~acosta/paginas/vncIPv6.html so it looks someone has compiled TightVNC with IPv6 support. Try the new font fix, and see if it works -Rob ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Missing fonts for tightvnc
On Wed, Aug 13, 2008 at 12:14 PM, Toby Bluhm <[EMAIL PROTECTED]> wrote: > Robert Moskowitz wrote: >> >> Toby Bluhm wrote: >>> >>> Robert Moskowitz wrote: You would think installing via yum would handle dependencies, but perhaps fonts are not managed like dependencies. Anyway, I installed tightvnc to test out its IPv6 support. Installed ok (after I erased regular vnc). But when I tried to start it, I got 5 warnings about: Font directory '/usr/X11R6/lib/X11/fonts/misc' not found - ignoring (then the same message for Speedo, Type1, 75dpi, and 100dpi). Then a fatel server error about: could not open default fount 'fixed' So I looked in the repos (curtesy of yumex) and did find a few 75dpi a 100dpi fonts, but there seemed to be a lot of these two. I installed a ocuple of them and tried again. Got the same errors. So how do I fix this one? >> >> But I stopped both iptables and ip6tables and the same error messages. >> >> And installing OpenOffice did not 'fix' things. Perhaps setting symlinks >> may be needed. >> >> > > I remember playing games with Matlab to get it to find it's own fonts. I > think it went something like: > > mkdir > cp fonts* > mkfontdir > Add to /etc/X11/fs/config > > Like you say, maybe just a link to /usr/share/X11/fonts/misc would do the > trick. > > Perhaps a vnc/X startup script somewhere is hardcoded? Robert, I noticed the same thing, so what I did is the following: cd /usr/X11R6/; mkdir lib; cd lib; ln -s /usr/share/X11 . Now try it. Seems like the repository from which I got TightVNC has issues in directory compatibility but at least I got it working. I didn't have a misc fonts directory, and my $HOME/.vnc/xtartup has: #!/bin/sh # Red Hat Linux VNC session startup script exec /etc/X11/xinit/xinitrc If that still doesn't work, I'll post the /etc/init.d/vncserver script that works for me (possibly from an older install of tightvnc - 1.2.9 I believe). If there's a more elegant solution, someone please let us know! :-) -Rob ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] vncserver on IPv6
On Mon, Aug 11, 2008 at 12:01 PM, Robert Moskowitz <[EMAIL PROTECTED]>wrote: > > On Fri, Aug 8, 2008 at 3:55 PM, Robert Moskowitz <[EMAIL PROTECTED]> [EMAIL PROTECTED]>> wrote: >> >>http://www.realvnc.com/products/enterprise/4.1/ipv6.html >> >> >> IPv6 support in VNC Server E4.1.7/P4.1.2 >> >>VNC Server E4.1.7 & P4.1.2 are fully IPv6-aware, but is shipped >>with IPv6 support disabled by default, for security reasons. IPv6 >>can be enabled by setting "InTransports=IPv6,IPv4" (the default >>being IPv4 only), either on the command-line when starting >>vncserver under Unix >> >>Ok. we have vnc-server-4.1.2-9.el5.i386.rpm, so it SHOULD support >>IPv6. >> >>Don't know how to add a setting to the command-line, as I rund >>VNCserver via the service command, but I added it to >>/etc/sysconfig/vncservers: >> >>InTransports="IPv6" (note I also tried without the quotes) >> >>and netstat -na|grep 5902 >> >>shows vncserver only running on IPv4 and I can only connect to it >>via IPv4. >> >>So what am I missing? >> >> > Rob Lockhart wrote: > > In /etc/sysconfig/vncservers I have something like this: >> >> VNCSERVERS="1:myusername" >> VNCSERVERARGS[1]="-geometry 1400x1050 -depth 16 -localhost" >> >> (so I can only use localhost, which means I only allow connections over >> ssh or from the local machine). >> >> Yours might be something like this: >> >> VNCSERVERS="1:robert" >> VNCSERVERARGS[1]="-geometry 1400x1050 -depth 16 InTransports=IPv6,IPv4" >> >> > Well first my line has [2]. I changed that to [1] and tried all sorts of > variants to the above, including putting a - infront of InTransports (like > other options), and replacing the = with a space. No listening on IPv6. > > I have foudn the RealVNC support mailing list and sent a question there, > hopefully to get answers. But if anyone has anything to suggest here, > please do. > > > Robert, I recently reinstalled VNC - actually "TightVNC" as it's better than VNC for bandwidth. If you type "Xvnc -h" you'll see all the parameters supported. I didn't see any options for IPv6 in my version. But yours might indeed have more options. I noticed that the default /etc/init.d/vncserver script seemed to be ignoring my parameters for VNCSERVERARGS as in the log file, it showed listening for all hosts (not just local hosts). This was confirmed by connecting directly from another machine to the VNC server port (:1 which is port 5901). I had an older version of the vncserver script, and I overwrote the one from the repository with that one, and it took my parameters. However, the parameters I can confirm are working are: "-nolisten tcp -localhost -desktop RobHome -geometry 1280x1024". First, verify via "Xvnc -h" that the parmeters for IPv6 are supported (InTransports). Next, could it be possible the ip6tables is blocking you? My network doesn't use IPv6 so I don't think I could retrace your steps. Indeed, you are right in that I had omitted a "-" in my email, but didn't want to waste list bandwidth in sending out the obvious typo. Regards, -Rob ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] vncserver on IPv6
In /etc/sysconfig/vncservers I have something like this: VNCSERVERS="1:myusername" VNCSERVERARGS[1]="-geometry 1400x1050 -depth 16 -localhost" (so I can only use localhost, which means I only allow connections over ssh or from the local machine). Yours might be something like this: VNCSERVERS="1:robert" VNCSERVERARGS[1]="-geometry 1400x1050 -depth 16 InTransports=IPv6,IPv4" then obviously as root: service vncserver restart Have you tried that? Does VNC work over IPv4? On Fri, Aug 8, 2008 at 3:55 PM, Robert Moskowitz <[EMAIL PROTECTED]>wrote: > http://www.realvnc.com/products/enterprise/4.1/ipv6.html > > > IPv6 support in VNC Server E4.1.7/P4.1.2 > > VNC Server E4.1.7 & P4.1.2 are fully IPv6-aware, but is shipped with IPv6 > support disabled by default, for security reasons. IPv6 can be enabled by > setting "InTransports=IPv6,IPv4" (the default being IPv4 only), either on > the command-line when starting vncserver under Unix > > Ok. we have vnc-server-4.1.2-9.el5.i386.rpm, so it SHOULD support IPv6. > > Don't know how to add a setting to the command-line, as I rund VNCserver > via the service command, but I added it to /etc/sysconfig/vncservers: > > InTransports="IPv6" (note I also tried without the quotes) > > and netstat -na|grep 5902 > > shows vncserver only running on IPv4 and I can only connect to it via IPv4. > > So what am I missing? > > ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
Re: [CentOS] Reg. VNC server and Windows and Centos interworking
Reply bottom-posted: On Mon, Feb 25, 2008 at 12:52 AM, Padmaja <[EMAIL PROTECTED]> wrote: > Hi, > > Thanks for your response, I could connenct to the Centos PC from Windows > using VNC. However, I do not see the icons etc., that I see when I access > any windows PC. I ran the command ps aux and saw there is a vnc process > running for iconic view, but 'm not able to view the icons on the desktop. > What should I do to get access to the GUI? > > Thanks for your help, > Padmaja > > - Original Message - > From: "Les Mikesell" <[EMAIL PROTECTED]> > To: "CentOS mailing list" > Sent: Monday, February 25, 2008 5:23 AM > Subject: Re: [CentOS] Reg. VNC server and Windows and Centos interworking > > > > Padmaja wrote: > >> Hi, > >> > >> Thanks for such a fast response. I typed vncserver at the command line > >> and it asked me for a password. It said I would require password to > enter > >> the desktop. I did not set any before so gave some dummy password. It > >> again showed Verify and I typed the same password again. Then the > screen > >> showed something like > >> > >> for user padmaja, the startup script is in /home/padmaja/.vnc/Xstartup > >> the startup applications are in /home/padmaja/.vnc/Xstartup > >> the log file is in /home/padmaja/.vnc/sipserver.com.log > >> > >> After this I typed ps aux and saw that there is a Xvnc running againt > pid > >> 11435. > >> > >> Now, I tried to connect to the Centos PC from Windows using Vnc client > >> and it gave the error > >> > >> "unable to connect to host: connection refused (10061)." > >> > >> I cant understand what the issue is. I am however able to connect to > >> Windows PCs from VNC on windows. > > > > > > Vncserver creates separate desktops for each instance and should have > > given you a 'screen number" when you started it - probably :1 for the > > first one. Then you have to specify the matching screen when you > connect > > from the client: hostname:1. If you have the firewall running on > Centos, > > you have to permit the appropriate port in ( 5900 + screen number). If > > you are expecting to access the desktop running on the console you need > a > > different approach. KDE and Gnome have 'screen sharing' options for the > > running desktop. > You need some sort of xstartup, I believe. I run VNC at home and it works great, once it's set up correctly. Not sure if this will work, it was the first google hit (and it looks like it's set up for RHEL4): http://www.skullbox.net/vncserver.php I use Gnome since it's the default. ___ CentOS mailing list CentOS@centos.org http://lists.centos.org/mailman/listinfo/centos
