ubuntu-x-swat team mailing list archive

[Bryce Harrington <bryce@xxxxxxxxxxxxxxxxxxx>]

There's so many comments on this bug from so many people, it's hard to
understand what's wrong exactly.

I notice there were some xserver patches proposed as fixes; I've
verified these are included in the xserver we ship with lucid.

I don't see any comments about having this issue with the open drivers,
which makes me wonder if the problem is particular to the binary drivers
(like, broken or missing XDamage support or something).  In this case,
the xserver task can be closed, and instead the issue should be raised
directly to NVIDIA, ATI, and virtualbox to provide the missing support.
These fixes are not something that can be done at the distro level.

My guess is that the xserver API here changed in some fashion, causing
this to break with the binary drivers, but they have not been updated to
fix the issue.  Perhaps this use case is not one they test?  Probably
the logical next step would be to approach NVIDIA and ATI about this,
for further information.

Given all that, the xorg-server task can be closed.  I don't think there
is anything we can change in xorg-server at the distro level to address
this issue.  However I'll leave the Lucid nomination in case the vino
community wants to consider adding one of the various workarounds
discussed here for Lucid.  I'll also leave the upstream xserver bug
report open in case I'm wrong and there is something that can be done in
the xserver; if that upstream bug report gets some activity by upstream
developers indicating that this could be fixed in xserver, feel free to
reopen the xorg-server task.

** Changed in: xorg-server (Ubuntu)
       Status: Incomplete => Fix Released

-- 
Compiz / vnc screen refresh with nvidia-restricted driver/VirtualBox/ATI fglrx driver using X.org prior to release 7.5
https://bugs.launchpad.net/bugs/353126
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in ubuntu.