Bug#361304: vino: causes xorg to take 100% cpu

[Christian Pernegger]

> Can you try the unstable version (it'll pull a number of libs from
> unstable as well) and see if it's any better? This version is using
> libxdamage, so I have reasons to think it will.

Done.

xorg CPU usage is 12-20% now with a client connected vs.
0-1% with no client connected. Better, but still seems high.

Additionally the display (on the client) updates very slowly now
- windows kind of shuffle over the screen when moved, etc ...
Of course there is lag with the testing version as well, but not that bad.

Any other ideas? Or is such performance expected at this point in
vino development and I should try other remote-control means?

Thanks,

C.