Hello everyone,

I'm have a couple of issues with Realvnc 3.3.4 that I'm hoping someone here
can provide me with a little help.

The test platform is: REALvnc 3.3.4, 100% OpenLinux 3.1.1, KDE 3.0.3, XFree
4.2.99.

I have two un-resolvable issues.

First, using -fullscreen on the vncviewer command line causes the client to fail
to load. Executing "vncviewer -fullscreen spyro:2" causes a new window to open,
then promptly close. Please see "CONSOLE MESSAGE" and "VNCLOG"  at the end of
this message for relevant console and vnc log failure messages.

Second, from KDE 3.0.3 I am unable to construct a desktop object that would
provide a one-click startup of a vncviewer. I very carefully enter the follow
command into the execute property of the object, but it fails to start a
client;"/usr/bin/vncviewer -passwd ~/.vnc/passwd spyro:2".  However, keying in
the same command line into a konsole will work correctly. The ONLY complaint I
can find about this is in ~/.xsessions-errors... it contains:

---XSESSION-ERRORS---
VNC viewer version 3.3.4 - built Sep 20 2002 15:18:28
Copyright (C) 2002 RealVNC Ltd.
Copyright (C) 1994-2000 AT&T Laboratories Cambridge.
See http://www.realvnc.com for information on VNC.
VNC server supports protocol version 3.3 (viewer 3.3)
Cannot read valid password from file "~/.vnc/passwd"
---END XSESSION-ERRORS---

The password file is there and is obviously read ok when vncviewer is called
from the konsole... But not from a KDE desktop object. Obviously I'm missing
something in the object construction, but it has been eluding me...

The next two rather long log clips relate to my first problem...

----CONSOLE MESSAGE--- 
VNC viewer version 3.3.4 - built Sep 20 2002 15:18:28
Copyright (C) 2002 RealVNC Ltd.
Copyright (C) 1994-2000 AT&T Laboratories Cambridge.
See http://www.realvnc.com for information on VNC.
VNC server supports protocol version 3.3 (viewer 3.3)
VNC authentication succeeded
Desktop name "root's X desktop (spyro.my.domain:2)"
Connected to VNC server, using protocol version 3.3
VNC server default format:
  16 bits per pixel.
  Least significant byte first in each pixel.
  True colour: max red 31 green 63 blue 31, shift red 11 green 5 blue 0
Using default colormap and visual, TrueColor, depth 16.
Got 256 exact BGR233 colours out of 256
Using BGR233 pixel format:
  8 bits per pixel.
  True colour: max red 7 green 7 blue 3, shift red 0 green 3 blue 6
Throughput 20322 kbit/s - changing to Hextile
Throughput 20322 kbit/s - changing from 8bit
Using viewer's native pixel format:
  16 bits per pixel.
  Least significant byte first in each pixel.
  True colour: max red 31 green 63 blue 31, shift red 11 green 5 blue 0
vncviewer: ../rfb/zrleDecode.h:190: void zrleDecode16(int, int, int, int, class
::rdr::InStream *, class ::rdr::ZlibInStream *, U16 *): Assertion `len <= end -
ptr' failed.
---END CONSOLE MESSAGE--

---VNCLOG---
28/09/02 11:11:00 Got connection from client 192.168.0.10
28/09/02 11:11:00 Protocol version 3.3
28/09/02 11:11:03 Pixel format for client 192.168.0.10:
28/09/02 11:11:03   8 bpp, depth 8
28/09/02 11:11:03   true colour: max r 7 g 7 b 3, shift r 0 g 3 b 6
28/09/02 11:11:03 Using ZRLE encoding for client 192.168.0.10
28/09/02 11:11:04 rfbSendUpdateBuf: write: Connection reset by peer
28/09/02 11:11:04 Client 192.168.0.10 gone
28/09/02 11:11:04 Statistics:
28/09/02 11:11:04   framebuffer updates 3, rectangles 3, bytes 47349
28/09/02 11:11:04     ZRLE rectangles 3, bytes 47349
28/09/02 11:11:04   raw bytes equivalent 1364844, compression ratio 28.825192
---END VNCLOG---


Thank you, in advance.

Jerry McBride



-- 

******************************************************************************
                     Registered Linux User Number 185956
          http://groups.google.com/groups?hl=en&safe=off&group=linux
             Join me in chat at #linux-users on irc.freenode.net
    11:06am  up 199 days, 16:15,  6 users,  load average: 1.04, 1.36, 1.47
_______________________________________________
VNC-List mailing list
[EMAIL PROTECTED]
http://www.realvnc.com/mailman/listinfo/vnc-list

Reply via email to