Comment 30 for bug 353126

You may want to switch to freeNX until this bug is resolved

On Apr 29, 2009, at 6:11 PM, jose <email address hidden> wrote:

> I don't know if adding more "me too" helps move the importance up or
> not, but this only started when I upgraded to Jaunty and its a real
> real
> real problem. I use the remote desktop all the time. Compiz is on by
> default, and turning if on and off would be a real pain, and is not
> really a good solution only a bad workaround. I sure hope this gets
> fixed soon, I'm considering switching back to intrepid because of
> this,
> --
> Compiz / vnc screen refresh with nvidia-restricted driver
> You received this bug notification because you are a direct subscriber
> of the bug.
> Status in X.Org X server: Confirmed
> Status in “compiz” source package in Ubuntu: Confirmed
> Status in “vino” source package in Ubuntu: Confirmed
> Bug description:
> Binary package hint: compiz
> When using the nvidia-restricted driver and compiz desktop effects
> the vnc server will not refresh the screen. This is being caused by
> the xserver not getting "damaged" by the nvidia-restricted drivers.
> Linked bugs confirm this is not an issue on intel chipsets or nv
> driver.
> Steps to reproduce:
> Enable desktop-effects (default) with nvidia-restricted driver
> Enable remote desktop
> Connect with VNC
> Results:
> You see a screen snapshot of your desktop but if you click a menu
> item there are no updates to the screen.
> Notes:
> If you close and restart the vnc session, you get an updated
> snapshot but still no refreshes.
> Workarounds:
> Use the -noxdamage argument with vncviewer. This is really
> inefficient and bandwidth hungry since the whole screen refreshes.
> Kill compiz and use a different wm (metacity).
> This bug has been confirmed by many others with linked reports.
> Might be an issue with xorg since there is a report of ATI drivers
> with similar issues in .