Since installing suse 9.2, using the remote desktop and using vnc -or tightvnc (from a windows workstation) the keystrokes are double/trippled up.
such as i type 'ls' and it outputs 'lssssss'.
Ive noticed if i type slow it doesn't happen. very slow. any tips what to try to fix this? its over an internal network only and its constant and repeatable, always been that way..would like to fix.

I hope this hasnt been discussed already, i did a search of the whole site nothing came up.

Thanks!

Matt

VNC eats up massive resources. Instead of releasing your user, release your display.

Go to SAX2 and there you can release your display (with password), it's a lot faster.

I had the same problem and now everything works really fast.

Since its internal, I'd suggest choosing a slower connection speed. I had similar issues over DSL connection and I just picked Low connection and surprisingly it was just as fast but less delay.

thanks both, I'm not even sure its vnc , im using the remote desktop sharing applet built in with suse 9.2. looking at processes i don't see Xvnc (or vncserver) like i did when i ran the server manually on suse 9.1.

i don't see anything about speed in the host settings..

what's sax2? i looked around didn't see anything relating to vnc. I do know there are a few projects going with vnc compatibility i will try one of those other packages, thanks!

matt

sax2 is accessible from yast. You can adjust settings for display, keyboard, and mouse in it.

thanks i did just find it and try turning on vnc in there am still experimenting with it, thanks!

Well, I enabled vnc w/a pw in Sax2 but can't figure out how to connect to it? I'm not sure if I need to also have remote desktop turned on or to manually start vnc?
I tried connecting to various common ports (5900, etc). also can't find any docs on using vnc configged through sax2. help appreciated. (and already received thanks)

You should disable the firewall. I couldn't get it to work well with the firewall on. Then from the other computer VNC to ipadress:0

that should work. For windows you need realVNC enterprise or something. You need the VNC 3 Protocol.

For the key repeating problem you can start it with the -norepeat flag.

i was JUST about to repost to you guys that i couldn;t get it still and noticed jess's comment about need the version 3 protocol and thats what did it. I did notice in my logs it showed "got connection, ignoring minor version mismatch". apparently it wasn;t ignoring it too successfully even though i got no more errors than that. so on the windows client config i troed checking off the butyton to only use protocol 3.3 and i can connect to :5900, problem solved!
i am now using the remote desktop as configged though sax2. thanks to all folks!

Kumbaya,
It never hurts to help!