Two VNC problems

[Bog]

Problem #1 :

I installed RealVNC on my Mandrake 9.2 machine. Actually, let me back up and say that this is the first thing I've ever installed, so I don't entirely know if I was doing it right:

I unrared/untared, then followed the instruction in the README, which required me to su to root in order to do.

Anyway, I ran vncviewer and that worked fine if I'm root, but when I run it as user, I get:

vncviewer: error while loading shared libraries: libstdc++-libc6.1-1.so.2: cannot open shared object file: No such file or directory

I tried chmodding it to 777 (as root) and then trying again but no good.

-----------------------------------------
Problem #2:

If I run vncserver, I am unable to login from my windows machine. The windows VNC client simply says "Failed to connect". I tried explicitly specifying the :number, no good either. I AM able to do the reverse- to login FROM the linux machine (running vncviewer as root) TO the windows machine. (They are both connected to the same router.)

-------------------------------------------
Bonus Problem:

When I run vncviewer as root, and login to my windows box, the scroll bars of the RightVNC window are malfunctioning. They are stark black and whit and do wierd unpredictable stuff when clicked on.

tia

[pmrphs2002]

TightVNC is available as a package on your install CDs

[Bog]

Yes I know, thanks. I want to know how to install and use VNC (or any app for that matter), myself. The main reason I installed linux is to learn it.

[o0zi]

Solution to problem #1:

If vncviewer can't find libstdc++-libc6.1-1.so.2, that means it's probably looking in the wrong place. libstdc++ is one of the most common libraries, and Mandrake will certainly have it. Try looking for libstdc++-libc6-something, and symlink it to the file that vncviewer can't find. For instance, if you had libstdc++-libc6.1-2.so.2, you'd type:

ln -s libstdc++-libc6.1-2.so.2 libstdc++-libc6.1-1.so.2

However, this does seem a bit odd - did you compile vncviewer yourself?

Solution to problem #2:
Perhaps you're starting vncserver wrong - check the manpage (man vncserver) on how to do it.

[hlrguy]

Problem #2

Is you firewall blocking connection from that machine, or more specifically, ports 5900, 5901, etc?

After starting the server, check the log file, cause any errors will be present there.

hlrguy

[Bog]

Regarding problem #1, here's some more info:

As myself, I tried "which vncviewer" I got:

/usr/local/bin/vncviewer

I sued to be root and tried "which vncviewer", I got:

/usr/X11R6/bin/vncviewer

I think this is because mandrake comes with its own vncviewer (I did NOT install the VNC package when I installed mandrake- I think it only gave me the client). The one I installed is the one in usr/local/bin. So the reason it was working as root is because it was the wrong app.

Also, I cd'ed to /usr/local/bin and the only thing in it is the vnc stuff I installed:

bog@localhost bin]$ pwd
/usr/local/bin
[bog@localhost bin]$ ls
vncconnect* vncpasswd* vncserver* vncviewer* Xvnc*
[bog@localhost bin]$

Is that normal? Is /usr/local/bin supposed to be empty when linux is installed? Or is Mandrake totally on crack and I should use a different distrib?

Also how do I make it so that, as root, "which vncserver" will return the /usr/local/bin one?

[mdwatts]

Originally posted by Bog

Is that normal? Is /usr/local/bin supposed to be empty when linux is installed? Or is Mandrake totally on crack and I should use a different distrib?

Also how do I make it so that, as root, "which vncserver" will return the /usr/local/bin one?

'/usr/local/bin' is usually empty until you start installing personal apps unless you specify a prefix when compiling.

i.e.

./configure --prefix=/usr

Which will then install the app in /usr/bin instead of /usr/local/bin.

You will need to change your PATH variable. Check in /etc/profile and put '/usr/local/bin' ahead of the others.

Easiest way to do is add

export PATH=/usr/local/bin:$PATH

at the end of /etc/profile

[Bog]

Originally posted by o0zi
Solution to problem #1:

If vncviewer can't find libstdc++-libc6.1-1.so.2, that means it's probably looking in the wrong place. libstdc++ is one of the most common libraries, and Mandrake will certainly have it. Try looking for libstdc++-libc6-something, and symlink it to the file that vncviewer can't find. For instance, if you had libstdc++-libc6.1-2.so.2, you'd type:

ln -s libstdc++-libc6.1-2.so.2 libstdc++-libc6.1-1.so.2

However, this does seem a bit odd - did you compile vncviewer yourself?


Nope, I didn't, I downloaded binaries from realvnc.com and followed the instructions in the readme:

"You should copy the programs to some directory which is in your PATH
environment variable, such as /usr/local/bin. You can use the vncinstall
script to do this for you:
% ./vncinstall /usr/local/bin"

About the libc6 problem, I searched for the libc6 and found it. Here's how far I got:

[bog@localhost lib]$ pwd
/sda3/lib
[bog@localhost lib]$ ls -l libstdc++-libc6.1-1.so.2
lrwxrwxrwx 1 root root 30 Jan 13 2000 libstdc++-libc6.1-1.so.2 -> libstdc++-2-libc6.1-1-2.9.0.so*
[bog@localhost lib]$

It looks like there's already a symlink for it... (er is that what that's saying?) so I didn't try to create another one.

(Also fyi this is a fresh mandrake 9.2 install, installed on monday, and I haven't installed or removed anything else.)

[Bog]

Originally posted by hlrguy
Problem #2

After starting the server, check the log file, cause any errors will be present there.

hlrguy

I took your advice, and it looks like vncserver has the same problem finding libc6 that vncviewer has. Here is me trying and then looking at the log files:

[bog@localhost .vnc]$ vncserver

New 'X' desktop is localhost:1

Starting applications specified in /home/bog/.vnc/xstartup
Log file is /home/bog/.vnc/localhost:1.log

[bog@localhost .vnc]$ more localhost\:1.log
Xvnc: error while loading shared libraries: libstdc++-libc6.1-1.so.2: cannot
open shared object file: No such file or directory
[bog@localhost .vnc]$ vncviewer
vncviewer: error while loading shared libraries: libstdc++-libc6.1-1.so.2: cannot open shared object file: No such file or directory
[bog@localhost .vnc]$ more localhost\:1.log
Xvnc: error while loading shared libraries: libstdc++-libc6.1-1.so.2: cannot
open shared object file: No such file or directory
xsetroot: unable to open display 'localhost:1'
/home/bog/.vnc/xstartup: line 5: xterm: command not found
twm: unable to open display "localhost:1"
[bog@localhost .vnc]$

[mdwatts]

Originally posted by Bog

Xvnc: error while loading shared libraries: libstdc++-libc6.1-1.so.2: cannot
open shared object file: No such file or directory
[bog@localhost .vnc]$ vncviewer
vncviewer: error while loading shared libraries: libstdc++-libc6.1-1.so.2: cannot open shared object file: No such file or directory
[bog@localhost .vnc]$ more localhost\:1.log
Xvnc: error while loading shared libraries: libstdc++-libc6.1-1.so.2: cannot
open shared object file: No such file or directory


Either those libraries are not installed or they are not the correct version VNC is expecting.

If they are installed and the required version, ensure the path to those libraries are in '/etc/ld.so.conf'. Add the path if necessary and run 'ldconfig' (as root).

Doing a 'locate libstdc++', I find I have

/usr/lib/libstdc++-3-libc6.1-2-2.10.0.so
/usr/lib/libstdc++-3-libc6.2-2-2.10.0.so
/usr/lib/libstdc++-libc6.1-1.so.2
/usr/lib/libstdc++-libc6.1-2.so.3
/usr/lib/libstdc++-libc6.2-2.so.3
/usr/lib/libstdc++.a
/usr/lib/libstdc++.la
/usr/lib/libstdc++.so
/usr/lib/libstdc++.so.2.7.2
/usr/lib/libstdc++.so.2.7.2.8
/usr/lib/libstdc++.so.2.8
/usr/lib/libstdc++.so.2.8.0
/usr/lib/libstdc++.so.2.9
/usr/lib/libstdc++.so.2.9.0
/usr/lib/libstdc++.so.5
/usr/lib/libstdc++.so.5.0.5

Why not just install the VNC packages included on your distros cd's as they should work with the libraries and versions you have installed.

[mdwatts]

See if the post by Choozo in this thread (http://justlinux.com/forum/showthread.php?s=&threadid=119007) pertains to your library problem.

[Bog]

Originally posted by mdwatts
See if the post by Choozo in this thread (http://justlinux.com/forum/showthread.php?s=&threadid=119007) pertains to your library problem.

That did it. Wierd too, because .3 isn't what vnc was looking for, it was looking for .2. Maybe the rpm did other stuff that fixed. Now I have a new problem with VNC, the Gray Screen of Emptiness, for which I will make a new post.

thanks