HI,
I try to start the vnc-E-4-1-6 server but I get the following error:
svrvnc: /apps/vnc/vnc-ed4.1.6/vncserver
VNC Server Enterprise Edition 4.1.6 - built Mar 31 2005 17:35:58
Copyright (C) 2002-2005 RealVNC Ltd.
See http://www.realvnc.com for information on VNC.
sh: vnckeygen: not found
Error:
Hello All,
I!/m using HP-UX10.20 like below:
# uname -r
B.10.20
I!/m a beginner on HP unix. I!/ve installed vnc only on solaris.
So, I have met many problem with installing vnc on this HP-UX10.20.
When I!/ve first trying, font-path error occurred. So I!/ve modified xfs
config like follo
Wesley,
The first thing to try would be upgrading to VNC 4.1.1 on the Solaris
system.
Regards,
Wez @ RealVNC Ltd.
> -Original Message-
> From: [EMAIL PROTECTED]
> [mailto:[EMAIL PROTECTED] On Behalf Of wesleyz
> Sent: 27 June 2005 04:30
> To: vnc-list@realvnc.com
> Subject: inconsist
Use dtterm's copy function (ctrl+insert). Alternatively upgrade to
4.1.1 - vncconfig now has an option to continually poll the selections
in order to cope with broken applications like dtterm. For example
"vncconfig -poll 1000" will poll every second, which should be frequent
enough for most
The clipboard implementation in the Windows vncviewer does not handle
non-ascii characters. This is true for the 4.0 and 4.1.1 version. This is
because non-ascii chars are explicitly removed. Why? The patch below
restores the vncviewer3 behaviour and solves our problem (cut and paste
with Swedi
JooHwan,
If you are able to connect to the VNC server using both the native VNC
Viewer and the Java VNC Viewer, what makes you think that the server is
dumping core?
Which version of VNC are you using?
Regards,
Wez @ RealVNC Ltd.
> ./vncserver -geometry 1024x7680 -depth 16 -fp tcp/127.0.0.1:7
Ferindo,
The fact that the viewer is showing the desktop window but is then closing
suggests that you are able to connect to the server, but that the server is
then closing the connection again, so you may want to look at the server's
log (in your .vnc directory) to see why it is doing so.
Are yo
Hello Wez,
I'm using vnc ver. 3.3.7.
And, I don't know when vnc produce core.
But, I know only font issue has been cleared.
What can I check for this issue?
Best Regards,
JooHwan Kim
-Original Message-
From: James Weatherall [mailto:[EMAIL PROTECTED]
Sent: Monday, June 27, 2005 8:26 P
Peter,
VNC 4.1.1 has no such function as removeNonAsciiChars(), replacing it
instead with removeNonISOLatin1Chars(), specifically in order to support
accented characters. The problem you are seeing is a known bug in VNC
4.1.1, caused by comparing a signed char with ISO-8859-1 character values,
wh
Running 'vncpasswd foo' and entering a password that's, say, 12
characters long results in a buffer overflow. It is caught by glibc:
*** glibc detected *** vncpasswd: free(): invalid next size (fast): 0x09292110
***
=== Backtrace: =
/lib/libc.so.6[0x49c384]
/lib/libc.so.6(__libc_free
I recently downloaded Real VNC. I am currently trying to figure out
how to connect to my computer from outside my network. I have enabled
port forwarding from 5802 to computers ip:5800. When I go to computers
ip:5802 I go to the client download page. Then a box comes up asking
for a server. It fill
When you use the java viewer in the free eddition of vnc you need to forward
two ports.
Port 5800 (default java) only serves the applet itself, you still need port
5900 (default) forwarded so that vnc traffic can travel across it.
--ANgelo
On 6/27/05, Brennan Ujcich <[EMAIL PROTECTED]> wrote:
>
>
I've spent a considerable amount of time tracking down the
incompatibilities between dtlogin on Sparc Solaris and Xvnc 4.x (dtlogin
is the CDE version of XDM which is used to provide the Solaris login
screen when you use the -query option to Xvnc).
There are a number of issues, the most signif
Brennan Ujcich wrote:
> I recently downloaded Real VNC. I am currently trying to figure out
> how to connect to my computer from outside my network. I have enabled port
> forwarding from 5802 to computers ip:5800. When I go to computers ip:5802
> I go to the client download page. Then a box comes u
Thanks for the information, Tristan.
I added the "-nolisten named" parm to my entry in inetd.conf for my
Solaris 8 (sparc) systems and now VNC works fine for my Solaris 8
machines.
This is the entry in my inetd.conf
"vnc5901 stream tcp nowait root /usr/sbin/tcpd /usr/local/bin/Xvnc
-inetd -que
when I attempt to connect with
VNC, I never connect. However, I never get a failure notice either
___
VNC-List mailing list
VNC-List@realvnc.com
To remove yourself from the list visit:
http://www.realvnc.com/mailman
Tristan,
Thanks for the solution! The addition of the "-nolisten named" option
fixes Xvnc 4.1.1 and now dtlogin launches as it should, even on my
Solaris 2.6 systems. I have been using a font server so that issue I
already addressed.
Tom
Tristan Richardson wrote:
I've spent a considerable
I use the VNC Server & client that came packaged with Fedora when I'm on
the server but I use version 4.1.1 on my Windows 2000 machine running
remotely on my LAN... both them act the same way way connecting to the
server. Locally in the .vnc folder of the user on the server, the most
recent log
Hi
Nobody seemed to notice the earlier email and/or help.
But anyways for others who may notice such a problem in future, the
cause I figured out for the core dump was due to the screensaver.
Setting kde's option to "no screensaver" doesn't dump core and crash the
session.
Didn't delve deeper into
Part of the .vnc localhost:2.log logfile below says:
error opening security policy file
/usr/X11R6/lib/X11/xserver/SecurityPolicy
Could not init font path element /usr/X11R6/lib/X11/fonts/CID/, removing
from list!
I'm not sure why this xserver/SecurityPolicy file was removed or can no
longer
20 matches
Mail list logo