Discussion:
[Bug 353126] Re: Compiz / vnc screen refresh with nvidia-restricted driver/VirtualBox/ATI fglrx driver using X.org
Valentin Rocher
2010-07-04 09:46:58 UTC
Permalink
As the fix has been released in the nvidia drivers, couldn' they be
backported for Jaunty/Karmic/Lucid ?

** Changed in: nvidia-drivers-ubuntu
Status: In Progress => Fix Released

** Also affects: lucid-backports
Importance: Undecided
Status: New

** Changed in: lucid-backports
Status: New => Confirmed
--
Compiz / vnc screen refresh with nvidia-restricted driver/VirtualBox/ATI fglrx driver using X.org
https://bugs.launchpad.net/bugs/353126
You received this bug notification because you are a member of Ubuntu
Backporters, which is the registrant for lucid-backports.
VPablo
2010-07-04 10:09:21 UTC
Permalink
It needs to be backported xserver 1.7.0 on Karmic and Jaunty too as
mentioned Aaron on #278. I don't think this could be done on previous
distros.
--
Compiz / vnc screen refresh with nvidia-restricted driver/VirtualBox/ATI fglrx driver using X.org
https://bugs.launchpad.net/bugs/353126
You received this bug notification because you are a member of Ubuntu
Backporters, which is the registrant for lucid-backports.
raraki-adpt
2010-07-08 18:44:09 UTC
Permalink
I have this issue with both remote desktop server and client running
Ubuntu 10.4, server uses ATI/AMD FGLRX graphics driver; either disabling
desktop-effects or setting noxdamage to true in gconf-editor are
verified workarounds, but it would be great to have a fix.
--
Compiz / vnc screen refresh with nvidia-restricted driver/VirtualBox/ATI fglrx driver using X.org
https://bugs.launchpad.net/bugs/353126
You received this bug notification because you are a member of Ubuntu
Backporters, which is the registrant for lucid-backports.
Pierce Albert
2010-07-15 02:39:49 UTC
Permalink
** Changed in: xorg-server (Ubuntu)
Status: Fix Released => Fix Committed

** Changed in: xorg-server (Ubuntu)
Status: Fix Committed => Fix Released
--
Compiz / vnc screen refresh with nvidia-restricted driver/VirtualBox/ATI fglrx driver using X.org
https://bugs.launchpad.net/bugs/353126
You received this bug notification because you are a member of Ubuntu
Backporters, which is the registrant for lucid-backports.
swatspyder
2010-07-15 03:23:43 UTC
Permalink
Not working for me. 10.04 AMD64 with NVIDIA Drivers. Connection from
Android OS to Ubuntu via VNC. Had to disable Visual Effects to be able
to receive screen refreshes.
--
Compiz / vnc screen refresh with nvidia-restricted driver/VirtualBox/ATI fglrx driver using X.org
https://bugs.launchpad.net/bugs/353126
You received this bug notification because you are a member of Ubuntu
Backporters, which is the registrant for lucid-backports.
Troy Ready
2010-07-15 03:34:53 UTC
Permalink
swatspyder: For Lucid, It requires the drivers from the right PPA -- see
comment 280.
--
Compiz / vnc screen refresh with nvidia-restricted driver/VirtualBox/ATI fglrx driver using X.org
https://bugs.launchpad.net/bugs/353126
You received this bug notification because you are a member of Ubuntu
Backporters, which is the registrant for lucid-backports.
swatspyder
2010-07-15 03:38:31 UTC
Permalink
Thank you Troy.
--
Compiz / vnc screen refresh with nvidia-restricted driver/VirtualBox/ATI fglrx driver using X.org
https://bugs.launchpad.net/bugs/353126
You received this bug notification because you are a member of Ubuntu
Backporters, which is the registrant for lucid-backports.
Steve Stalcup
2010-08-05 18:13:54 UTC
Permalink
This should be a Stable Release Update and not a Backport.

Please see https://wiki.ubuntu.com/StableReleaseUpdates for information
on how to request an SRU

** Changed in: lucid-backports
Status: Confirmed => Invalid
--
Compiz / vnc screen refresh with nvidia-restricted driver/VirtualBox/ATI fglrx driver using X.org
https://bugs.launchpad.net/bugs/353126
You received this bug notification because you are a member of Ubuntu
Backporters, which is subscribed to lucid-backports.
Kriston Rehberg
2010-08-05 19:38:59 UTC
Permalink
I do not have any idea what you are talking about.
I reported a bug.
I hope this does not mean you are marking the whole bug invalid, and
therefore the bug is quietly ignored.

Kris
Post by Steve Stalcup
This should be a Stable Release Update and not a Backport.
Please see https://wiki.ubuntu.com/StableReleaseUpdates for information
on how to request an SRU
** Changed in: lucid-backports
Status: Confirmed => Invalid
--
Compiz / vnc screen refresh with nvidia-restricted driver/VirtualBox/ATI
fglrx driver using X.org
https://bugs.launchpad.net/bugs/353126
You received this bug notification because you are a direct subscriber
of a duplicate bug.
--
Kriston Rehberg
http://kriston.net/
--
Compiz / vnc screen refresh with nvidia-restricted driver/VirtualBox/ATI fglrx driver using X.org
https://bugs.launchpad.net/bugs/353126
You received this bug notification because you are a member of Ubuntu
Backporters, which is subscribed to lucid-backports.
Bug Watch Updater
2010-09-15 19:42:49 UTC
Permalink
** Changed in: vino
Status: Incomplete => Fix Released

** Changed in: vino
Importance: Unknown => Wishlist
--
Compiz / vnc screen refresh with nvidia-restricted driver/VirtualBox/ATI fglrx driver using X.org
https://bugs.launchpad.net/bugs/353126
You received this bug notification because you are a member of Ubuntu
Backporters, which is subscribed to lucid-backports.
KruyKaze
2010-10-22 03:15:40 UTC
Permalink
I am still experiencing this bug on Maverick 64bit
--
Compiz / vnc screen refresh with nvidia-restricted driver/VirtualBox/ATI fglrx driver using X.org
https://bugs.launchpad.net/bugs/353126
You received this bug notification because you are a member of Ubuntu
Backporters, which is subscribed to lucid-backports.
Josh
2010-10-22 03:46:21 UTC
Permalink
I don't understand how the most user friendly Linux distribution in the
world can have such a fundamental problem for *four years*.
--
Compiz / vnc screen refresh with nvidia-restricted driver/VirtualBox/ATI fglrx driver using X.org
https://bugs.launchpad.net/bugs/353126
You received this bug notification because you are a member of Ubuntu
Backporters, which is subscribed to lucid-backports.
KruyKaze
2010-10-22 03:58:18 UTC
Permalink
I think it's more like 2 years the problem is that it was working before and
then it broke.What I don't understand is that I know it's not uncommon to
use compiz and vnc at the same time.
Post by Josh
I don't understand how the most user friendly Linux distribution in the
world can have such a fundamental problem for *four years*.
--
Compiz / vnc screen refresh with nvidia-restricted driver/VirtualBox/ATI
fglrx driver using X.org
https://bugs.launchpad.net/bugs/353126
You received this bug notification because you are a direct subscriber
of the bug.
Status in AMD fglrx video driver: Confirmed
Status in Lucid Backports: Invalid
Status in NVIDIA Drivers Ubuntu: Fix Released
Status in GNOME Remote Desktop: Fix Released
Status in X.Org X server: Fix Released
Status in ?vino? package in Ubuntu: Fix Released
Status in ?xorg-server? package in Ubuntu: Fix Released
Status in ?vino? package in Fedora: Unknown
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/245for details). Linked bugs confirm this is not an issue on intel chipsets or
nv driver.
Enable desktop-effects (default) with nvidia-restricted, virtualBox's
display or some ATI driver like RV610
Enable remote desktop
Connect with VNC
You see a screen snapshot of your desktop but if you click a menu item
there are no updates to the screen.
If you close and restart the vnc session, you get an updated snapshot but
still no refreshes.
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).
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 .
https://bugs.launchpad.net/fglrx/+bug/353126/+subscribe
--
Compiz / vnc screen refresh with nvidia-restricted driver/VirtualBox/ATI fglrx driver using X.org
https://bugs.launchpad.net/bugs/353126
You received this bug notification because you are a member of Ubuntu
Backporters, which is subscribed to lucid-backports.
Rocko
2010-10-22 04:42:21 UTC
Permalink
The open-source ATI driver doesn't have this problem; it's only a
problem with the proprietary ATI driver, so it's a problem that the
Ubuntu developers cannot solve (and the same goes for the X developers).

It might therefore be worth raising the bug directly with AMD if you are
experiencing it. It only took nvidia a few days to release a fixed
driver when I logged the bug on their forums.
--
Compiz / vnc screen refresh with nvidia-restricted driver/VirtualBox/ATI fglrx driver using X.org
https://bugs.launchpad.net/bugs/353126
You received this bug notification because you are a member of Ubuntu
Backporters, which is subscribed to lucid-backports.
KruyKaze
2010-10-22 06:24:06 UTC
Permalink
My apologies, I found out i was not using the "current" NVIDIA driver.It is
working fine now :)
Post by Rocko
The open-source ATI driver doesn't have this problem; it's only a
problem with the proprietary ATI driver, so it's a problem that the
Ubuntu developers cannot solve (and the same goes for the X developers).
It might therefore be worth raising the bug directly with AMD if you are
experiencing it. It only took nvidia a few days to release a fixed
driver when I logged the bug on their forums.
--
Compiz / vnc screen refresh with nvidia-restricted driver/VirtualBox/ATI
fglrx driver using X.org
https://bugs.launchpad.net/bugs/353126
You received this bug notification because you are a direct subscriber
of the bug.
Status in AMD fglrx video driver: Confirmed
Status in Lucid Backports: Invalid
Status in NVIDIA Drivers Ubuntu: Fix Released
Status in GNOME Remote Desktop: Fix Released
Status in X.Org X server: Fix Released
Status in ?vino? package in Ubuntu: Fix Released
Status in ?xorg-server? package in Ubuntu: Fix Released
Status in ?vino? package in Fedora: Unknown
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/245for details). Linked bugs confirm this is not an issue on intel chipsets or
nv driver.
Enable desktop-effects (default) with nvidia-restricted, virtualBox's
display or some ATI driver like RV610
Enable remote desktop
Connect with VNC
You see a screen snapshot of your desktop but if you click a menu item
there are no updates to the screen.
If you close and restart the vnc session, you get an updated snapshot but
still no refreshes.
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).
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 .
https://bugs.launchpad.net/fglrx/+bug/353126/+subscribe
--
Compiz / vnc screen refresh with nvidia-restricted driver/VirtualBox/ATI fglrx driver using X.org
https://bugs.launchpad.net/bugs/353126
You received this bug notification because you are a member of Ubuntu
Backporters, which is subscribed to lucid-backports.
Bug Watch Updater
2011-01-25 13:47:11 UTC
Permalink
** Changed in: xorg-server
Importance: High => Unknown
--
You received this bug notification because you are a member of Ubuntu
Backporters, which is subscribed to lucid-backports.
https://bugs.launchpad.net/bugs/353126

Title:
Compiz / vnc screen refresh with nvidia-restricted
driver/VirtualBox/ATI fglrx driver using X.org
Bug Watch Updater
2011-02-05 15:03:24 UTC
Permalink
** Changed in: xorg-server
Importance: Unknown => High
--
You received this bug notification because you are a member of Ubuntu
Backporters, which is subscribed to lucid-backports.
https://bugs.launchpad.net/bugs/353126

Title:
Compiz / vnc screen refresh with nvidia-restricted
driver/VirtualBox/ATI fglrx driver using X.org
Matt Marnell
2011-02-15 18:16:26 UTC
Permalink
I can confirm this is still an issue with Ubuntu 10.10 x64 and ATI/AMD
Proprietary FGLRX graphics drivers installed.

Linux brutus 2.6.35-25-generic #44-Ubuntu SMP Fri Jan 21 17:40:44 UTC
2011 x86_64 GNU/Linux

With Visual Effects enabled, I get no client-side visual refresh from
VNC (using ubuntu's built-in vino server) although commands are being
processed. With Visual Effects set to None, it seems to work fine.
--
You received this bug notification because you are a member of Ubuntu
Backporters, which is subscribed to lucid-backports.
https://bugs.launchpad.net/bugs/353126

Title:
Compiz / vnc screen refresh with nvidia-restricted
driver/VirtualBox/ATI fglrx driver using X.org
rambamram
2011-03-22 21:03:50 UTC
Permalink
I can confirm that I'm also having this issue on 10.10 x32 with nVidia
drivers.

Was having this issue with 10.04 as well.

yes with Visual effects disabled you can get Client side info but with
visual effects enabled it does not automatically disable when someone
connects.

If you setup a vncserver :1 and higher the issue does not present
itself...it only affects the main Desktop vncserver :0

in earlier versions there was a built in visual effects auto disable
when VNC connected to the main desktop...but not since 9.14.
--
You received this bug notification because you are a member of Ubuntu
Backporters, which is subscribed to lucid-backports.
https://bugs.launchpad.net/bugs/353126

Title:
Compiz / vnc screen refresh with nvidia-restricted
driver/VirtualBox/ATI fglrx driver using X.org
djdvant
2011-04-30 01:00:16 UTC
Permalink
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
--
You received this bug notification because you are a member of Ubuntu
Backporters, which is subscribed to lucid-backports.
https://bugs.launchpad.net/bugs/353126

Title:
Compiz / vnc screen refresh with nvidia-restricted
driver/VirtualBox/ATI fglrx driver using X.org
Josh
2011-04-30 01:28:40 UTC
Permalink
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.
--
You received this bug notification because you are a member of Ubuntu
Backporters, which is subscribed to lucid-backports.
https://bugs.launchpad.net/bugs/353126

Title:
Compiz / vnc screen refresh with nvidia-restricted
driver/VirtualBox/ATI fglrx driver using X.org
Thorsten Giesecke
2011-05-27 05:51:36 UTC
Permalink
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
--
You received this bug notification because you are a member of Ubuntu
Backporters, which is subscribed to lucid-backports.
https://bugs.launchpad.net/bugs/353126

Title:
Compiz / vnc screen refresh with nvidia-restricted
driver/VirtualBox/ATI fglrx driver using X.org
Bryce Nesbitt
2011-06-13 21:19:28 UTC
Permalink
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.
--
You received this bug notification because you are a member of Ubuntu
Backporters, which is subscribed to lucid-backports.
https://bugs.launchpad.net/bugs/353126

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/fglrx/+bug/353126/+subscriptions
Josh
2011-06-14 02:05:22 UTC
Permalink
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.
--
You received this bug notification because you are a member of Ubuntu
Backporters, which is subscribed to lucid-backports.
https://bugs.launchpad.net/bugs/353126

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/fglrx/+bug/353126/+subscriptions
Greg Michalec
2011-09-04 00:19:01 UTC
Permalink
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).
--
You received this bug notification because you are a member of Ubuntu
Backporters, which is subscribed to lucid-backports.
https://bugs.launchpad.net/bugs/353126

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/fglrx/+bug/353126/+subscriptions
Bryce Harrington
2011-10-07 00:57:58 UTC
Permalink
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
--
You received this bug notification because you are a member of Ubuntu
Backporters, which is subscribed to lucid-backports.
https://bugs.launchpad.net/bugs/353126

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/fglrx/+bug/353126/+subscriptions
MestreLion
2012-02-08 15:43:25 UTC
Permalink
** Also affects: maverick-backports
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Backporters, which is subscribed to lucid-backports.
https://bugs.launchpad.net/bugs/353126

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/fglrx/+bug/353126/+subscriptions
Evan Broder
2012-05-10 21:59:29 UTC
Permalink
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
--
You received this bug notification because you are a member of Ubuntu
Backporters, which is subscribed to lucid-backports.
https://bugs.launchpad.net/bugs/353126

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/fglrx/+bug/353126/+subscriptions
Josh
2012-12-08 04:42:41 UTC
Permalink
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.
--
You received this bug notification because you are a member of Ubuntu
Backporters, which is subscribed to lucid-backports.
https://bugs.launchpad.net/bugs/353126

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/fglrx/+bug/353126/+subscriptions
MestreLion
2013-09-06 11:00:49 UTC
Permalink
@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.
--
You received this bug notification because you are a member of Ubuntu
Backporters, which is subscribed to Lucid Backports.
https://bugs.launchpad.net/bugs/353126

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/fglrx/+bug/353126/+subscriptions
Bug Watch Updater
2017-10-27 03:59:50 UTC
Permalink
Launchpad has imported 29 comments from the remote bug at
https://bugzilla.redhat.com/show_bug.cgi?id=214446.

If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
https://help.launchpad.net/InterBugTracking.

------------------------------------------------------------------------
On 2006-11-07T17:53:46+00:00 Travis 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.

Reply at: https://bugs.launchpad.net/ubuntu/+source/xorg-
server/+bug/353126/comments/0

------------------------------------------------------------------------
On 2006-11-07T17:56:06+00:00 Travis wrote:

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

Reply at: https://bugs.launchpad.net/ubuntu/+source/xorg-
server/+bug/353126/comments/1

------------------------------------------------------------------------
On 2006-11-08T10:22:26+00:00 Adam wrote:

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

Reply at: https://bugs.launchpad.net/ubuntu/+source/xorg-
server/+bug/353126/comments/2

------------------------------------------------------------------------
On 2006-11-08T12:35:17+00:00 Travis wrote:

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

Reply at: https://bugs.launchpad.net/ubuntu/+source/xorg-
server/+bug/353126/comments/3

------------------------------------------------------------------------
On 2006-11-20T16:31:08+00:00 Victor 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.

Reply at: https://bugs.launchpad.net/ubuntu/+source/xorg-
server/+bug/353126/comments/4

------------------------------------------------------------------------
On 2006-12-05T13:43:21+00:00 Adam wrote:

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

Reply at: https://bugs.launchpad.net/ubuntu/+source/xorg-
server/+bug/353126/comments/5

------------------------------------------------------------------------
On 2006-12-05T16:31:54+00:00 Travis wrote:

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


Reply at: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/353126/comments/6

------------------------------------------------------------------------
On 2007-01-18T16:37:18+00:00 Adam wrote:

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

Reply at: https://bugs.launchpad.net/ubuntu/+source/xorg-
server/+bug/353126/comments/7

------------------------------------------------------------------------
On 2007-08-17T15:29:49+00:00 Didier 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)


Reply at: https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/353126/comments/8

------------------------------------------------------------------------
On 2007-09-03T10:10:53+00:00 Tomasz wrote:

This bug is a duplicate of
https://bugzilla.redhat.com/show_bug.cgi?id=208983

Reply at: https://bugs.launchpad.net/ubuntu/+source/xorg-
server/+bug/353126/comments/12

------------------------------------------------------------------------
On 2007-11-04T01:19:33+00:00 Aaron 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?

Reply at: https://bugs.launchpad.net/ubuntu/+source/xorg-
server/+bug/353126/comments/13

------------------------------------------------------------------------
On 2008-04-04T04:30:04+00:00 Bug 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

Reply at: https://bugs.launchpad.net/ubuntu/+source/xorg-
server/+bug/353126/comments/14

------------------------------------------------------------------------
On 2008-05-06T16:44:11+00:00 Bug 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.

Reply at: https://bugs.launchpad.net/ubuntu/+source/xorg-
server/+bug/353126/comments/15

------------------------------------------------------------------------
On 2009-09-30T09:06:05+00:00 Emmanuel 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 ?

Reply at: https://bugs.launchpad.net/ubuntu/+source/xorg-
server/+bug/353126/comments/172

------------------------------------------------------------------------
On 2009-11-20T04:58:10+00:00 BrianK 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.

Reply at: https://bugs.launchpad.net/ubuntu/+source/xorg-
server/+bug/353126/comments/197

------------------------------------------------------------------------
On 2009-12-21T23:41:26+00:00 Chris 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.

Reply at: https://bugs.launchpad.net/ubuntu/+source/xorg-
server/+bug/353126/comments/201

------------------------------------------------------------------------
On 2010-02-22T00:06:27+00:00 Walter wrote:

I confirm this bug in FC12.

Reply at: https://bugs.launchpad.net/ubuntu/+source/xorg-
server/+bug/353126/comments/217

------------------------------------------------------------------------
On 2010-04-25T17:42:20+00:00 txvs 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.

Reply at: https://bugs.launchpad.net/ubuntu/+source/xorg-
server/+bug/353126/comments/267

------------------------------------------------------------------------
On 2010-04-27T22:37:10+00:00 A 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

Reply at: https://bugs.launchpad.net/ubuntu/+source/xorg-
server/+bug/353126/comments/277

------------------------------------------------------------------------
On 2010-05-08T01:34:29+00:00 John 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

Reply at: https://bugs.launchpad.net/ubuntu/+source/xorg-
server/+bug/353126/comments/291

------------------------------------------------------------------------
On 2010-05-08T01:37:15+00:00 John wrote:

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

-John

Reply at: https://bugs.launchpad.net/ubuntu/+source/xorg-
server/+bug/353126/comments/292

------------------------------------------------------------------------
On 2010-05-22T13:50:25+00:00 Sandro 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.

Reply at: https://bugs.launchpad.net/ubuntu/+source/xorg-
server/+bug/353126/comments/295

------------------------------------------------------------------------
On 2010-06-30T15:59:01+00:00 Michael wrote:

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

Reply at: https://bugs.launchpad.net/ubuntu/+source/xorg-
server/+bug/353126/comments/323

------------------------------------------------------------------------
On 2010-06-30T16:00:33+00:00 Michael wrote:

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

Reply at: https://bugs.launchpad.net/ubuntu/+source/xorg-
server/+bug/353126/comments/324

------------------------------------------------------------------------
On 2010-11-04T12:14:34+00:00 Bug 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

Reply at: https://bugs.launchpad.net/ubuntu/+source/xorg-
server/+bug/353126/comments/340

------------------------------------------------------------------------
On 2010-11-05T13:36:38+00:00 John wrote:

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

Reply at: https://bugs.launchpad.net/ubuntu/+source/xorg-
server/+bug/353126/comments/341

------------------------------------------------------------------------
On 2010-11-05T13:48:41+00:00 Michael 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.

Reply at: https://bugs.launchpad.net/ubuntu/+source/xorg-
server/+bug/353126/comments/342

------------------------------------------------------------------------
On 2010-11-05T13:53:22+00:00 John wrote:

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

-John

Reply at: https://bugs.launchpad.net/ubuntu/+source/xorg-
server/+bug/353126/comments/343

------------------------------------------------------------------------
On 2011-05-13T19:40:53+00:00 Michael wrote:

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

Reply at: https://bugs.launchpad.net/ubuntu/+source/xorg-
server/+bug/353126/comments/348


** Changed in: vino (Fedora)
Status: Unknown => Invalid

** Changed in: vino (Fedora)
Importance: Unknown => High

** Bug watch added: Red Hat Bugzilla #208983
https://bugzilla.redhat.com/show_bug.cgi?id=208983
--
You received this bug notification because you are a member of Ubuntu
Backporters, which is subscribed to Lucid Backports.
https://bugs.launchpad.net/bugs/353126

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/fglrx/+bug/353126/+subscriptions
--
ubuntu-backports mailing list
ubuntu-***@lists.ubuntu.com
Modify settings or unsubscribe at: https://lists.ubuntu.com
Olleg Samoylov
2018-01-19 12:54:20 UTC
Permalink
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.
--
You received this bug notification because you are a member of Ubuntu
Backporters, which is subscribed to Lucid Backports.
https://bugs.launchpad.net/bugs/353126

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

To manage notifications about this bug go to:
https://bugs.launchpad.net/fglrx/+bug/353126/+subscriptions
--
ubuntu-backports mailing list
ubuntu-***@lists.ubuntu.com
Modify settings or unsubscribe at: https://lists.ubuntu.com/mailman/listinfo/
Loading...