Description of problem: Using F11 x86_64, I've noticed that vino presents a black screen whenever I turn on compiz. With compiz off, vino presents the screen to remote clients properly. Version-Release number of selected component (if applicable): vino-2.26.1-2.fc11.x86_64 tigervnc-0.0.90-0.10.fc11.x86_64 libvncserver-0.9.1-4.fc11.x86_64 Steps to Reproduce: 1. turn on vino and compiz 2. VNC into the machine and observe black screen 3. turn compiz off 4. VNC should now work properly
same report here ! i only get first screen then impossible to see changes on remote desktop turning off compiz solves the problem !
I get the same problem. My packages are vino-2.26.2-1.fc11.x86_64 compiz-0.7.8-18.fc11.x86_64 tigervnc-0.0.91-0.11.fc11.x86_64 libvncserver-0.9.1-4.fc11.x86_64
This does not happen with x11vnc even without the noxdamage option. So it looks like it is a vino-server problem. My workaround was to install x11vnc (had to compile from source since there are no rpm's for fedora 11) and use the following .x11vncrc file. # --noxdamage -rfbauth .vnc/passwd -forever -display :0 -tightfilexfer -solid black -cursor arrow -loop I am using crontab to restart it after server reboot.
I have this issue too, this seems to have been present through the whole life of F11.
Adding "me too" as under F10 and the old version of vino with compiz turned on allowed you to view your desktop and work.
Just FYI, the folks over in Ubuntu discovered the same bug: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/353126 Would much appreciate a fix to this ... one of my basic needs of this desktop is to connect to an existing session remotely, which as far as I can tell, only vino can do.
Still a problem in fedora 12.
This is a dupe of bug 505558. Even though the initial screen symptoms are different, the bug is still the same. XDAMAGE events are not be propagated any more from the VNC server to the client. *** This bug has been marked as a duplicate of bug 505558 ***