Ubuntu VNC Refresh Problem

[firefly2442]

Hello. Under "System", "Preferences", "Remote Desktop" on Ubuntu... there's a nice little window to setup VNC. This works great except when I login there's refresh problems. I'll open things and move windows around and nothing will show up or it will be messed up. I believe it's a refresh issue but I'm not sure how to fix it. Could it be the fact that I'm using tightvncserver? Thanks in advance.

[Teutons]

I have the exact same problem... Where you able to fix it?

[[HUN]Levente]

Same problem here.
No advanced Ubuntu user had a problem like this? :)

[QwizzTest]

Hello. Under "System", "Preferences", "Remote Desktop" on Ubuntu... there's a nice little window to setup VNC. This works great except when I login there's refresh problems. I'll open things and move windows around and nothing will show up or it will be messed up. I believe it's a refresh issue but I'm not sure how to fix it. Could it be the fact that I'm using tightvncserver? Thanks in advance.



What client are you using?

[[HUN]Levente]

What client are you using?

realvnc, winxp

[simon0t7]

hm. I have the same problem too

[ronmarley1]

I use the TightVNC client, Fast Compression and it works fine into Redhat ES4 and Ubuntu Breezy.

[simon0t7]

will try that ....

[simon0t7]

tried tightvnc as my viewer, no difference

[[HUN]Levente]

Noone can solve this problem? It's very annoying...

[QwizzTest]

Levente']Noone can solve this problem? It's very annoying...

What are your connection speeds (local and remote)?

What are your realVNC viewer settings?

[[HUN]Levente]

What are your connection speeds (local and remote)?

What are your realVNC viewer settings?

Which is local and which is remote? :)

So, where the VNC server runs: 2560/512kbit/s
Where the VNC client is: 100/100mbit/s

I don't think the connection speed could be the problem...

I tried to set VNC viewer to lower color depth and no wallpaper, but it didn't help...

[Divide By Zero]

I'm having the same problem. Trying to control my office computer (Ubuntu - Dapper) with the living room laptop (WinXP RealVNC or TightVNC) over 10/100. It used to work on a previous installation of Dapper between these machines. I didn't muck with VNC on the Dapper machine this time before it broke. I've tried color depths, etc. Requesting screen refreshes through both clients doesn't do any good.

[_hannu]

My VNC infact did worked OK, but then I installed Ati video drivers (becauce of resume problems). After that I have the same problem...
-Hannu

[Alcopops]

similar problem here, I can establish a session, my remote desktop is displayed, but it will not refresh, even if you prompt it to in the client.

I've tried the default edgy vnc server and tightvnc server (from repositories) i get the same each time. I've also tried it from the same box via gome-rdp and accross the internet from an xpbox using tightvncviewer; same result.

I have nvidia drivers installed and beryl if that makes a difference.

Possibly there is an incompatibility somewhere but, being a noob, i wouldn't know where to start looking

hope theres some experts who can help.

peace out,

Jaime

[Alcopops]

Update to my last post,

Vnc server at least the default edgy one (Libvncserver?) will not work with beryl desktop manager. If you have it running and don't get screen updates but do get a connection. Try switching back to metacity. Worked for me!!

Libvncserver is dead slow though so I will give tightvncserver a go since it performed well on win32.

cheers,

Jaime

[martinitime1975]

It's not perfect, but I think I have an answer. I have the exact same problems with remote desktop on my ubuntu dapper box, and trying to connect to it using realvnc from windows. The problem is with the :0 desktop (the one you see if you're using the machine directly). Try this:

In ubuntu, run this at the command prompt:

realvncserver -geometry 1280x1024 -depth 16

You may be prompted to specify a password, if not it's either yours or the root password (you'll need this when you connect with the vnc viewer). You should get some output that lists the new vnc session server name, i.e. server:1 (instead of the default, server:0)

Using a vnc viewer, connect using that new server name server:1 (1 is the session number. Every time you invoke vncserver, it creates a new unique session, until you kill them with vncserver -kill :1 or whatever session you need to kill).

You should get a clean desktop and the refresh problem goes away. Let me know what you think.

[[HUN]Levente]

Thanks, this helped for me.