Red Hat Bugzilla – Bug 505558
Vino only shows first picture, changes on remote screen aren't visible
Last modified: 2014-06-18 05:11:19 EDT
Description of problem:
When i try to connect to vino, it seems to work showing the remote desktop. I try to move cursor to interact with windows but nothing seems to happen, like if keyboard and mouse aren't actives.
But if i disconnect and immediately reconnect i get a new remote desktop image showing that changes applied with mouse were taken into account.
So it seems that vino seems to work but it only sends the first image of the desktop.
I tried from a Windows XP machine with 3 differents vnc viewers : UltraVNC, RealVNC, and Tightvnc. Same result !
Everything worked perfectly well under FC10.
I've been able to find mention of this problem on an old bug delcaration here :
Version-Release number of selected component (if applicable):
rpm -q vino compiz xorg-x11-server-Xorg
Steps to Reproduce:
1.Enable remote desktop
2.Connect with any VNC viewer
Control seems possible but changes in remote desktop are not transmitted to viewer !
working remote desktop
forgot to say that i have compiz fusion running on vino server
turning off compiz solve the problem of remote desktop
same bug as :
I confirm that I have exactly the same trouble:
If compiz is enabled, vino show the first picture of the screen, then changes on remote screen aren't visible.
If compiz is disabled, all works fine.
Occurs on my F11 after F10 upgrade.
#rpm -q vino compiz xorg-x11-server-Xorg
Same symptoms here with:
This also effects F12. No screen refresh if compiz is enabled on the "remote" end when viewing with vncviewer to vino.
There's a bug with X and XDAMAGE. The X server in F8 worked great. Everything after that isn't sending xdamage events. Ubuntu have packaged a version where XDAMAGE is not used, but that causes extra bandwidth usage due to full screen updates instead of partial.
This bug is very old and very annoying. It's probably best reassigned to xorg. I don't think the Gnome/vino guys can do much about it.
*** Bug 505801 has been marked as a duplicate of this bug. ***
All that writing and I forgot to mention the workaround.
Set the GConf key of "/desktop/gnome/remote_access/disable_xdamage" to true. VNC will work again. :)
It's not a permanent workaround though.
The above workaround in your shell: gconftool-2 -s -t bool /desktop/gnome/remote_access/disable_xdamage true
This needs confirmed, the version changed to F12 and probably reassigned.
This message is a reminder that Fedora 11 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 11. It is Fedora's policy to close all
bug reports from releases that are no longer maintained. At that time
this bug will be closed as WONTFIX if it remains open with a Fedora
'version' of '11'.
Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version'
to a later Fedora version prior to Fedora 11's end of life.
Bug Reporter: Thank you for reporting this issue and we are sorry that
we may not be able to fix it before Fedora 11 is end of life. If you
would still like to see this bug fixed and are able to reproduce it
against a later version of Fedora please change the 'version' of this
bug to the applicable version. If you are unable to change the version,
please add a comment here and someone will do it for you.
Although we aim to fix as many bugs as possible during every release's
lifetime, sometimes those efforts are overtaken by events. Often a
more recent Fedora release includes newer upstream software that fixes
bugs or makes them obsolete.
The process we are following is described here:
As mentioned by Andy twice, this also applies to Fedora 12. The version needs to be changed to 12 before 11 EOL.
See https://bugzilla.redhat.com/show_bug.cgi?id=567410, in another bug I was asked to resubmit this for F12.
But just to confirm, this is still a problem on F12.
As Michael mentioned this is not an actual bug with VNC or vino but with xorg or perhaps the nvidia proprietary drivers and the XDAMAGE event not being fired.
This bug also appears to be a *DUPLICATE* of the incredibly old bug https://bugzilla.redhat.com/show_bug.cgi?id=214446 which is also improperly listed as a vino bug.
See bug 214446 comment 22.
*** This bug has been marked as a duplicate of bug 214446 ***