Description of problem:
The screen does not refresh when connecting to a VNC Server (remote desktop)
that has 'Desktop Effects' enabled.
When connecting to a Server with Desktop Effects enabled, a screen shot of the
desktop is displayed in the client but never again updates. You can monitor
the Server's display and see that the mouse and keyboard function, however no
output can be seen through the VNC client.
Version-Release number of selected component (if applicable): Zod
This is consistent with my configuration. Disabling Desktop Effects
immediately resolved the problem.
Steps to Reproduce:
1. Enable desktop effects
2. Establish a VNC connection to FC6 from remote machine
3. Note the screen displays, but you do not recieve and screen updates
Additional info: The configuration is on a Dell D610 with Intel video drivers.
*** Bug 214448 has been marked as a duplicate of this bug. ***
please, could you specify more when is the desktop effect options?? I can't find
it + which window manager're you using. thanks
In gnome, under System/Preferences/Desktop Effects. You can 'Enable Desktop
Effects' which change the behavior of the Windows to wobble when dragged.
I have the same problem, my window manager is the default one, compiz, it shows
up in the ps command as following :
compiz --sm-client-id default1 gconf
If you exits the vncviewer and restart the session the image is updated.
Could you please write me if you join to native vncserver (from vnc-server
package) or to gnome's vino server?
It is the vino server, activated by the Remote Desktop features within Gnome.
This is from a very generic installation of FC6.
This bug isn't in vnc. Reassigning to proper component.
Confirmed on a fully updated F7, with components :
vnc-4.1.2-18.fc7 (for vncviewer)
compiz-0.4.0-1.fc7 (for desktop effects)
Disclaimer : tested with the proprietary nvidia driver
(kmod-nvidia-100.14.11-22.214.171.124.1_41.fc7 and xorg-x11-drv-nvidia-100.14.11-1.lvn7)
This bug is a duplicate of https://bugzilla.redhat.com/show_bug.cgi?id=208983
x11vnc apparently works where vino fails:
Perhaps the '-noxdamage' option for x11vnc can be reproduced for vino to fix this?
Fedora apologizes that these issues have not been resolved yet. We're
sorry it's taken so long for your bug to be properly triaged and acted
on. We appreciate the time you took to report this issue and want to
make sure no important bugs slip through the cracks.
If you're currently running a version of Fedora Core between 1 and 6,
please note that Fedora no longer maintains these releases. We strongly
encourage you to upgrade to a current Fedora release. In order to
refocus our efforts as a project we are flagging all of the open bugs
for releases which are no longer maintained and closing them.
If this bug is still open against Fedora Core 1 through 6, thirty days
from now, it will be closed 'WONTFIX'. If you can reporduce this bug in
the latest Fedora version, please change to the respective version. If
you are unable to do this, please add a comment to this bug requesting
Thanks for your help, and we apologize again that we haven't handled
these issues to this point.
The process we are following is outlined here:
We will be following the process here:
http://fedoraproject.org/wiki/BugZappers/HouseKeeping to ensure this
doesn't happen again.
And if you'd like to join the bug triage team to help make things
better, check out http://fedoraproject.org/wiki/BugZappers
This bug is open for a Fedora version that is no longer maintained and
will not be fixed by Fedora. Therefore we are closing this bug.
If you can reproduce this bug against a currently maintained version of
Fedora please feel free to reopen thus bug against that version.
Thank you for reporting this bug and we are sorry it could not be fixed.
This issue is still there on an up to date fedora 11 machine.
I'm using vino for the desktop sharing service, have desktop effects enabled, and an nvidia graphic card.
I've tried vinagre and vncviewer in order to connect to vino, and I obtain the exact same behaviour than what the original reporter described.
Will this bug be reopened, or do I need to open a new one ?
(In reply to comment #14)
> This issue is still there on an up to date fedora 11 machine.
> I'm using vino for the desktop sharing service, have desktop effects enabled,
> and an nvidia graphic card.
> I've tried vinagre and vncviewer in order to connect to vino, and I obtain the
> exact same behaviour than what the original reporter described.
> Will this bug be reopened, or do I need to open a new one ?
I can confirm same bug with ubuntu...I have networked computer with my sister and she was running ubuntu 8.10 ...vino worked fine...But when I upgraded her to 9.04 (yes 9.10 is out) her vino started doing what has been described.
I was using vncviewer on FC8 through FC10 to remotely control and view
the desktop of a Mac OSX machine using the native OSX remote desktop capability (which is essentially VNC). After an upgrade to FC12, the vncviewer
on the FC12 machine now exhibits the symptoms described here-- namely, you
get one screen image which then does not update after you do anything on the Mac desktop. The keyboard and mouse traffic do move from FC12 to the Mac but screen updates in the return direction do not occur.
Also, coincident with the upgrade to FC12 from FC10, the application 'x2vnc'
now fails to work. The cursor will move down to the lower left corner of the
screen but fails to move onto the Mac desktop. I have lost the ability to control the Mac desktop from the FC12 Linux desktop as a result.
There have been no changes to the Mac OSX installation. Only the Linux machine was changed from FC10 to FC12. Additionally, it was a fresh install of FC12 rather than an in-place upgrade from FC10.
I confirm this bug in FC12.
The same on Fedora 11.
vino + fglrx + desktop effects --> no screen refresh on vnc client.
vino + fglrx - desktop effects --> normal screen refresh on vnc client.
https://bugzilla.redhat.com/show_bug.cgi?id=214446 seems to be a duplicate of this bug. Ubuntu launchpad says the bug is in xorg or possibly the ATI/nvidia drivers: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/353126
For a workaround in your shell type:
gconftool-2 -s -t bool /desktop/gnome/remote_access/disable_xdamage true
Issue seen here on updated F12:
-nVidia Corporation GeForce Go 7900 GS
When connecting to vino with any vnc client, I can see the initial rendering of the desktop, but no changes/updates are seen through the client. The updates can still be seen on the primary screen.
Let me know if I can provide any more info.
Oh and the workaround in https://bugzilla.redhat.com/show_bug.cgi?id=214446#c18 seems to work after restarting vino-server.
This issue only remains with the proprietary ati driver and virtualbox additions driver. The issue with the proprietary nvidia driver has been fixed in the latest 256 beta release (http://www.nvnews.net/vbulletin/showthread.php?p=2255561), the issue does not appear to affect any open intel / ati / nvidia drivers.
*** Bug 505558 has been marked as a duplicate of this bug. ***
Should this be closed now? CANTFIX? (binary drivers)
This message is a reminder that Fedora 12 is nearing its end of life.
Approximately 30 (thirty) days from now Fedora will stop maintaining
and issuing updates for Fedora 12. 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 '12'.
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 12'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 12 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:
Last I checked this was still an issue with 13. Haven't tried 14 yet.
(In reply to comment #26)
> Last I checked this was still an issue with 13. Haven't tried 14 yet.
John, you're using the proprietary driver. Make sure you are using the latest version. At least the 256.xx or 260.xx series driver. The issue was resolved. This should be closed.
Oh, I missed that. Will do. Sorry for the noise. Feel free to close if others have tested and confirmed thats it.
Just make sure you update all packages (Fedora and proprietary).