Hello,
I have been playing with VINO on Fedora Core 5 Test 3 but I find it pretty unusable. First, screen updates are painfully slow: sometimes on the real desktop I launch a gnome-terminal, but it takes up to five seconds for the window to appear on the remote VNC client (it appears almost instantly on the real desktop). Other times, working on the real desktop produces no updates on the remote VNC client.
At first, I thought VINO wasn't using XDamage, but it seems it is, since "xpyinfo | grep -i damage" reveals the local X server supports the XDamage extension, and also "ldd /usr/libexec/vino-server" reveals it is linked against libXdamage.so.1.
Am I the only one experiencing these issues with VINO? Thanks.
On Fri, 2006-03-03 at 01:07 +0100, Felipe Alfaro Solana wrote:
Hello,
I have been playing with VINO on Fedora Core 5 Test 3 but I find it pretty unusable. First, screen updates are painfully slow: sometimes on the real desktop I launch a gnome-terminal, but it takes up to five seconds for the window to appear on the remote VNC client (it appears almost instantly on the real desktop). Other times, working on the real desktop produces no updates on the remote VNC client.
Am I the only one experiencing these issues with VINO?
No, I find vino to be unusably slow and buggy as well. I use the vnc X server extension instead. Which oddly enough, is even faster than using a dedicated Xvnc server. The VNC extension seems to have broken in test3 however...
Callum Lerwick wrote:
No, I find vino to be unusably slow and buggy as well. I use the vnc X server extension instead. Which oddly enough, is even faster than using a dedicated Xvnc server. The VNC extension seems to have broken in test3 however...
Have you filed a bug report on the VNC extension being broken?
On Sat, 2006-03-04 at 04:12 +0530, Rahul Sundaram wrote:
Callum Lerwick wrote:
No, I find vino to be unusably slow and buggy as well. I use the vnc X server extension instead. Which oddly enough, is even faster than using a dedicated Xvnc server. The VNC extension seems to have broken in test3 however...
Have you filed a bug report on the VNC extension being broken?
Nope. FC5t3 broke a bunch of stuff (Can't log in to Gnome either) on this particular system, (Laptop upgraded just fine, go fig) and I don't have a lot of time (School) to deal with it right now. Bleh.
Am I the only one experiencing these issues with VINO?
No, I find vino to be unusably slow and buggy as well. I use the vnc X server extension instead. Which oddly enough, is even faster than using a dedicated Xvnc server. The VNC extension seems to have broken in test3 however...
Are you sure? I'm using it right now with no apparent problems.