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

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.

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

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

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

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

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

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

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.

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

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.

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

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

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.

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

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.

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.

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.

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.

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.

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

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

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

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?

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

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.

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,

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 .

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.

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.

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)

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.

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

I installed x11vnc and use this command in the terminal:

x11vnc --noxdamage --passwd XXX -forever

as a work-around until vino is fixed.

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

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.

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

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

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

Is the x11vnc bug confirmed? Any more data on that?

I feel guilty that I love eye candy this much (I never thought I'd say this...), but I'd REALLY like to keep using Compiz, haha!

Maybe one of the more experienced nixers could come up with a script to disable Compiz only when a VNC connection is established, and re-enable it upon termination?

Also, has anyone tried switching from the nvidia v180 driver to the v173 driver? I'm not able to try it atm, and there is speculation this is nvidia independent, but maybe it's worth a shot.

Just wanted to add another "me too"...

I've upgraded to Jaunty with VNC problems too. Tried ShipiboConibo's suggestion to go with v173 NVIDIA drivers. Same issue. To connect to Jaunty, I'm using a Mac JollysFastVNC + Screen Sharing. The X11VNC workaround appears to work for now, but it's a pain in the butt since it's mega slow.

And of course, I decided to go all the way down to the v96 NVIDIA drivers too. Same issue, doesn't work.

1 step forward, 2 steps back...

Also seeing on fglrx driver:
(II) Module fglrx: vendor="FireGL - ATI Technologies Inc."
        compiled for 1.4.99.906, module version = 8.60.40
        Module class: X.Org Video Driver
(--) fglrx(0): Chipset: "ATI Radeon HD 3600 Series" (Chipset = 0x9598)

x11vnc seems to work fine.

> The X11VNC workaround appears to work for now,
> but it's a pain in the butt since it's mega slow.

You need to supply the "-noxdamage" to x11vnc's cmdline.

XDAMAGE is broken under compiz and the "-noxdamage" option tells x11vnc to not use it; this avoids the problem of no/slow screen updates.

Hi, folks.

I've uploaded a vino package in my PPA (https://launchpad.net/~wendell/+archive/ppa) which adds a gconf option: disable_xdamage.

After install the package, go to gconf-editor and change the key "/desktop/gnome/remote_access/disable_xdamage" to true. Then enable vino at System->Preferences->Remote Desktop.

Tell me if it works for you so that I can apply that patch on vino upstream.

Thanks.

If this fix works, I think you should also do that this key could be easily changed without using gconf-editor...Maybe in the "Remote Desktop" menu, put a choice with "Disable XDAMAGE - Use this if it doesn't work with compiz"

Can't this be checked automatically whether xdamage is supported or not?

This doesn't seem to improve things for me:
dpkg -s vino:
Package: vino
Status: install ok installed
Architecture: amd64
Version: 2.26.1-0ubuntu2

gconftool-2 -g /desktop/gnome/remote_access/disable_xdamage
true

killall vino-server

Still get no updates on vncviewer. Maybe user error ?

Hi!

I've also tried the patched package, but it did not work. I completely removed the original vino and installed the patched package. After changing the gconf-setting I activated the server again and tried it. After connecting the screen still does not refresh after changes.
I also tried to set disable_xdamage to false but the result was the same.

Maybe the gconf-value is not read properly?

Thank you very much!

Stupid me. I forgot to actually use the new conf while starting the server.

Just uploaded a new version (-ubuntu3). Please test it.

Thanks.

Hello!

I tried it again but nothing changed.. I'm sorry.

I saw in the diff file that there should appear a debug message when xdamage is turned off.
 + if (vfb->priv->disable_xdamage)
-+ return;
++ {
++ dprintf (POLLING, "Not using XDamage extension, as requested via gconf key\n");
++ return;
++ }
 +

But I cannot see this message. This is what is in my ~/.xsession-errors when I start vino and open a connection:
http://nopaste.info/1b85475786.html

Any further ideas?
Thank you!

Try the -ubuntu4 version please. (just uploaded)

Hi!

It works!! Thank you very much!
I installed the package, activated vino again, connected and I could see the changes!
When I set disable_xdamage to false, I won't see any changes over VNC. What a surprise. ;)

Thank you!!

Confirmed - -ubuntu4 w/ disable_xdamage set to true gets me an properly updated desktop as well. Thanks!

It works for me too with the proprietary nvidia drivers (TwinView with 2 monitors). Thanks guy :-)

I found a different workaround. I had this installed on my HTPC and can only connect via SSH and VNC so I gave it this command

"sudo apt-get remove --purge compiz-core desktop-effects"

to remove compiz and desktop effects and then

"sudo /etc/init.d/gdm restart"

to restart the x server.

Fixed the problem...

Should this be marked "Fix Released"? There is workaround, but it requires using the slower noxdamage. It does not fix the regression. If this is accepted as a fix, would it be okay to file a new bug about the need to use "-noxdamage" in VNC, when I didn't used to have to?

I don't think this should be marked as fix released at all, the work around detailed is not suitable for me using a wireless connection. VNC worked fine before Jaunty with desktop effects without using -noxdamage is just a temporary work around for some people, hardly a fix.

$ dpkg -l |grep vino
ii vino 2.26.1-0ubuntu4 VNC server for GNOME

$ gconftool-2 -g /desktop/gnome/remote_access/disable_xdamage
true

i am able to reproduce the bug using this version.

the machine is running fglrx. i've restarted vino-server several times; the process id has changed each time indicating that i am not speaking to an old vino-server process. do i need to restart the X server?

I don't think this should be marked as fix either. Doesn't this suit better under the 'Workarounds' section in the description? I doubt -noxdamage is the intended way to run a VNC server in the future.

i had a chance to visit the machine in person today, and the fix in -ubuntu4 worked for me after i had rebooted the machine. it seems that something besides vino-server must be restarted for the fix to take effect.

thank you for your attention to this problem. i hope that this package can be accepted into ubuntu before the next release cycle.

Thanks for the workaround, but I agree this is not a fix, but rather a good workaround. This problem should definitely not be marked as fixed, but it sure is nice to have a working workaround

Thank you very much!!!
1. gconf-editor
2. /desktop/gnome/remote_access/disable_xdamage ----> true
3. sudo /etc/init.d/gdm restart
4. ???????
5. PROFIT

I agree that fix released should be dropped. It's not a whole lot better than just releasing a fix that says "don't use VNC".

The bug still seems to be marked as fix released any word on this, as the suggested fix is not suitable for myself and no doubt other affected users.

As I understand it from the status page, only the vino task is marked Fix
released, which is simply a workaround in vino.
The status for compiz and xorg server (where the root of the problem
actually lies) are both marked as "confirmed", so these issues are still
open.

From the comments on the upstream freedesktop bug, it appears the issue has
been fixed in the latest development versions of the drivers/xorg:
https://bugs.freedesktop.org/show_bug.cgi?id=12255

When these will appear in ubuntu though is what we are interested in of
course.

On Fri, May 22, 2009 at 4:53 AM, tonyhartfield
<email address hidden>wrote:

> The bug still seems to be marked as fix released any word on this, as
> the suggested fix is not suitable for myself and no doubt other affected
> users.
>
> --
> Compiz / vnc screen refresh with nvidia-restricted driver/VirtualBox/ATI
> fglrx driver
> https://bugs.launchpad.net/bugs/353126
> You received this bug notification because you are a direct subscriber
> of the bug.
>

I can confirm this bug, but it also happens with ATI-restricted drivers and compiz.

Judging from the suggested workaround, I wouldn't at all be surprised, if this was caused by this:
http://lists.freedesktop.org/archives/compiz/2008-May/003125.html

I'm also hit by this bug. This is a really annoying one -- i had a working 8.10 system, upgraded to 9.04, now it's broken!

is any proper solution approaching?

Problem still not solved!?

Sorry, it's with the newest version of Vino from Jonh Wendell has solved my problem thx.

I'm adding a "I can't live on like this" - I have all the problems you guys have, but disabling compiz is not a choice, I use "Elegant Brit" and use a lot exposé. I do use the machine for actual work... well long story short, this situation is unacceptable for me. I cannot use remote desktop from my usual remote spots that have slow wifi. For me, this is actually outrageous. In retrospect, I understand that I should have not updated to jaunty, but there is little chance of knowing that the next-best-version is actually totally flawed. I mean, is there actually a way for somebody that would like to use the newest version of ubuntu to know these problems?

Please, try to release a real fix as soon as possible! And oh boy you should know what I think of these "workarounds"...

While waiting for a true fix, I ended up installing NoMachine's NX server which works great.

While waiting for a fix, using x11vnc will be fine. I hope a fix for Jaunty comes soon. It would be awful to have to wait till 9.10 for this regression to be fixed.

I wouldn't get my hopes up. With the exception of security vulnerabilities I can't think of a time when a bug I've been watching has been fixed between Ubuntu releases.

that's sad.
can anyone help me with setting up an alternative vnc server?

> can anyone help me with setting up an alternative vnc server?

$ sudo apt-get install x11vnc
$ x11vnc

:)

Wow, I didn't know it was that much complicated :)
It's significantly slower for me than vino, but it's better than moving the
cursor blind. Thanks.

-- Amr

Can't I just downgrade a certain package to get a version where this is still working?

Is this problem only when you upgrade to 9.04 from a previous version?

It has nothing to do with upgrading. It's a problem where damage
isn't getting picked up. It's a problem in the package. Clean
install or not. I don't think refreshing the entire screen is a
sufficient workaround either for the most part. It's bad enough that
you can't set compression options in either the Ubuntu server
interface or in the client, but now you can't use the VNC server
without refreshing the entire image everytime? That's murder for
lower bandwidth use. I feel like getting on the suggested features
forum/launchpad whatever and suggesting that Ubuntu come out of the
box with some type of workable remote desktop type solution. Windows
provides remote desktop out of box on Windows XP, Ubuntu should have a
workable alternative. (And it should not require setting up of SSH
tunnels manually either if you want to make it open on a network,
because currently VNC is unencrypted and unsafe for network use except
behind SSH).

On Tue, Jun 2, 2009 at 7:27 PM, no-use <email address hidden> wrote:
> Can't I just downgrade a certain package to get a version where this is
> still working?
>
> Is this problem only when you upgrade to 9.04 from a previous version?
>
> --
> Compiz / vnc screen refresh with nvidia-restricted driver/VirtualBox/ATI fglrx driver
> https://bugs.launchpad.net/bugs/353126
> You received this bug notification because you are a direct subscriber
> of the bug.
>
> Status in GNOME Remote Desktop: Fix Released
> 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 .
>

Definitely a regression. I used Remote Desktop with Ubuntu 8.10, 8.04, and 7.10 and UltraVNC client on Windows without issue.

Confirmed - Clean install of 9.04 - VNC client shows initial screen but no updates. Clicking Refresh button in client doesn't refresh the screen.

Confirmed - I am using NVIDIA restricted driver and "Extra" visual effects.

Confirmed - setting visual effects to "None" restores display updates to VNC client.

Interesting behavior - With visual effects set to "Extra", I was watching both computers. The VNC client was able to control the Ubuntu 9.04 desktop correctly, but the screen updates weren't being updated in the VNC client. The VNC server appears to work correctly except for the screen updates w/ compiz enabled.

today i tested it with a fresh installation of Ubuntu Karmic Koala 9.10
Alpha 2. the screen still does not refresh while compiz is enabled.

On Sat, Jun 13, 2009 at 7:29 AM, Andrew <email address hidden> wrote:

> Definitely a regression. I used Remote Desktop with Ubuntu 8.10, 8.04,
> and 7.10 and UltraVNC client on Windows without issue.
>
> Confirmed - Clean install of 9.04 - VNC client shows initial screen but
> no updates. Clicking Refresh button in client doesn't refresh the
> screen.
>
> Confirmed - I am using NVIDIA restricted driver and "Extra" visual
> effects.
>
> Confirmed - setting visual effects to "None" restores display updates to
> VNC client.
>
> Interesting behavior - With visual effects set to "Extra", I was
> watching both computers. The VNC client was able to control the Ubuntu
> 9.04 desktop correctly, but the screen updates weren't being updated in
> the VNC client. The VNC server appears to work correctly except for the
> screen updates w/ compiz enabled.
>
> --
> Compiz / vnc screen refresh with nvidia-restricted driver/VirtualBox/ATI
> fglrx driver
> https://bugs.launchpad.net/bugs/353126
> You received this bug notification because you are a direct subscriber
> of the bug.
>
> Status in GNOME Remote Desktop: Fix Released
> 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 .
>

Just wanted to add another instance of this issue. I like to remotely access my desktop, which I use as a desktop, from my laptop. I don't want a hack where compiz is disabled which vnc connections is made. I used intrepid fine remotely with desktop effects still enabled, even over my narrow 256kbs upload. Since this worked fine in Intrepid, please fix it for Jaunty (and Karmic).

Thanks,

Alex

I can confirm/reproduce this bug on a fresh and up-to-date install of Ubuntu 9.04 running compiz and the nvidia restricted driver.

Awaiting a fix ++;

I'm also facing the same issue since I have upgraded to Jaunty Jackalope. Even if I select the old NVidia Driver (version 96) the VNC client screen doesn't update eigther. VNC only works propperly after disabling visual effects.

Is this any closer to being fixed? Or, is there a way for a normal person that doesn't know about digging thru config files to get this to work, or revert back to a previous working version?

Use FreeNX (http://freenx.berlios.de/). IMO it's much better than VNC
anyway, it automatically sets your screen res, and works with compiz, of
course.

Rolo.

On Mon, Jun 22, 2009 at 7:44 PM, edub <email address hidden> wrote:

> Is this any closer to being fixed? Or, is there a way for a normal
> person that doesn't know about digging thru config files to get this to
> work, or revert back to a previous working version?
>
> --
> Compiz / vnc screen refresh with nvidia-restricted driver/VirtualBox/ATI
> fglrx driver
> https://bugs.launchpad.net/bugs/353126
> You received this bug notification because you are a direct subscriber
> of a duplicate bug.
>
> Status in GNOME Remote Desktop: Fix Released
> 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 .
>

FreeNX is not a solution. It is not in the repositories and is not a default installation item. It also will not connect me to an existing session.

Still awaiting a fix to this. Why has there been no research into why this broke between 8.10 and 9.04?

I'm using x11vnc as an alternative. The performance isn't great but it
works.

Thanks to Rolo for the earlier FreeNX suggestion as a work around, I can't
believe how much better it is than VNC, amazingly smooth and responsive even
over wifi.

Using x11vnc is more or less the same as using the noxdamage flag in the patched version provided by John Wendell. Is FreeNX really an alternative? Can it see the desktop like it was, or does it start a completely new session?

I am using Ubuntu Jaunty 9.04 and noticing this problem.

So far, the easiest fix I found was to run metacity --replace on the server machine.
This kills the compiz window manager and replaces it with metacity which enables vnc clients to run fine.

I am able to notice the changes at runtime, so changing window manager updates the clients as soons as the command is run.

I hope this helps anyone with this problem.

-Changing window managers *does not* fix this bug, it is a workaround.
-Running FreeNX *does not* fix this bug, it is a workaround.
-Using x11vnc with -noxdamage *does not* fix this bug, it is a workaround.

A fixed bug would mean that I log into a machine via vnc and it simply works without any sort of modification.

Has anyone tried using the version of compiz that used to work with the version of everything else that doesn't work? Basically intrepid's compiz with jaunty everything else. Pretty sure there is nothing compiz can do here so that would still not work.

Also, does this happen if you enable metacity compositing or kwin compositing? The post on the compiz mailing list describes how compiz has always worked, not some recent change. It's the way that all compositors work.

I agree with Chris Balcum, so far everything submitted to date with this bug has been a workaround. and changing the window manager from compiz to metacity makes no sense as a workaround, because if you didn't want to run compiz you wouldn't be effected by the bug in the first place, and I like compiz, I just want it to work correctly with VNC

I have used 4 of my 5 Linux computers with VNC, nvidia-restricted, and Compiz since Feisty without a single hiccup.

This is a regression to when I used Edgy, Compiz/Beryl and Intel 810 graphics (that's almost 3 YEARS!) Back then the solution to everything was 'disable Compiz.'

My ENTIRE NETWORK as well as my ability to assist friends/family remotely (VNC over SSH --the workarounds are useless here) is affected by this bug.

I use the Compiz cube, not for eye-candy but because I'm more productive with an application on each workspace - roll the mouse wheel, I'm where I want to be. Linux has affected my way of computing - for the better- this bug has disabled much of what I have come to expect for the last 3 years.

 Three months is too long to wait for a genuine fix for something that worked for so long. This is a serious regression, it breaks some of the very things that set Linux apart and that make it more useful than what we used to suffer with.

Please consider the following:
1. VNC with Compiz enabled worked prior to Jaunty using nvidia-restricted v. 173, v.177, & v. 180 (and apparently with the other graphics drivers listed in the title.)

2. VNC with Compiz enabled DOES NOT work in Jaunty with nvidia-restricted v.173, v.177, v.180 or the other drivers listed above (which previously worked.)

3. The bug doesn't manifest itself without proprietary drivers.

We can draw the conclusion from this that the bug manifests itself with proprietery drivers, but the fault of the sudden change in usability does not lie with the video drivers, right?

If that is the case, can we re-word the title and description of this bug to reflect that the problem (the change in usability) lies with the interaction of Compiz/ Vino and/or X.Org ??

This bug may receive more attention if it didn't look like another problem which could only be fixed by an update in proprietary software.

I agree with J N B. Since everything was working with the restricted driver before, I think more focus need to be put into whatever changed in Compiz and X.org between the versions.

No one has answered my questions and I'm pretty sure there is nothing in compiz that changed that could possibly have an effect on this. It's going to be an nvidia<->xorg thing for sure.

Has anyone tried using the previous 8.10 or 8.04 distros and then manually updating Nvidia, Compiz, and other components that are suspect one at a time? Seems to me that would be the logical place to start and help identify what exactly isn't working; update an application, test VNC, then continue for each known update. It would also provide a workaround with a simple rollback or downgrade a particular component once it's isolated.

Forget my suggestion. I took a leap and just removed ALL Compiz components from the package manager and rebooted. Works fine now. So it appears that it's not some crazy kernel update like I suspected, or anything with Nvidia. So the simple solution, the 'actual' workaround until Compiz gets their crap together is just go into the Package Manager, run a query for Compiz, and do a "Mark for complete removal" on all 8 or so components of compiz. Reboot, and VNC works fine. A relatively easy workaround for now.

Travis:

Sorry I overlooked your questions. It does work with Metacity compositing enabled. I haven't had a chance to install an older version of Compiz yet to see if that works. I was inclined to agree with your nvidia<->xorg hypothesis, but I hope the changes in Compiz from 0.7.8(Intrepid) to 0.8.2(Jaunty) are taken into consideration as well.

Folks,

Sorry for the multiple posts, I've been posting as I go.

Seems I was slightly off course in blaming solely Compiz for this issue. I installed some older versions of it and had the exact same issue with two different versions (9.04 has 1:0.8.2-0ubuntu8, whereas a fresh install of 8.10 has 0.7.8-0ubuntu4.1....thanks VMware Fusion). So I went after the next likely offender...Nvidia. It seems that whatever is new in Nvidia's software is not playing nice with any version of Compiz, newer or otherwise. So yes, removing Compiz fixes the VNC...the problem is all of your windows open half off the screen in the top left, I'm assuming some goofy default x/y coord setting somewhere that I don't have the patience to find. So here's a different workaround.

I went into Package Manager again and ripped out anything that even hinted it belonged to Nvidia. Then I ran an update to put the newest Compiz back on, since that wasn't the main offender anyways. Now the windows open normally again, and whats more is VNC works great! I've proven this by making these system changes from my Macbook pro, while simultaneously watching the screens on my Windows 7 and Windows XP laptops. All 3 worked nice with VNC, as expected.

There's a bit of a downside to my workaround. My resolution isn't ideal. I'm rocking the 800x600 (It's hosted on a 15" HP Pavilion widescreen), so it's not uber great, but it's usable.

For those of you interested, I found a quite useful server hosting all the old versions of Compiz and Compiz related goodies, and in .deb packages no less. You can find it here:

https://mirror.umoss.org/ubuntu/pool/main/c/compiz/

It has a security cert, so your browser may freak out. I know FF on ubuntu did, but you just have to allow the cert, no biggie.
I'm still hunting down the previous versions of the Nvidia stuff, and I'm going to try and isolate what exactly Compiz doesn't like, since ripping out ALL of the Nvidia components is somewhat drastic.

If anyone makes any more headway in the meantime, please for goodness sakes post it, sitting for hours hunting this stuff down gives me a headache.

But at least we now have a workaround!

I feel confident Travis Watkins is right sending it the xorg-server direction. I look forward to seeing it resolved

jjericho,

Although I appreciate your tests performed, they show nothing more than the workaround that has been around for quite some time, namely, disable compiz. You were saying that you believe it was something nvidia changed in their new drivers, I have to disagree with reference to J N B's and my own experimental findings where the same drivers worked in 8.10. It is thus more likely that this is caused by an x.org issue as the discussions between J N B and Travis indicates.

XCan,

You are correct that disabling compiz was my original suggestion. However, as I mentioned before, I've narrowed the issue down to either xorg or Nvidia, and the more I mess with it, it's seeming to be nvidia. Compiz is fully installed on my system. After removing all nvidia referencing packages, VNC works however my resolution was only 800x600. So after more troubleshooting today, I've confirmed on my own system that VNC now works with Compiz, in addition to having xserver-xorg-video-nv installed (1:2.1.12-1ubuntu5), in addition to some other nvidia modaliases. I simply manually selected a few packages to install in Package Manager, the xorg being the first one I tried. I now have a normal screen resolution, Compiz enabled, and VNC working. The only thing I cannot do at this point is enable Extra visual effects because of the packages that option installs. Other than not having some fancy features like window wobble...my system is fully functional now with VNC and the necessary packages. Hope this helps!

Sorry but I have to disagree. I have seen this bug with ATI drivers also, along with nVidia. I bet Intel drivers would do the same thing.

As long as compiz is running, VNC cannot work unless xdamage is disabled (x11vnc can do this). But that is not a solution, it's merely a workaround.

The problem lies either within compiz code or with xorg code.

I would like to add that I have also experienced this bug under ati drivers
this is not an nvidia issue at all.

Its extremely discouraging to see how little progress has been made with
this over the months. This is a major regression which affects me every day.

On Jul 12, 2009 6:53 PM, "Chris Balcum" <email address hidden> wrote:

Sorry but I have to disagree. I have seen this bug with ATI drivers
also, along with nVidia. I bet Intel drivers would do the same thing.

As long as compiz is running, VNC cannot work unless xdamage is disabled
(x11vnc can do this). But that is not a solution, it's merely a
workaround.

The problem lies either within compiz code or with xorg code.

-- Compiz / vnc screen refresh with nvidia-restricted driver/VirtualBox/ATI
fglrx driver https://b...

Apparently it's agreed by all of us that this bug is manifest using nvidia (and ATI, and virtualbox, ?others?) drivers. But the 'trigger' is a change in one of the packages added to Jaunty. Fixing the offending package will restore functionality.

I installed Compiz 0.7.8 (intrepid's package) and dependencies manually last night with no change in [lack of] functionality.

(Can someone else install an earlier version of Compiz in Jaunty to back me up? )

In the meantime, disable Compiz (visual effects) and use Metacity Compositing if you 'need' a compositing manager; or use the vino workaround from Jonh Wendell if you can spare the bandwidth. Both options will allow us to keep full resolution and use VNC, but we've still lost functionality.

Xorg devs..... we're anxious to see what you find. :)

To answer Travis Watkins's earlier questions:

In my experience:
1. VNC works using Metacity compositing.
2. Using Intrepid's Compiz with Jaunty's everything else still does not work.

(Those are my previous comments in a nutshell.)

When you use metacity composting you are not enabling any 'Extra'/additional visual effects. As others have already reported, this is the issue. Simply turning off additional visual effects isn't an answer or solution, it's a poor workaround. Vino seems to think that they have resolved the issue:
http://bugzilla.gnome.org/show_bug.cgi?id=533613
 Comment #3 from André Klapper (points: 30)
2009-05-13 11:25 UTC [reply]

This bug has also been fixed for 2.26.2:
http://git.gnome.org/cgit/vino/commit/?h=gnome-2-26&id=f5260a2ad0ad9f3b1c673f6a52a938abd2a58dbb

For jaunty:
$ apt-cache policy vino
vino:
  Installed: 2.26.1-0ubuntu1
  Candidate: 2.26.1-0ubuntu1
  Version table:
 *** 2.26.1-0ubuntu1 0
        100 /var/lib/dpkg/status

Has anyone tried vino 2.26.2 to see if that works?
https://launchpad.net/ubuntu/+source/vino
karmic development main release 2.26.2-1ubuntu1

freenx server is affected by the same bug. Seeing as nomachine nx server was reported working, I will try that. Seeing as thi bug is not present when runing freenx in arch, which has a newer Xorg, i guess this is already fixed upstream, and i hope a bugfix will come soon.

I think a posting very early in the thread suggested that a fix (Vino) was available in Debian, but not yet available in Ubuntu.  I haven't seen any other confirmation of this statement.  I also haven't seen anyone defnitively isolate the problem (Compiz, binary/free drivers, updated restricted drivers, X, Vino, etc.)

Manually installing packages at different versions is quite a bit a bit over my head.  Based on your post below, it seems like you are a good candidate for isolating the package / version where the regression occurred.

Are you able to restore 9.04's Compiz and try 8.10's Vino to see if it is a Vino regression?

________________________________
From: J N B <email address hidden>
To: <email address hidden>
Sent: Sunday, July 12, 2009 11:02:52 PM
Subject: [Bug 353126] Re: Compiz / vnc screen refresh with nvidia-restricted driver/VirtualBox/ATI fglrx driver

Apparently it's agreed by all of us that this bug is manifest using
nvidia (and ATI, and virtualbox, ?others?) drivers.  But the 'trigger'
is a change in one of the packages added to Jaunty.  Fixing the
offending package will restore functionality.

I installed Compiz 0.7.8 (intrepid's package) and dependencies manually
last night with no change in [lack of] functionality.

(Can someone else install an earlier version of Compiz in Jaunty to back
me up? )

In the meantime, disable Compiz (visual effects) and use Metacity
Compositing if you 'need' a compositing manager; or use the vino
workaround from Jonh Wendell if you can spare the bandwidth.  Both
options will allow us to keep full resolution and use VNC, but we've
still lost functionality.

Xorg devs..... we're anxious to see what you find.  :)

--
Compiz / vnc screen refresh with nvidia-restricted driver/VirtualBox/ATI fglrx driver
https://bugs.launchpad.net/bugs/353126
You received this bug notification because you are a direct subscriber
of the bug.

Status in GNOME Remote Desktop: Fix Released
Status in X.Org X server: Confirmed
Status in “vino” package in Ubuntu: Confirmed
Status in “xorg-server” package in Ubuntu: New

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 .

I installed 2.62.2 and it does indeed allow you to disable XDamage via
the gconf key 'disable_xdamage' boolean. I think this is still
considered a work around and not a fix.

NoOp wrote:
> When you use metacity composting you are not enabling any 'Extra'/additional visual effects. As others have already reported, this is the issue. Simply turning off additional visual effects isn't an answer or solution, it's a poor workaround. Vino seems to think that they have resolved the issue:
> http://bugzilla.gnome.org/show_bug.cgi?id=533613
> Comment #3 from André Klapper (points: 30)
> 2009-05-13 11:25 UTC [reply]
>
> This bug has also been fixed for 2.26.2:
> http://git.gnome.org/cgit/vino/commit/?h=gnome-2-26&id=f5260a2ad0ad9f3b1c673f6a52a938abd2a58dbb
>
> For jaunty:
> $ apt-cache policy vino
> vino:
> Installed: 2.26.1-0ubuntu1
> Candidate: 2.26.1-0ubuntu1
> Version table:
> *** 2.26.1-0ubuntu1 0
> 100 /var/lib/dpkg/status
>
> Has anyone tried vino 2.26.2 to see if that works?
> https://launchpad.net/ubuntu/+source/vino
> karmic development main release 2.26.2-1ubuntu1
>
>

I replace the vino with x11vnc before that there is no real fix
I use gnome but with krfb and KRDC there is the same problem, screen not refresh in client machine

My temporary work around and not a fix
# sudo apt-get remove vino
# killall vino-server
# sudo apt-get install x11vnc
# x11vnc -storepasswd password /path/to/passfile
# x11vnc -rfbauth /path/to/passfile
# x11vnc --noxdamage -rfbauth /path/to/passfile -forever -ncache 10 & > /dev/null

Hi andrew-barbaccia,

Please attach the output of `lspci -vvnn`, and attach your /var/log/Xorg.0.log (and maybe Xorg.0.log.old) file from after reproducing this issue. If you've made any customizations to your /etc/X11/xorg.conf please attach that as well.

[This is an automated message. Apologies if it has reached you inappropriately; please just reply to this message indicating so.]

Had the same problem updating to 9.04 (ATI graphics card)

I managed to work-around by following part of this old forum post:
http://ubuntuforums.org/showthread.php?t=470306

That is:
- Install x11vnc and vnc-common:

   sudo apt-get install x11vnc vnc-common

- Disable vino (preferences -> remote desktop)
- Start the vnc server:

sudo /usr/bin/x11vnc -rfbauth /etc/vnc.passwd -noxdamage -forever -bg -o /var/log/x11vnc.log -rfbport 5900

Hope this helps,
Lorenzo

I have same problem.

When compiz desktop effects is ON and nvidia-restricted driver installed the vnc server will not refresh the screen. If compiz is OFF then vnc works good.

>>>
Bryce Harrington wrote on 2009-07-21:

Please attach the output of `lspci -vvnn`, and attach your /var/log/Xorg.0.log (and maybe Xorg.0.log.old) file from after reproducing this issue

My files:

>> lspci -vvnn

Can anyone test to see if this is still prevalent in Karmic Koala? I can't
quite check until Sunday night.

On Fri, Jul 24, 2009 at 1:46 PM, Sergei Sedov <email address hidden> wrote:

> >> lspci -vvnn
>
> ** Attachment added: "lspci -vvnn"
> http://launchpadlibrarian.net/29490159/lspci%20-vvnn
>
> --
> Compiz / vnc screen refresh with nvidia-restricted driver/VirtualBox/ATI
> fglrx driver
> https://bugs.launchpad.net/bugs/353126
> You received this bug notification because you are a direct subscriber
> of a duplicate bug.
>
> Status in GNOME Remote Desktop: Fix Released
> Status in X.Org X server: Confirmed
> Status in “vino” package in Ubuntu: Confirmed
> Status in “xorg-server” package in Ubuntu: Incomplete
>
> 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 .
>

--
Julian Lam
Hons. BMus. III
(416) 843-4323

On 07/24/2009 11:18 AM, Julian Lam wrote:
> Can anyone test to see if this is still prevalent in Karmic Koala? I can't
> quite check until Sunday night.

See:
<https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/353126/comments/112>

When I connect to karmic amd64 in VirtualBox with desktop effects turned on, I just get a black window in the vnc viewer (at least in Jaunty it draws the initial window).

Seems that this has not been resolved yet ... not trying to beat a dead horse, but to provide more information I will describe my experience with this issue.

I have three machines I used:

Laptop:
- Ubuntu 9.04 i386 (clean install)
- non NVidia video card
- the machine running Remote Desktop Viewer (vinagre 2.26.1-0ubuntu1)
- Visual Effects set to Extra

File Server:
- Ubuntu 8.10 i386 (clean install)
- NVidia video running NVIDIA accelerated graphics driver (version 173)
- a machine runing vino 2.24.1-0ubuntu1 (VNC server)
- Visual Effects set to Extra

Workstation
- Ubuntu 9.04 amd64 (clean install)
- NVidia video running NVIDIA accelerated graphics driver (version 180)
- a machine runing vino 2.26.1-0ubuntu1 (VNC server)
- Visual Effects set to None, Normal, Extra

1) I was doing a clean install of Ubuntu 9.04 amd64 on Workstation. The Visual Effects on Workstation were defaulted to "Normal". Just after the installation (before doing anything to the system), I VNCed into Workstation from Laptop. At the same time I VNCed into File Server from Laptop. At that point in time, both VNC sessions worked perfectly.

2) While VNCed into Workstation from Laptop, On Workstation I installed the NVIDIA accelerated graphics driver (version 180). It did not ask me to reboot, so I did not at that time (but I had a sneaking suspicion that I needed to have the new driver run.) At that point in time, both VNC sessions worked perfectly.

3) Still while VNCed into Workstation from Laptop, On Workstation (just after installing the NVidia driver) I ran the Update Manager and updated everything (July 24 2009) at which point I was prompted to reboot Workstation. Again just prior to rebooting Workstation, both VNC sessions worked perfectly.

4) After rebooting and logging into Workstation, I VNCed into it from Laptop. The Visual Effects on Workstation were still set to "Normal". The initial display seemed to work but there were no updates. However it appeared that mouse clicks and keystrokes were sent to Workstation from Laptop (was able to see Workstation's Monitor). If I shut the the Remote Desktop Viewer on Laptop down and brought it back up and re-VNCed into Workstation, the display updated to what was shown on Workstation, but there were no further updates. VNCing into File Server from Laptop continued to work perfectly.

5) I rebooted Workstation and Laptop a number of times, still same result VNCing into Workstation from Laptop did not update, while VNCing into File Server from Laptop it worked (updated). Trying to debug this some more, I tried VNCing into Workstation from File Server (did not update), and into Laptop from File Server (updated).

6) I found this bug report, switched Workstation's Visual Effects to "None", VNCed into Workstation from Laptop and it updated.

To recap...
Laptop --> Workstation (pre NVidia driver, Normal visual effects) == updates
Laptop --> Workstation (post NVidia driver, Normal visual effects) == no updates
File Server --> Workstation (post NVidia driver, Normal visual effects) == no updates
Laptop --> File Server == updates
File Server --> Laptop == updates
Laptop --> Workstation (post NVidia driver, None visu...

I would just like to add something that i have recently noticed. [Running Jaunty 9.04 with all system updates]

We all know that the screen does not refresh, but now something else is happening.

My compiz effects are always on, and when im at work and want to remote in, i do this:

1-connect, right click on desktop, disconnect
2-select 'change desktop background', disconnect
3-select 'visual effect', disconnect
4-select 'no effects' and away i go.

each time i used to reconnect, the screen would show what i had previously done, therefore i was able to step through each time to turn compiz effects off. Now it doesnt show what i had previously done. i dont know if the button clicks are not working, or if the screen is not refreshing.

Cheers,
Eddie

Ubunto 9.04 with NVidia Drivers is not working using VNC (Vino).

Moreover, FreeNX in shadow mode can't enter into login display (session is showed as "gmd" user and connection is refused)

The fix is not in karmic unfortunately. It was fixed just recently on xserver master (what will be 1.7).

The fixes-
http://cgit.freedesktop.org/xorg/xserver/commit/?id=af8047f7816b39be7015e8cbbe085c57bb354592
http://cgit.freedesktop.org/xorg/xserver/commit/?id=c80ed4945ef6dd50473fab871211b71b3d20dc3c

Info on them-
http://lists.x.org/archives/xorg-devel/2009-July/001450.html

And what is the easiest way to install those patchs?

any workarround instead?

if it helps here's my lspci attached ..

and my xorg log as well ..

Perhaps a good RDP program instead of VNC? This would make it work with Windows (w/o client software) and Linux. What options are available and has anyone tried them?

There is FreeNX and google recently released their own version called neatx

http://code.google.com/p/neatx/

On Tue, Aug 18, 2009 at 3:45 PM, hanasaki <email address hidden>wrote:

> Perhaps a good RDP program instead of VNC? This would make it work with
> Windows (w/o client software) and Linux. What options are available and
> has anyone tried them?
>
> --
> Compiz / vnc screen refresh with nvidia-restricted driver/VirtualBox/ATI
> fglrx driver
> https://bugs.launchpad.net/bugs/353126
> You received this bug notification because you are a direct subscriber
> of the bug.
>
> Status in GNOME Remote Desktop: Fix Released
> Status in X.Org X server: Confirmed
> Status in “vino” package in Ubuntu: Confirmed
> Status in “xorg-server” package in Ubuntu: Incomplete
>
> 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 .
>

A good rdp like program already exsists, either freeNX or noMachines's free NX work great, and I use them all the time to connect to several of my linux computers from bith linux and windows machines. However, VNC canserves a similar but different purpose, VNC allows you to loginto an exsisting x session and view / control that session. Both RDP and NX start new sessions. Often times I need to get access to a session that is already running and perhaps is use by someone else either to show them something or to have them show me something on their screen

I've packaged the latest upstream vino for Jaunty, if anyone wants it. It allows you to disable XDamage, which makes VNC as slow as molasses, but it works.

http://www.xmission.com/~ink/vino/

It's a kludge of a workaround, not a real solution. At least I can check my POP mail remotely with it.

Well I hate to put my 2 cents worth in since there are plenty of complaints already, but I too have the same annoying problem. And it's this type of things that gives a great OS a bad rap for the average user. I know how to get to the work a rounds but average Joe would just give up and go to the OTHER OS's.
Is ther any hope for a fix on this yet? Seems to be well known and a problem for awhile.

I am not surprised it isn't fixed. If you look in Ubuntu's forum, every time anyone asks about VNC they get attacked with a bunch of people telling them to use SSH instead. I guess many of the involved people haven't realized yet that X forwarding or even FreeNX don't have the same functionalities and never have. Some people do use their machines to work, and some people do like to work from several places. Currently Windows' remote desktop capabitilites mutilates the joke in Ubuntu. Even if it would work it's still questionable why one would choose Vino, and especially why one would by standard choose vinagre, which has to be one of the suckiest clients available. :p

I really wish we'd stop getting these excessively fresh versions of Xorg. I can usually stand bleeding-edge software, but this stuff is ripped straight from the spleen and marrow.

i tried this agian last night with a freind of mine accros town, both running 9.04

we both disabled compiz and told it to use metacity

same thing, takes about 10 minutes to just bring up the desktop

crazy stuff, at least when i was connecting to my friend to help him when he had 8.04 it was useable

Chirs, your right, and there in lays the problem. But it's our own. I made the choice tho run 9.04, knowing it would have some possible problems. So I shouldn't snivel and I now recall that in the download site it say 8.04 is "ideal for larger deployment", which many of us means stable. My problem is newcomers into Ubuntu 9.04 see latest version at the site and so assumes 8.04 means old, which it is. The new user doesn't know that it also means one is considerably more stable than the other. Frustration can them continue the mantra that Linux sucks as an OS which in fact we know it's the best.

Of course this is something to take up in another forum and so I shall. I like the Debian way they simply tell you stable. testing, unstable. And we more knowledgeable users know 9.04 is the testing branch so expect hiccups.
SO SORRY FOR THE WHINING, MY BAD!!!!!

So to bring this full circle that's why there is Launchpad to post the problems so they can address them, as we have.
Thank you for the great work you all do here and please forgive our impassions it's in our nature, or we'd be using 8.04.

Can't you cherry pick the fix into ubuntu xorg packages?

Just adding those patches doesn't do anything, drivers have to be modified to provide the other half the functionality. Honestly I'm not even sure if that is going to fix this problem, seems to be something nvidia specific.

Well apparently people are reporting to same issues with AMD/ATi cards. And if it indeed is purely driver issue, why does the exact same drivers work in, for example, 8.10?

wow, 5 months and still no fix or even a clue as to what this prob is, with reports of the same regression in 9.10 it looks like my work around may be a new mobo with intel graphics.

Oh by the way all this time and I have neglected to mention that this is also a problem for my Intel laptop chipset which is the 4500MHD in an HP dv5. So it's not just limited to nvidia/VirtualBox/ATI.

Hi,

Doing nothing is not a solution.

Either everything needs to work together or something needs to be changed.

There are four possible outcomes to this debacle:

1. Do nothing and:

a) ...ignore the problem because fixing it would be too hard.
b) ...blame someone else (problem with drivers etc)

2. If the Vino server is not going to work with Desktop Effects enabled, there should be a notification when the user enables the Remote Desktop feature telling them that it won't work unless Desktop Effects is disabled.

3. Add a script to the Lock Screen command that shuts off Compiz Fusion and replaces it with Metacity (something like export DISPLAY=:0.0 ; killall -9 compiz.real ; metacity --replace ) -- then add a script to the Unlock Screen command that turns Compiz Fusion back on.

4. Replace Vino with a more useful remote desktop solution.

---

Please pick one of two through four.

This is a link to my post on the Ubuntu Forums regarding this problem with a workaround posted by another community member:

http://ubuntuforums.org/showthread.php?t=1270527

Big problem for use of Ubuntu in a school as a teacher. I just work with Intrepid in a room, with 20 computers and all is working fine : vnc and compiz. It's impossible to use scripts or ask everybody to switch off compiz each time i want to use vino. So I just don't come to jaunty at this time. It's a pity because jaunty is much more fast and use OOo 3.1. I hope someone will arrive to fix this bug wich is coming with intel graphic card too.

On Sat, Sep 19, 2009 at 6:35 PM, granier nicolas
<email address hidden>wrote:

> Big problem for use of Ubuntu in a school as a teacher. I just work with
> Intrepid in a room, with 20 computers and all is working fine : vnc and
> compiz. It's impossible to use scripts or ask everybody to switch off
> compiz each time i want to use vino. So I just don't come to jaunty at
> this time. It's a pity because jaunty is much more fast and use OOo 3.1.
> I hope someone will arrive to fix this bug wich is coming with intel
> graphic card too.
>
>
Nicolas,

You can gain access remotely by SSH'ing to the device and running:
DISPLAY=:0 metacity --replace &

This will disable compiz on the primary display, thus allowing you to
remotely manage.

Its not a fix, but a workaround when you are remote.

While I agree that the problem is irritating, frankly i've switched to FreeNX and haven't looked back. It's faster than vino ever was, and doesn't have the problems.

Surely FreeNX is faster, but it can't be seen as a solution since it serves
a whole other task. Sometime you just need to get in the *current* session,
and not in a newly started...

2009/9/21 Dave <email address hidden>

> While I agree that the problem is irritating, frankly i've switched to
> FreeNX and haven't looked back. It's faster than vino ever was, and
> doesn't have the problems.
>
> --
> Compiz / vnc screen refresh with nvidia-restricted driver/VirtualBox/ATI
> fglrx driver
> https://bugs.launchpad.net/bugs/353126
> You received this bug notification because you are a direct subscriber
> of a duplicate bug.
>

--
Grüße, Tobias Baeumer
(Web: http://mcdope.berserks.org | Blog: http://blog.mcdope.berserks.org)

@Tim - re comment #145:

Thanks for that:
"You can gain access remotely by SSH'ing to the device and running:
DISPLAY=:0 metacity --replace &"

That works. However there is a problem when switching the target machine back to compiz. I have three workspaces on the target & switch it back using:

DISPLAY=:0 compiz --replace &

Window Switcher defaults to only 2 workspaces. Checking preferences on WS on the target machine still shows 3 workspaces, but only 2 are available. The only way to get it back to three (as far as I can figure out) is for the target to use System|Preferences|Appearance|None then Extra. Following that the original 3 workspaces are restored.
Any suggestions on what to change in 'DISPLAY=:0 compiz --replace &' to restore the original number of workspaces?

I have just opened a bug report in gnome since this still persists in 9.10 and seems to be vino specific. (https://bugzilla.gnome.org/show_bug.cgi?id=595949)

A gconf option (/desktop/gnome/remote_session/disable_xdamage) has been added to disable the xdamage extension which is a temporary workaround although it requires more bandwidth. Enable the option through gconf-editor.

Please limit comments on bug reports to items that are related to development. Adding "me too", suggesting software alternatives and all other rants should be held in the forums. :)

Hopefully this gets fixed before 9.10...

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

This Bug has been fixed but not applied!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!

It's with Xorg Server, like I said months ago!!!!

Can we please get the fix ?????

Hello,

This problem is NOT related to Nvidia. I have exactly the same problem running a motherboard with integrated ATI/AMD grafics.
So I suppose it is not in the grafic driver but in another package.

It is a *very serieus problem IMHO*. I need VNC to maintain the server !!
Also note that I need a VNC version which can connect to the login screen, in oposite to connect to u user.

Louis
PS Running 9.04 x64 latest updates with the AMD via Ubuntu provided driver.

Hi all,

The people who can help with this problem have recommended that we move the discussion to the Ubuntu Forums.

Each post into this bug takes away from the time they have to fix the problem because they have to spend the time reading our comments instead.

I recommend that we move suggestions, arguments and edge cases to this thread on the forums:

http://ubuntuforums.org/showthread.php?t=1270527

We can post our comments there and if there is more feedback needed from us they can check on the forum.

I have installed a standard 9.04 installation and the nVidia restricted driver and I am experiencing the same problem. I have got round the bug by disabling the screen effects. Nightmare as I use VNC a lot.

I'm still seeing this issue on karmic koala 9.10 (just upgraded today). Using latest nvidia restricted drivers on a dual monitor setup.

The same workaround of switching to metacity still works. But I was really looking forward (hoping!) to be able to use compiz again :-)

I'm also still experiencing this bug even with a fresh install of 9.10 Desktop & nvidia-restricted drivers.

I am also having problems with this. 2 machines, each with an ATI card, running 9.1. Interestingly enough, when I VNC from the desktop to the laptop it works normally. But, when I VNC from the laptop I get the screen freeze thing.
Bob

This bug was not fixed in either Jaunty or Karmic. From the upstream reports it hasn't been fixed upstream either, so it will probably not be fixed in Lucid either. The only true fix/workaround is to reinstall Intrepid which is the last version which had a working VNC + Active Compiz integration.

is there any plan to get this fixed? the workaround is painfully slow and rumors are that there is a fix in xorg that should resolve the issue but I have yet to see any real absolute fix

what is the fix in xorg you're talking about?

On Mon, Nov 2, 2009 at 10:30 PM, jose <email address hidden> wrote:
> is there any plan to get this fixed? the workaround is painfully slow
> and rumors are that there is a fix in xorg that should resolve the issue
> but I have yet to see any real absolute fix
>
> --
> Compiz / vnc screen refresh with nvidia-restricted driver/VirtualBox/ATI fglrx driver
> https://bugs.launchpad.net/bugs/353126
> You received this bug notification because you are a direct subscriber
> of the bug.
>
> Status in GNOME Remote Desktop: Incomplete
> Status in X.Org X server: Confirmed
> Status in “vino” package in Ubuntu: Confirmed
> Status in “xorg-server” package in Ubuntu: Incomplete
>
> 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 .
>

To my knowledge, the bug was indeed fixed in the new xorg, but xorg was
delayed and wasnt released in time to be included in karmic. Looks like
we'll have to wait some more till Lucid arrives with the new xorg and
xserver

On Mon, Nov 2, 2009 at 10:40 PM, KruyKaze <email address hidden> wrote:

> what is the fix in xorg you're talking about?
>
> On Mon, Nov 2, 2009 at 10:30 PM, jose <email address hidden> wrote:
> > is there any plan to get this fixed? the workaround is painfully slow
> > and rumors are that there is a fix in xorg that should resolve the issue
> > but I have yet to see any real absolute fix
> >
> > --
> > Compiz / vnc screen refresh with nvidia-restricted driver/VirtualBox/ATI
> fglrx driver
> > https://bugs.launchpad.net/bugs/353126
> > You received this bug notification because you are a direct subscriber
> > of the bug.
> >
> > Status in GNOME Remote Desktop: Incomplete
> > Status in X.Org X server: Confirmed
> > Status in “vino” package in Ubuntu: Confirmed
> > Status in “xorg-server” package in Ubuntu: Incomplete
> >
> > 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 .
> >
>
> --
> Compiz / vnc screen refresh with nvidia-restricted driver/VirtualBox/ATI
> fglrx driver
> https://bugs.launchpad.net/bugs/353126
> You received this bug notification because you are a direct subscriber
> of the bug.
>
> Status in GNOME Remote Desktop: Incomplete
> Status in X.Org X server: Confirmed
> Status in “vino” package in Ubuntu: Confirmed
> Status in “xorg-server” package in Ubuntu: Incomplete
>
> 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...

> Looks like we'll have to wait some more till Lucid arrives with the new xorg and xserver

Yes because it totally make sense to wait two years for a major revision of an OS to fix a critical yet broken feature.

Remote desktop? Why no, my OS doesn't have that because it's called "karmic" not "lucid." I'll have to wait two years to have what Windows users and most other operating systems have had since ooooh, about 2000, possibly earlier.

The worst is that the fix has been released (view earlier messages) but not
implemented in ubuntu.

On Tue, Nov 3, 2009 at 9:31 AM, Josh <email address hidden> wrote:

> > Looks like we'll have to wait some more till Lucid arrives with the
> new xorg and xserver
>
> Yes because it totally make sense to wait two years for a major revision
> of an OS to fix a critical yet broken feature.
>
> Remote desktop? Why no, my OS doesn't have that because it's called
> "karmic" not "lucid." I'll have to wait two years to have what Windows
> users and most other operating systems have had since ooooh, about 2000,
> possibly earlier.
>
> --
> Compiz / vnc screen refresh with nvidia-restricted driver/VirtualBox/ATI
> fglrx driver
> https://bugs.launchpad.net/bugs/353126
> You received this bug notification because you are a direct subscriber
> of the bug.
>
> Status in GNOME Remote Desktop: Incomplete
> Status in X.Org X server: Confirmed
> Status in “vino” package in Ubuntu: Confirmed
> Status in “xorg-server” package in Ubuntu: Incomplete
>
> 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 .
>

Oh man this sucks. I really wish I hadn't upgraded(fresh install) from 8.04.*
Everythign was wroking fine. EVEN REMOTE DESKTOP W/ DESKTOP EFFECTS TURNED ON. This sucks.
This is one of the few times I've been extremely disappointed with my Linux OS

Wow, what a whine-fest! You people don't seem to understand what compositing is... You would NOT want desktop effects transmited over a VNC connection, the end-result would be horrible. Would you try to play a 3D game over VNC? I'm surprised it even works at all with the latest X.org. If you want desktop effects, they need to be rendered locally. Take a look at xdmx and Suse's Nomad http://en.opensuse.org/Nomad I think the latter is a good candidate for inclusion in the next Ubuntu as it seems quite user friendly already. So please, stop salivating at the mouth and just turn off compositing/desktop effects if you want to use VNC. It's that simple.

Also--for a quick, easy and user-friendly solution, install fusion-icon. It will easily let you switch between Compiz and Metacity on the fly...

FYI--for those of you bitching about VNC working on other operating systems, you really have no clue what you are talking about. X was *designed* as a remote desktop solution long before it was even possible on Windows. VNC was also designed for X and only later ported to Windows. Windows didn't even have compositing (DWM) until Visa, and VNC will work just as badly with it enabled as it does on Ubuntu. And to "John Doe:" there is no "Linux OS". Ubuntu is an OS, which runs the Linux kernel. There is no "Linux OS," don't blame the kernel developers for a problem that has nothing to do with them at best, and is only user-error at worst.

people whine because this worked very well before with composting working. The reason people like vnc is that its cross-platform, s I can connect to my desktop from some other machine regardless of what machine I'm on. from your rant, at least you point to xrdp which could be a real solution and not a workaround

That's not the point is it? No one here has claimed to want to run games through VNC, however, they do wonder why there is a broken-out-of-the-box-built-in function in Ubuntu to handle remote desktop. And unless I have missed something, if one turns off the visual effects or on, all windows from all desktops will be clogged into one single workspace. That's hardly ideal for seamless work (yes some people do use their computer to work on). Besides, the remote desktop as jose pointed out has worked prior Jaunty, there is a fix out, it is a valid bug, and there is no reason NOT to wanting it fixed tbh.

The last paragraph on your post hackel, I, however, completely agree on.

Just wanted to say, that everything is working out of the box here.

I have tested this with two system both with intel graphics (Karmic).
I also tested both directions. One system has a gma945 and the other has a X4500HD.

As far as I understand this problem it seems, that only proprietary drivers are affected.

Regards
Achim

is there a way to toggle compiz from terminal and not loose the compiz
settings everytime?

On Sun, Nov 15, 2009 at 9:29 AM, Achim <email address hidden> wrote:
> Just wanted to say, that everything is working out of the box here.
>
> I have tested this with two system both with intel graphics (Karmic).
> I also tested both directions. One system has a gma945 and the other has a X4500HD.
>
> As far as I understand this problem it seems, that only proprietary
> drivers are affected.
>
> Regards
> Achim
>
> --
> Compiz / vnc screen refresh with nvidia-restricted driver/VirtualBox/ATI fglrx driver
> https://bugs.launchpad.net/bugs/353126
> You received this bug notification because you are a direct subscriber
> of the bug.
>
> Status in GNOME Remote Desktop: Incomplete
> Status in X.Org X server: Confirmed
> Status in “vino” package in Ubuntu: Confirmed
> Status in “xorg-server” package in Ubuntu: Incomplete
>
> 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 .
>

Am Montag, den 16.11.2009, 01:49 +0000 schrieb KruyKaze:
> is there a way to toggle compiz from terminal and not loose the compiz
> settings everytime?

You can try:

metacity --replace &

and

compiz --replace &

I don't know if this is the best way, but it seems to work.
If the paneles are invisible after switching back to compiz, simply
click on them, then they should appear again.

Regards
Achim

oh thanks i'll give it a try. why wouldn't this be integrated with vnc?

On Mon, Nov 16, 2009 at 6:13 AM, Achim <email address hidden> wrote:
> Am Montag, den 16.11.2009, 01:49 +0000 schrieb KruyKaze:
>> is there a way to toggle compiz from terminal and not loose the compiz
>> settings everytime?
>
> You can try:
>
> metacity  --replace &
>
> and
>
> compiz --replace &
>
> I don't know if this is the best way, but it seems to work.
> If the paneles are invisible after switching back to compiz, simply
> click on them, then they should appear again.
>
> Regards
> Achim
>
> --
> Compiz / vnc screen refresh with nvidia-restricted driver/VirtualBox/ATI fglrx driver
> https://bugs.launchpad.net/bugs/353126
> You received this bug notification because you are a direct subscriber
> of the bug.
>
> Status in GNOME Remote Desktop: Incomplete
> Status in X.Org X server: Confirmed
> Status in “vino” package in Ubuntu: Confirmed
> Status in “xorg-server” package in Ubuntu: Incomplete
>
> 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 .
>

Am Montag, den 16.11.2009, 13:31 +0000 schrieb KruyKaze:
> oh thanks i'll give it a try. why wouldn't this be integrated with vnc?

I think this wouldn't make to much sense.

As I see it, this is only a bug of proprietary drivers that don't
integrate very well into the infrastructure.

The right solution is to tell NVIDIA and AMD to fix up there drivers.

Regards
Achim

I am unsubscribing from this bug.
I contributed a significant number of hours (clear back in JULY, three months after this bug was originally reported) in an attempt to diagnose or track down the cause of this bug. My conclusion was that it was with xorg.
Subsequent posts confirmed this:
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/353126/comments/124
Still, no patches or fixes have been applied.
My inbox continues to be filled with, "same thing here, doesn't work."
The fix, it appears, has been available since August, and yet, no one has it.
All users should help the community however they can, including with bugs, but this has made me feel like that might be a waste of time.

@J N B, I have to completely agree with you. I'm unsubscribing from this one too (and the others that I've been subscribed to for a while that have NOT been resolved either). I'm very disappointed in Ubuntu at the moment and very tired of having to 'fix' things after 'every' upgrade/update, so I've begun moving all of my systems away from Ubuntu. I'm sure I'll test Ubuntu out gain in the future, but for now, It's on to a more community friendly distro (and one that I won't have to upgrade EVERY 6 months).

@jackmetal: https://wiki.ubuntu.com/LTS

I think we need to bring more attention to this bug - and according to the Ubuntu Forums post referenced by Josh ( https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/353126/comments/152 http://ubuntuforums.org/showthread.php?t=1270527 ) one way to accomplish this would be to get more people to mark themselves as affected by it. Since this bug seems to affect everyone running Ubuntu post 8.10 with Compiz enabled, getting hordes of people to mark themselves as affected should be pretty easy. Here's a direct link if any of you have any avenues you might want to try:

https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/353126/+affectsmetoo

Who's on board?

the bug was due to x.org which was fixed months ago. unfortunately
x.org7.5 wasnt released till the end of October which was far too late
to include
it in 9.10 Karmic. Unless you want to manually upgrade your ubuntu to the
latest version of x.org then i guess we'll have to wait for 10.04 Lucid Lynx

On Tue, Nov 17, 2009 at 2:14 PM, chrisolof <email address hidden> wrote:

> @jackmetal: https://wiki.ubuntu.com/LTS
>
> I think we need to bring more attention to this bug - and according to
> the Ubuntu Forums post referenced by Josh (
> https://bugs.launchpad.net/ubuntu/+source/xorg-
> server/+bug/353126/comments/152
> http://ubuntuforums.org/showthread.php?t=1270527 ) one way to accomplish
> this would be to get more people to mark themselves as affected by it.
> Since this bug seems to affect everyone running Ubuntu post 8.10 with
> Compiz enabled, getting hordes of people to mark themselves as affected
> should be pretty easy. Here's a direct link if any of you have any
> avenues you might want to try:
>
> https://bugs.launchpad.net/ubuntu/+source/xorg-
> server/+bug/353126/+affectsmetoo
>
> Who's on board?
>
> --
> Compiz / vnc screen refresh with nvidia-restricted driver/VirtualBox/ATI
> fglrx driver
> https://bugs.launchpad.net/bugs/353126
> You received this bug notification because you are a direct subscriber
> of the bug.
>
> Status in GNOME Remote Desktop: Incomplete
> Status in X.Org X server: Confirmed
> Status in “vino” package in Ubuntu: Confirmed
> Status in “xorg-server” package in Ubuntu: Incomplete
>
> 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 .
>

That sounds more reasonable.is there a tutorial for upgrading xorg safely?

On Tue, Nov 17, 2009 at 4:37 PM, nhasian <email address hidden> wrote:
> the bug was due to x.org which was fixed months ago.  unfortunately
> x.org7.5 wasnt released till the end of October which was far too late
> to include
> it in 9.10 Karmic.  Unless you want to manually upgrade your ubuntu to the
> latest version of x.org then i guess we'll have to wait for 10.04 Lucid Lynx
>
> On Tue, Nov 17, 2009 at 2:14 PM, chrisolof <email address hidden>
> wrote:
>
>> @jackmetal:  https://wiki.ubuntu.com/LTS
>>
>> I think we need to bring more attention to this bug - and according to
>> the Ubuntu Forums post referenced by Josh (
>> https://bugs.launchpad.net/ubuntu/+source/xorg-
>> server/+bug/353126/comments/152
>> http://ubuntuforums.org/showthread.php?t=1270527 ) one way to accomplish
>> this would be to get more people to mark themselves as affected by it.
>> Since this bug seems to affect everyone running Ubuntu post 8.10 with
>> Compiz enabled, getting hordes of people to mark themselves as affected
>> should be pretty easy.  Here's a direct link if any of you have any
>> avenues you might want to try:
>>
>> https://bugs.launchpad.net/ubuntu/+source/xorg-
>> server/+bug/353126/+affectsmetoo
>>
>> Who's on board?
>>
>> --
>> Compiz / vnc screen refresh with nvidia-restricted driver/VirtualBox/ATI
>> fglrx driver
>> https://bugs.launchpad.net/bugs/353126
>> You received this bug notification because you are a direct subscriber
>> of the bug.
>>
>> Status in GNOME Remote Desktop: Incomplete
>> Status in X.Org X server: Confirmed
>> Status in “vino” package in Ubuntu: Confirmed
>> Status in “xorg-server” package in Ubuntu: Incomplete
>>
>> 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 .
>>
>
> --
> Compiz / vnc screen refresh with nvidia-restricted driver/VirtualBox/ATI fglrx driver
> https://bugs.launchpad.net/bugs/353126
> You received this bug notification because you are a direct subscriber
> of the bug.
>
> Status in GNOME Remote Desktop: Incomplete
> Status in X.Org X server: Confirmed
> Status in “vino” package...

Fresh install ubuntu x86_64 with nvidia prop drivers 190.42
managed to compile and install latest xorg-server. compiz and vino are latest i could find. Xorg -version:

X.Org X Server 1.7.1
Release Date: 2009-10-23
X Protocol Version 11, Revision 0
Build Operating System: Linux 2.6.31-14-generic x86_64
Current Operating System: Linux htpc 2.6.31-14-generic #48-Ubuntu SMP Fri Oct 16 144
Kernel command line: BOOT_IMAGE=/boot/vmlinuz-2.6.31-14-generic root=UUID=547ef98a-o
Build Date: 26 November 2009 07:35:59PM

Current version of pixman: 0.16.2
        Before reporting problems, check http://wiki.x.org
        to make sure that you have the latest version.

Still no result. Vnc viewer on my laptop never refreshes the screen. Thought I was getting somewhere, but nada

I was under the impression that yo needed xorg 7.5

On Thu, Nov 26, 2009 at 7:11 PM, jocefus <email address hidden> wrote:
> Fresh install ubuntu x86_64 with nvidia prop drivers 190.42
> managed to compile and install latest xorg-server. compiz and vino are latest i could find. Xorg -version:
>
> X.Org X Server 1.7.1
> Release Date: 2009-10-23
> X Protocol Version 11, Revision 0
> Build Operating System: Linux 2.6.31-14-generic x86_64
> Current Operating System: Linux htpc 2.6.31-14-generic #48-Ubuntu SMP Fri Oct 16 144
> Kernel command line: BOOT_IMAGE=/boot/vmlinuz-2.6.31-14-generic root=UUID=547ef98a-o
> Build Date: 26 November 2009  07:35:59PM
>
> Current version of pixman: 0.16.2
>        Before reporting problems, check http://wiki.x.org
>        to make sure that you have the latest version.
>
> Still no result. Vnc viewer on my laptop never refreshes the screen.
> Thought I was getting somewhere, but nada
>
> --
> Compiz / vnc screen refresh with nvidia-restricted driver/VirtualBox/ATI fglrx driver using X.org prior to release 7.5
> https://bugs.launchpad.net/bugs/353126
> You received this bug notification because you are a direct subscriber
> of the bug.
>
> Status in GNOME Remote Desktop: Incomplete
> Status in X.Org X server: Confirmed
> Status in “vino” package in Ubuntu: Confirmed
> Status in “xorg-server” package in Ubuntu: Incomplete
>
> 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 .
>

I believe 1.7.1 is xorg R7.5.

On Thu, Nov 26, 2009 at 7:22 PM, KruyKaze <email address hidden> wrote:

> I was under the impression that yo needed xorg 7.5
>
> On Thu, Nov 26, 2009 at 7:11 PM, jocefus <email address hidden> wrote:
> > Fresh install ubuntu x86_64 with nvidia prop drivers 190.42
> > managed to compile and install latest xorg-server. compiz and vino are
> latest i could find. Xorg -version:
> >
> > X.Org X Server 1.7.1
> > Release Date: 2009-10-23
> > X Protocol Version 11, Revision 0
> > Build Operating System: Linux 2.6.31-14-generic x86_64
> > Current Operating System: Linux htpc 2.6.31-14-generic #48-Ubuntu SMP Fri
> Oct 16 144
> > Kernel command line: BOOT_IMAGE=/boot/vmlinuz-2.6.31-14-generic
> root=UUID=547ef98a-o
> > Build Date: 26 November 2009 07:35:59PM
> >
> > Current version of pixman: 0.16.2
> > Before reporting problems, check http://wiki.x.org
> > to make sure that you have the latest version.
> >
> > Still no result. Vnc viewer on my laptop never refreshes the screen.
> > Thought I was getting somewhere, but nada
> >
> > --
> > Compiz / vnc screen refresh with nvidia-restricted driver/VirtualBox/ATI
> fglrx driver using X.org prior to release 7.5
> > https://bugs.launchpad.net/bugs/353126
> > You received this bug notification because you are a direct subscriber
> > of the bug.
> >
> > Status in GNOME Remote Desktop: Incomplete
> > Status in X.Org X server: Confirmed
> > Status in “vino” package in Ubuntu: Confirmed
> > Status in “xorg-server” package in Ubuntu: Incomplete
> >
> > 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 .
> >
>
> --
> Compiz / vnc screen refresh with nvidia-restricted driver/VirtualBox/ATI
> fglrx driver using X.org prior to release 7.5
> https://bugs.launchpad.net/bugs/353126
> You received this bug notification because you are a direct subscriber
> of a duplicate bug.
>
> Status in GNOME Remote Desktop: Incomplete
> Status in X.Org X server: Confirmed
> Status in “vino” package in Ubuntu: Confirmed
> Status in “xorg-server” package in Ubuntu: Incomplete
>
> Bug description:
> Binary package hint: compiz
>
> When u...

Hate to add a 'me, too' to this, but it is frustrating that it has been almost a year since I first started looking for a real solution to this problem and here I sit unable to remote in to my machine. Is there a solution to this in the works, or is it just going to be left to the affected users to fend for themselves after being told, essentially, "if it doesn't work for you then just don't use it"?

I think the solution is to wait for X.org 7.5 on Lucid Lynx as said on comment #175.