[Bug 353126] Re: Compiz / vnc screen refresh with nvidia-restricted driver/VirtualBox/ATI fglrx driver

2009-05-12 Thread XCan
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. -- Compiz / vnc screen refresh with nvidia-restricted driver/VirtualBox/ATI fglrx driver https

[Bug 353126] Re: Compiz / vnc screen refresh with nvidia-restricted driver/VirtualBox/ATI fglrx driver

2009-06-23 Thread XCan
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? -- Compiz / vnc screen refresh with nvidia-restricted driver/VirtualBo

[Bug 77442] Re: compiz / vnc screen updates with nVidia restricted

2009-04-28 Thread XCan
*** This bug is a duplicate of bug 353126 *** https://bugs.launchpad.net/bugs/353126 I too can confirm this issue. Running 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 cli

[Bug 353126] Re: Compiz / vnc screen refresh with nvidia-restricted driver

2009-04-28 Thread XCan
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. -- Compiz / vnc screen refr

[Bug 353126] Re: Compiz / vnc screen refresh with nvidia-restricted driver/VirtualBox/ATI fglrx driver

2009-07-11 Thread XCan
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. -- Compiz / vnc screen refresh with nvidia-restricted driver/VirtualBox/ATI fglrx driver https://bugs.launchpad.ne

[Bug 353126] Re: Compiz / vnc screen refresh with nvidia-restricted driver/VirtualBox/ATI fglrx driver

2009-07-12 Thread XCan
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

[Bug 353126] Re: Compiz / vnc screen refresh with nvidia-restricted driver/VirtualBox/ATI fglrx driver

2009-09-04 Thread XCan
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? -- Compiz / vnc screen refresh with nvidia-restricted driver/VirtualBox/ATI fglrx driver https://bugs.launchpad.net/bugs/35

[Bug 353126] Re: Compiz / vnc screen refresh with nvidia-restricted driver/VirtualBox/ATI fglrx driver

2009-11-10 Thread XCan
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 a

[Bug 353126] Re: Compiz / vnc screen refresh with nvidia-restricted driver/VirtualBox/ATI fglrx driver

2009-08-25 Thread XCan
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