After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 595949 - XDamage with Compiz not handled correctly
XDamage with Compiz not handled correctly
Status: RESOLVED NOTGNOME
Product: vino
Classification: Applications
Component: Server
2.28.x
Other Linux
: Normal major
: ---
Assigned To: Vino Maintainer(s)
Vino Maintainer(s)
: 598636 599817 618543 (view as bug list)
Depends on:
Blocks:
 
 
Reported: 2009-09-22 13:08 UTC by Andrew Barbaccia
Modified: 2011-05-02 21:21 UTC
See Also:
GNOME target: ---
GNOME version: ---



Description Andrew Barbaccia 2009-09-22 13:08:19 UTC
Currently Vino does work with Compiz. This has been a problem in Ubuntu since 9.04 and is still present with 9.10.

When enabling Compiz, the Vino server will connect, but not refresh. So, for example, when you click a menu, nothing will change on the VNC Client, but if you are watching the host machine, the updates are happening. If you reconnect the VNC Client (which forces a full refresh) the changes are displayed.

I am fairly confident this is directly related to the XDamage extension. If you use the Disable XDamage gconf option created in #533613 (https://bugzilla.gnome.org/show_bug.cgi?id=533613) all refreshes work as expected but this is non-ideal for two reasons:

1. It forces users to make chagnes with gconf-editor
2. Increased bandwidth consumption

This has been confirmed while using Nvidia restricted drives and fglrx. There are confirmed reports of it working with Intel chipsets but nothing of recent.

Please let me know which logs and how I may assist in debugging this problem. I feel it is a real show-stopper for vino since compiz is enabled by default on most major distributions.

Linux 2.6.31
Vino 2.28.0
Nvidia 185.18.36
Comment 1 Andrew Barbaccia 2009-09-22 13:10:12 UTC
Also, bug report in Launchpad (https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/353126)

Lots of comments, but many are "me too" and work arounds.
Comment 2 Jonh Wendell 2009-10-16 13:48:56 UTC
*** Bug 598636 has been marked as a duplicate of this bug. ***
Comment 3 Jonh Wendell 2009-10-27 18:35:24 UTC
*** Bug 599817 has been marked as a duplicate of this bug. ***
Comment 4 rockorequin 2010-03-21 23:05:17 UTC
This is still an issue with vino 2.28.1 in Ubuntu 10.04 (nvidia 195.36.15 drivers). I'm curious: is it a hard bug to fix? It obviously affects many people (see the Ubuntu bug), but there's been no progress in more than a year since it was originally discovered.
Comment 5 Jonh Wendell 2010-06-08 20:33:52 UTC
*** Bug 618543 has been marked as a duplicate of this bug. ***
Comment 6 David King 2011-05-02 21:21:06 UTC
As mentioned in the Launchpad report linked above, this is an issue of closed-source graphics drivers. There is a fixed version of the nVidia drivers available, but not for the ATi drivers. See:

http://www.nvidia.com/object/linux-display-amd64-256.35-driver.html

for the nVidia driver fix.