Compiz / vnc screen refresh with nvidia-restricted driver/VirtualBox/ATI fglrx driver using X.org

Bug #353126 reported by Andrew Barbaccia
This bug affects 420 people
Affects Status Importance Assigned to Milestone
Lucid Backports
Undecided
Unassigned
NVIDIA Drivers Ubuntu
Undecided
Unassigned
X.Org X server
Fix Released
High
fglrx
Invalid
Undecided
Unassigned
maverick-backports
Won't Fix
Undecided
Unassigned
vino
Fix Released
Wishlist
vino (Fedora)
Invalid
High
vino (Ubuntu)
Medium
Unassigned
Declined for Jaunty by Timo Aaltonen
Declined for Karmic by Timo Aaltonen
Nominated for Lucid by Agustin
xorg-server (Ubuntu)
Medium
Unassigned
Declined for Jaunty by Timo Aaltonen
Declined for Karmic by Timo Aaltonen
Nominated for Lucid by Agustin

Bug Description

Binary package hint: compiz

When using the nvidia-restricted or some ATI drivers and compiz desktop effects the vnc server will not refresh the screen. This is being caused by the xserver not getting "damaged" by the nvidia-restricted drivers (see https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/353126/comments/245 for details). Linked bugs confirm this is not an issue on intel chipsets or nv driver.

Steps to reproduce:
Enable desktop-effects (default) with nvidia-restricted, virtualBox's display or some ATI driver like RV610
Enable remote desktop
Connect with VNC

Results:
You see a screen snapshot of your desktop but if you click a menu item there are no updates to the screen.
Notes:
If you close and restart the vnc session, you get an updated snapshot but still no refreshes.

Workarounds:
Use the -noxdamage argument with vncviewer. This is really inefficient and bandwidth hungry since the whole screen refreshes.
Kill compiz and use a different wm (metacity).

[Tested with nvidia] Run compiz with the --use-root-window option, eg:
compiz --replace --use-root-window &

This bug has been confirmed by many others with linked reports. Might be an issue with xorg since there is a report of ATI drivers with similar issues in https://bugs.launchpad.net/bugs/328559 .

Revision history for this message
In , Travis (travis-redhat-bugs) wrote :

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

How reproducible:
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

Actual results:

Expected results:

Additional info: The configuration is on a Dell D610 with Intel video drivers.

Revision history for this message
In , Travis (travis-redhat-bugs) wrote :

*** Bug 214448 has been marked as a duplicate of this bug. ***

Revision history for this message
In , Adam (adam-redhat-bugs) wrote :

please, could you specify more when is the desktop effect options?? I can't find
it + which window manager're you using. thanks

Revision history for this message
In , Travis (travis-redhat-bugs) wrote :

In gnome, under System/Preferences/Desktop Effects. You can 'Enable Desktop
Effects' which change the behavior of the Windows to wobble when dragged.

Revision history for this message
In , Victor (victor-redhat-bugs) wrote :

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.

Revision history for this message
In , Adam (adam-redhat-bugs) wrote :

Could you please write me if you join to native vncserver (from vnc-server
package) or to gnome's vino server?

Revision history for this message
In , Travis (travis-redhat-bugs) wrote :

It is the vino server, activated by the Remote Desktop features within Gnome.
This is from a very generic installation of FC6.

Revision history for this message
In , Adam (adam-redhat-bugs) wrote :

This bug isn't in vnc. Reassigning to proper component.

Revision history for this message
In , Didier (didier-redhat-bugs) wrote :

Confirmed on a fully updated F7, with components :

vino-2.18.0-1.fc7
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-1.2.6.22.1_41.fc7 and xorg-x11-drv-nvidia-100.14.11-1.lvn7)

334 comments hidden view all 357 comments
Revision history for this message
In , Daniel Stone (daniels) wrote :

this should be fixed with current git mesa/xserver/et al, i believe.

Revision history for this message
In , Jonh Wendell (wendell) wrote :

(In reply to comment #1)
> this should be fixed with current git mesa/xserver/et al, i believe.
>

Oh, this is a great news. Do you have any idea when a new tarball (release) will be released?
Thanks,

334 comments hidden view all 357 comments
Revision history for this message
In , Tomasz (tomasz-redhat-bugs) wrote :
Revision history for this message
In , Aaron (aaron-redhat-bugs) wrote :

x11vnc apparently works where vino fails:
http://ubuntuforums.org/showthread.php?t=470306

Perhaps the '-noxdamage' option for x11vnc can be reproduced for vino to fix this?

Revision history for this message
In , Bug (bug-redhat-bugs) wrote :

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.
http://fedoraproject.org/wiki/LifeCycle/EOL

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
the change.

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:
http://fedoraproject.org/wiki/BugZappers/F9CleanUp

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

Revision history for this message
In , Bug (bug-redhat-bugs) wrote :

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.

336 comments hidden view all 357 comments
Revision history for this message
In , Andrew Barbaccia (andrew-barbaccia) wrote :

This seems to still be happening on latest Ubuntu Jaunty Beta with -restricted drivers (tested with nvidia restricted). vnc will show a static image with no refreshes. Monitoring the system will show that actions are actually taking place (or starting another vnc session to grab a new 'snapshot').

More info here: https://bugs.launchpad.net/ubuntu/+source/compiz/+bug/353126

Revision history for this message
Andrew Barbaccia (andrew-barbaccia) wrote : Compiz / vnc screen refresh with nvidia-restricted driver

Binary package hint: compiz

When using the nvidia-restricted driver and compiz desktop effects the vnc server will not refresh the screen. This is being caused by the xserver not getting "damaged" by the nvidia-restricted drivers. Linked bugs confirm this is not an issue on intel chipsets or nv driver.

Steps to reproduce:
Enable desktop-effects (default) with nvidia-restricted driver
Enable remote desktop
Connect with VNC

Results:
You see a screen snapshot of your desktop but if you click a menu item there are no updates to the screen.
Notes:
If you close and restart the vnc session, you get an updated snapshot but still no refreshes.

Workarounds:
Use the -noxdamage argument with vncviewer. This is really inefficient and bandwidth hungry since the whole screen refreshes.
Kill compiz and use a different wm (metacity).

This bug has been confirmed by over a dozen people in the linked bugs.

description: updated
Changed in xorg-server:
importance: Undecided → Unknown
status: New → Unknown
Changed in xorg-server:
status: Unknown → Confirmed
Revision history for this message
larson.eric.d@gmail.com (larsoner) wrote :

What's strange about this bug is that I /didn't/ have this problem in Intrepid, but I /do/ have it in Jaunty...

Revision history for this message
Graham Inggs (ginggs) wrote :

I got this problem after upgrading to Jaunty. It used to work fine in Intrepid.

1 comments hidden view all 357 comments
Revision history for this message
giruzz (giruzz) wrote :

Same here. All fine in Intrepid but it doesn't work with Jaunty

Revision history for this message
Teddyber (teddyber) wrote :

same here sine I upgraded too Jaunty. It was fine with Intrepid, Hardy, Gutsy, and Feisty at least (if not even before...)

Revision history for this message
Patrick Kilgore (patrick-kilgore) wrote :

There is a new version of x11 in jaunty which is probably why this is a problem with the new release.

Changed in compiz (Ubuntu):
importance: Undecided → Medium
status: New → Confirmed
Changed in vino (Ubuntu):
importance: Undecided → Medium
status: New → Confirmed
Revision history for this message
Patrick Kilgore (patrick-kilgore) wrote :

I've just noticed that turning off desktop effects fixes the problem.

Revision history for this message
Rocko (rockorequin) wrote :

I also get this problem using VirtualBox's display drivers (see https://bugs.launchpad.net/ubuntu/+source/compiz/+bug/333564 which looks like a duplicate bug): if I am running a VM with desktop effects, I get no updates in vnc, but if I turn desktop effects off, everything returns to normal.

So it seems to be both nvidia and VirtualBox drivers that exhibit this problem. It isn't a problem on another laptop running 3d effects with an ATI card.

Revision history for this message
jecarterii (jecarterii) wrote :

Just upgraded to 9.04 full release from 8.10 .. used update man gui to upgrade.. have same issue.. have to disable all desktop effects for users to vnc my system (which has vino server).. since im using full release, im guessing this issue got thru beta? any chance its gonna get fixed?..
thanks...

Revision history for this message
croaker___ (martin-gautier) wrote :

Confirmed as described.

8.10 -> 9.04 upgrade, proprietary nvidia drivers, screen effects on.
Fails on WinXP->tightvnc->9.04, WinXP->realvnc->9.04, WinXP->ultravnc->9.04, 8.10->Remote Desktop Viewer->9.04

Works in all cases when screen effects switched off.

Revision history for this message
Philip Wyett (philwyett) wrote :

I can confirm this issue and that turning off desktop effects works round the issue.

I ran into the issue after making a machine headless and moving it so had to disable desktop effects in the terminal. Todo this you use the two commands below then restart.

gconftool -s -t string /desktop/gnome/applications/window_manager/current /usr/bin/metacity
gconftool -s -t string /desktop/gnome/applications/window_manager/default /usr/bin/metacity

Revision history for this message
tonyhartfield (anthony-hartfield) wrote :

same problem here very frustrating, is it possible to switch the wm to and from compiz without rebooting?

Revision history for this message
RM (rmajeed) wrote :

Screen Sharing on MacOS 10.5.6, connected to Ubuntu Intrepid, worked well with Visual Effects set to "Normal". When I upgraded Ubuntu to Jaunty (release), Screen Sharing would no longer show updates. Setting Visual Effects to "Off" immediately caused screen updates to resume. It's unclear what the "nodamage" equivalent would be in MacOS Screen Sharing, or I would report that result. I can provide more detailed information if it would be helpful.

Revision history for this message
Trurl (trurl-online) wrote :

I can confirm this issue too and that turning off desktop effects helps. I hope a fix will be published soon :(

Revision history for this message
heggink (herman-eggink) wrote :

After upgrading to Jaunty, I found that my CPU load would constantly be stuck around 60% (which using an E8400 on an idle system is rather strange). Could not find any cause until I replaced vino with x11vnc. After uninstalling vino, not only was my system load back to idle load (few %) but also HD video runs much more smoothly than it ever did + x11vnc works perfectly with (using noxdamage, haven't tried without) all desktop effects enabled.
I run Geforece8500GT, E8400 with 4GB on a shuttle barebone.

Revision history for this message
Emilio Pozuelo Monfort (pochu) wrote : Re: [Bug 353126] Re: Compiz / vnc screen refresh with nvidia-restricted driver

heggink wrote:
> After upgrading to Jaunty, I found that my CPU load would constantly be stuck around 60% (which using an E8400 on an idle system is rather strange). Could not find any cause until I replaced vino with x11vnc. After uninstalling vino, not only was my system load back to idle load (few %) but also HD video runs much more smoothly than it ever did + x11vnc works perfectly with (using noxdamage, haven't tried without) all desktop effects enabled.
> I run Geforece8500GT, E8400 with 4GB on a shuttle barebone.

The CPU issue is a different bug that this one.

Revision history for this message
heggink (herman-eggink) wrote : Re: Compiz / vnc screen refresh with nvidia-restricted driver

i know the CPU issue is a different bug. What I said was that vino caused my CPU issue and vino also happens to be the vnc server. Too much coincidence for me.

Revision history for this message
XCan (xcan-) wrote :

I too can confirm this issue. It worked fine on 8.10, but after upgrading to 9.04, vnc client only displays initial screen. All consecutive actions are carried out (can be seen by restarting the vnc-client and logging in), but the screen on the client does not update.

Revision history for this message
Dan Smith (mrdanpsmith) wrote :

I too can confirm this bug. There was another bug that was similar in the previous versions, except it would be on subsequent X screens (if you had more than 1). I took it from one of the developers on that bug that there was a small patch he submitted to correct the problem, and that the problem had to be applied to the second screen. If this is the same problem, is there any chance we can make sure that the new fix fixes it for additional X screens? Because last time I couldn't use VNC on my second X server because it wouldn't refresh as long as desktop effects were enabled.

I also was able to use this fine in 8.04 and 8.10, Jaunty killed the support. I'm thinking that someone should take a look at the fix in the other bug.

Revision history for this message
Dan Smith (mrdanpsmith) wrote :

Here is the other bug report I filed for the second X server problem:

https://bugs.launchpad.net/bugs/309020

Revision history for this message
Dan Smith (mrdanpsmith) wrote :

Nobody really replied to my bug, the bug that it appears to be the exact same as is linked both in the bug report for my bug, and below:
https://bugs.launchpad.net/ubuntu/+source/vnc/+bug/77442

Revision history for this message
Dan Burke (dan-burke) wrote :

Can a developer explain why this all of a sudden started in Jaunty and was not a problem in Intrepid? The upstream bug report this is linked against is from mid to late 2007. I assume Jaunty didn't "Upgrade" to an Xorg release from 2007. This problem seems to be affecting a lot of people and is a regression, and the lack of activity suggests that it's not going to be fixed in Jaunty... it'd be nice if we heard something about this, as I'm willing to downgrade to Intrepid over this bug.

If this truly is a problem with the new Xorg, why are we tagging on to the upstream bug report from 2007 and not creating a new bug report for the new version?

Revision history for this message
Valentin Rocher (bishiboosh) wrote :

I have this error with Nvidia/Jaunty also. Is there some lead on how to fix this ?

Revision history for this message
Valentin Rocher (bishiboosh) wrote :

Hmmm...As in the duplicate, the importance on this bug must be set to "High", compiz is launched by default and nvidia is present on many computers...This problem renders the vnc server completely unusable.

Revision history for this message
jose (jose-cybergalvez) wrote :

I don't know if adding more "me too" helps move the importance up or not, but this only started when I upgraded to Jaunty and its a real real real problem. I use the remote desktop all the time. Compiz is on by default, and turning if on and off would be a real pain, and is not really a good solution only a bad workaround. I sure hope this gets fixed soon, I'm considering switching back to intrepid because of this,

Revision history for this message
nhasian (nhasian) wrote : Re: [Bug 353126] Re: Compiz / vnc screen refresh with nvidia-restricted driver

You may want to switch to freeNX until this bug is resolved

On Apr 29, 2009, at 6:11 PM, jose <email address hidden> wrote:

> I don't know if adding more "me too" helps move the importance up or
> not, but this only started when I upgraded to Jaunty and its a real
> real
> real problem. I use the remote desktop all the time. Compiz is on by
> default, and turning if on and off would be a real pain, and is not
> really a good solution only a bad workaround. I sure hope this gets
> fixed soon, I'm considering switching back to intrepid because of
> this,
>
> --
> Compiz / vnc screen refresh with nvidia-restricted driver
> https://bugs.launchpad.net/bugs/353126
> You received this bug notification because you are a direct subscriber
> of the bug.
>
> Status in X.Org X server: Confirmed
> Status in “compiz” source package in Ubuntu: Confirmed
> Status in “vino” source package in Ubuntu: Confirmed
>
> Bug description:
> Binary package hint: compiz
>
> When using the nvidia-restricted driver and compiz desktop effects
> the vnc server will not refresh the screen. This is being caused by
> the xserver not getting "damaged" by the nvidia-restricted drivers.
> Linked bugs confirm this is not an issue on intel chipsets or nv
> driver.
>
> Steps to reproduce:
> Enable desktop-effects (default) with nvidia-restricted driver
> Enable remote desktop
> Connect with VNC
>
> Results:
> You see a screen snapshot of your desktop but if you click a menu
> item there are no updates to the screen.
> Notes:
> If you close and restart the vnc session, you get an updated
> snapshot but still no refreshes.
>
> Workarounds:
> Use the -noxdamage argument with vncviewer. This is really
> inefficient and bandwidth hungry since the whole screen refreshes.
> Kill compiz and use a different wm (metacity).
>
> This bug has been confirmed by many others with linked reports.
> Might be an issue with xorg since there is a report of ATI drivers
> with similar issues in https://bugs.launchpad.net/bugs/328559 .

Revision history for this message
Valentin Rocher (bishiboosh) wrote : Re: Compiz / vnc screen refresh with nvidia-restricted driver

That's not really a workaround...The default vnc server on Ubuntu is vino. What's important is to allow all users to use their machine "out-of-the-box" and, with nvidia being present on many hardwares, it seems to me that it's a real problem.

Revision history for this message
nhasian (nhasian) wrote :

I'm not sure its exclusive to nvidia. I read a post on the ubuntu forums that a user with an ATI video card had the same problem. can anyone confirm? I dont have any machines with ATI video cards.

Revision history for this message
Dave Brosius (dbrosius) wrote :

I have an ati card

01:00.0 VGA compatible controller: ATI Technologies Inc RV610 [Radeon HD 2400 XT]

And this exact problem happens for me as well. (only in jaunty)

Revision history for this message
Aerogt3 (perry-robertl) wrote :

I have this same problem. While a fix would be great, how can I disable desktop effects if I am running the Nvidia driver? I cannot seem to figure it out, and this would solve the issue until there is a proper fix.

Revision history for this message
Yuriy Voziy (yuretsz) wrote :

Awfull bug I work with vnc alot. Everything worked fine with 8.10 and upgrade to 9.04 made me unhappy with it.

Revision history for this message
Trurl (trurl-online) wrote :

I installed x11vnc and use this command in the terminal:

x11vnc --noxdamage --passwd XXX -forever

as a work-around until vino is fixed.

Revision history for this message
Emilio Pozuelo Monfort (pochu) wrote : Re: [Bug 353126] Re: Compiz / vnc screen refresh with nvidia-restricted driver

Aerogt3 wrote:
> I have this same problem. While a fix would be great, how can I disable
> desktop effects if I am running the Nvidia driver?

System->Preferences->Appearance, Effects tab

Revision history for this message
jose (jose-cybergalvez) wrote : Re: Compiz / vnc screen refresh with nvidia-restricted driver

reading through the different "workarounds" x11vnc is the best. I can leave compiz turned on and still use vnc to connect ot the machine. Basically you turn off vino (Systems>Preferences>Remote Desktop uncheck sharing) and then I added x11vnc --noxdamage --passwd XXX -forever -shared -alwaysshared to my session. I don't know if shared and alwaysshared are needed options but they seem to make sense. And so far I don't see much of a performance hit with the --noxdamage turned on.

Revision history for this message
Aerogt3 (perry-robertl) wrote :

What I did was turn off desktop effects using compiz simple-ccsm.

Install simple-ccsm from synaptic and then its under preferences I think.

Revision history for this message
jose (jose-cybergalvez) wrote :

well there's a bug in x11vnc too, after a while you get a stuck "a" which requires you to restart the xserver so that workaround isn't going to work for me now

summary: - Compiz / vnc screen refresh with nvidia-restricted driver
+ Compiz / vnc screen refresh with nvidia-restricted driver/VirtualBox
John Affleck (jraffleck)
summary: - Compiz / vnc screen refresh with nvidia-restricted driver/VirtualBox
+ Compiz / vnc screen refresh with nvidia-restricted driver/VirtualBox/ATI
+ fglrx driver
Changed in vino:
status: Unknown → Fix Released
Changed in compiz (Ubuntu):
status: Confirmed → Invalid
affects: compiz (Ubuntu) → xorg-server (Ubuntu)
Changed in xorg-server (Ubuntu):
status: Invalid → New
Bryce Harrington (bryce)
tags: added: needs-xorglog
tags: added: needs-lspci-vvnn
Changed in xorg-server (Ubuntu):
status: New → Incomplete
koshari (holto2go)
Changed in vino:
status: Fix Released → Incomplete
300 comments hidden view all 357 comments
Revision history for this message
In , Emmanuel (emmanuel-redhat-bugs) wrote :

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 ?

J N B (wdflr73)
summary: Compiz / vnc screen refresh with nvidia-restricted driver/VirtualBox/ATI
- fglrx driver
+ fglrx driver using X.org prior to version 7.5
summary: Compiz / vnc screen refresh with nvidia-restricted driver/VirtualBox/ATI
- fglrx driver using X.org prior to version 7.5
+ fglrx driver using X.org prior to release 7.5
Revision history for this message
In , BrianK (baking666) wrote :

(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.

Agustin (agustin-bosso)
description: updated
Revision history for this message
In , Chris (chris-redhat-bugs) wrote :

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.

Revision history for this message
In , Walter (walter-redhat-bugs) wrote :

I confirm this bug in FC12.

Bryce Harrington (bryce)
Changed in xorg-server (Ubuntu):
status: Incomplete → Fix Released
koshari (holto2go)
Changed in xorg-server (Ubuntu):
status: Fix Released → Confirmed
summary: Compiz / vnc screen refresh with nvidia-restricted driver/VirtualBox/ATI
- fglrx driver using X.org prior to release 7.5
+ fglrx driver using X.org
Rocko (rockorequin)
Changed in vino (Fedora):
importance: Undecided → Unknown
status: New → Unknown
Revision history for this message
In , txvs (txvs-redhat-bugs) wrote :

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.

Regards.

Rocko (rockorequin)
description: updated
Revision history for this message
In , A (a-redhat-bugs) wrote :

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

Bryce Harrington (bryce)
Changed in xorg-server (Ubuntu):
status: Confirmed → Incomplete
tags: added: needs-retested-on-lucid-by-june
Revision history for this message
In , John (john-redhat-bugs) wrote :

Issue seen here on updated F12:

-nVidia Corporation GeForce Go 7900 GS
-kernel-2.6.32.11-99.fc12.i686
-vino-2.28.1-1.fc12.i686
-xorg-x11-server-Xorg-1.7.6-3.fc12.i686
-kmod-nvidia-2.6.32.11-99.fc12.i686-195.36.15-1.fc12.i686

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.

-John

Revision history for this message
In , John (john-redhat-bugs) wrote :

Oh and the workaround in https://bugzilla.redhat.com/show_bug.cgi?id=214446#c18 seems to work after restarting vino-server.

-John

Revision history for this message
In , Sandro (sandro-redhat-bugs) wrote :

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.

Sandro Mani (sandromani)
Changed in xorg-server (Ubuntu):
status: Incomplete → Fix Released
Changed in nvidia-drivers-ubuntu:
status: New → In Progress
Changed in fglrx:
status: New → Confirmed
Sandro Mani (sandromani)
Changed in vino (Ubuntu):
status: Confirmed → Fix Released
Revision history for this message
In , Michael (michael-redhat-bugs) wrote :

*** Bug 505558 has been marked as a duplicate of this bug. ***

Revision history for this message
In , Michael (michael-redhat-bugs) wrote :

Should this be closed now? CANTFIX? (binary drivers)

Changed in nvidia-drivers-ubuntu:
status: In Progress → Fix Released
Changed in lucid-backports:
status: New → Confirmed
Changed in xorg-server (Ubuntu):
status: Fix Released → Fix Committed
status: Fix Committed → Fix Released
Steve Stalcup (vorian)
Changed in lucid-backports:
status: Confirmed → Invalid
Changed in xorg-server:
importance: Unknown → High
status: Confirmed → Fix Released
Changed in vino:
importance: Unknown → Wishlist
status: Incomplete → Fix Released
Revision history for this message
In , Bug (bug-redhat-bugs) wrote :

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:
http://fedoraproject.org/wiki/BugZappers/HouseKeeping

Revision history for this message
In , John (john-redhat-bugs) wrote :

Last I checked this was still an issue with 13. Haven't tried 14 yet.

Revision history for this message
In , Michael (michael-redhat-bugs) wrote :

(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.

Revision history for this message
In , John (john-redhat-bugs) wrote :

Oh, I missed that. Will do. Sorry for the noise. Feel free to close if others have tested and confirmed thats it.

-John

Changed in xorg-server:
importance: High → Unknown
Changed in xorg-server:
importance: Unknown → High
36 comments hidden view all 357 comments
Revision history for this message
Kim Botherway (dj-dvant) wrote :

This is still a problem on Ubuntu 11.04:

fglrx 2:8.840-0ubuntu4
compiz 1:0.9.4+bzr20110415-0ubuntu2
vino 2.32.1-0ubuntu2
xorg 1:7.6+4ubuntu3

Revision history for this message
Josh (majik) wrote :

I am having the problem with ATI video card on 11.04.

I don't understand why this VNC server is still shipping with Ubuntu with this problem after several major releases.

36 comments hidden view all 357 comments
Revision history for this message
In , Michael (michael-redhat-bugs) wrote :

Just make sure you update all packages (Fedora and proprietary).

35 comments hidden view all 357 comments
Revision history for this message
In , Thorsten Giesecke (b-info-j) wrote :

This is still a problem on Ubuntu 10.10 (maverick):

kernel 2.6.25-29-generic
gnome 2.32.0
fglrx 2:8.780-0ubuntu2
compiz 1:0.8.6-0ubuntu9.2
vino 2.32.0-0ubuntu1.2
xorg 1:7.5+6ubuntu3

Revision history for this message
Bryce Nesbitt (bryce2) wrote :

Confirmed: 10.04
Removing NVida proprietary drivers, and suddenly all the windows and menus that were invisible on the remote show up.
On the local machine they were always visible.

Revision history for this message
Josh (majik) wrote :

That's because removing the driver eliminates the source of the problem along with the acceleration required to use Desktop Effects.

You might want to read the bug report before posting a comment.

Revision history for this message
Greg Michalec (greg-primate) wrote :

Unfortunately, I'm still seeing this issue in Oneric Beta 1.
Steps to reproduce:
1) log in to guest session
2) Enable Desktop Sharing
3) Open Remote Desktop Viewer
4) Open VNC connection to localhost:5900

You'll see the initial screen, and the mouse will move around, but no screen updates are made. If you repeat the steps abovem , but starting the guest session in 'Ubuntu 2D' mode, it will work as expected.

Obviously there is something incompatible between the VNC server and desktop compositing, but since Vino, Vinaigre, and Compiz are now all part of the default Ubuntu experience, it seems that the current situation will cause nothing but frustration for new users. Even if there is no programmatic solution, can't there be some sort of indication of why this won't work, or a best way to work around - i.e. maybe a notification in the Desktop Sharing preferences tool warning that sharing will not work unless you restart to a 2d session (if this is indeed the best/easiest solution).

Revision history for this message
Bryce Harrington (bryce) wrote :

This bug still exists, but we are tracking it at bug #772873; this report is a dupe of that one. I would set this as a dupe, but because this one has so many dupes on it, launchpad chokes.

Anyway, subscribe to bug #772873 if you want to follow it.

The short story is, it seems to be a bug in the fglrx driver, we're going to escalate it to AMD. Assuming it gets fixed we'll try to include the updated driver in the x-updates PPA. See bug #772873 for workarounds and more information.

Changed in fglrx:
status: Confirmed → Invalid
Revision history for this message
Evan Broder (broder) wrote :

I'm closing the maverick-backports task on this bug due to Ubuntu 10.10 (Maverick Meerkat) no longer being supported.

This bug is being closed by a bot. If you feel the change was made in error, please feel free to re-open the bug. However, backports requests for Ubuntu 10.10 (Maverick Meerkat) are no longer being accepted.

Changed in maverick-backports:
status: New → Won't Fix
Revision history for this message
Josh (majik) wrote :

I have discovered a useful workaround:

Splashtop.

It is a much more functional remote desktop solution than VNC or Vino. It has sound. You can play 3D games over it and even Second Life works beautifully.

And it's available in the Ubuntu Software Center for free.

This really should be the default remote desktop. It blows Microsoft's Remote Desktop away.

If you need a desktop client it's under "other products" on the Splashtop App download page.

Revision history for this message
MestreLion (mestrelion) wrote :

@Josh: being gratis does not mean it is free. Ubuntu, like Debian, values software freedom, so a proprietary software can ever be the default one.

Changed in vino (Fedora):
importance: Unknown → High
status: Unknown → Invalid
29 comments hidden view all 357 comments
Revision history for this message
Olleg Samoylov (olleg) wrote :

Ubuntu 17.10
tigervnc-xorg-extension 1.7.0+dfsg-7ubuntu1
xorg 1:7.7+19ubuntu3
cinnamon 3.4.6-1
nvidia-384 384.111-0ubuntu0.17.10.1

Bug exactly the same.

Displaying first 40 and last 40 comments. View all 357 comments or add a comment.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.