** Changed in: xorg-server (Ubuntu)
Status: Fix Released = Confirmed
** Summary changed:
- Compiz / vnc screen refresh with nvidia-restricted driver/VirtualBox/ATI
fglrx driver using X.org prior to release 7.5
+ Compiz / vnc screen refresh with nvidia-restricted driver/VirtualBox/ATI
From what I can see the issue has never been brought up at nvnews, which
is apparently one of the only ways to report problems with the binary
nvidia driver to their developers. I'd suggest someone who is affected
might want to try to point out the issue there (any maybe there is some
similar
Same problem. NVidia+Remote+Compiz still broken.
Odd enough, the update from a locked screen to desktop does work and
mouse pointer position updates as well.
--
Compiz / vnc screen refresh with nvidia-restricted driver/VirtualBox/ATI fglrx
driver using X.org prior to release 7.5
This was not brought up at nvnews because it was not originally a Binary
Blob issue. Whatever was changed in xorg to fix this apparently
requires a driver fix too.
At any rate, I tested my ATI box and the results were as one might
predict:
Radeon driver + Compiz: Works
FGLRX driver + Compix:
it's hard to understand what's wrong exactly.
iam guessing thats why this regression has existed for 2 years now.
it may be hard to understand whats wrong but its dead easy to reproduce
with just 3 steps.
1-install nvidia restricted drivers,
2-enable compiz
3- RDP from another machine.
and
Look: software evolves, and sometimes API breaks and things like that
are necessary. While you may be unhappy about the situation, there is
indeed nothing the open community can do if the developers behind the
closed source drivers do not want to react on the issue. That is, if
they really do
There's so many comments on this bug from so many people, it's hard to
understand what's wrong exactly.
I notice there were some xserver patches proposed as fixes; I've
verified these are included in the xserver we ship with lucid.
I don't see any comments about having this issue with the open
the xserver task can be closed, and instead the issue should be raised
directly to NVIDIA, ATI, and virtualbox to provide the missing support.
If three vendors are having the same problem, then the problem is
probably with the Vino server, not with all three vendors' products.
Perhaps you
Bryce,
If you are on Skype contact me via separate email and we can
test this out and have clarify the issue. I am about 96% sure that
I tested this with the non-proprietary nvidia driver with a friend and
we still had the problem. If that is the case I am not happy about
the bug being closed.
Comment #141 confirmed this is a bug with Intel drivers. So this is not
limited to binary blobs.
And the reason there are so many comments on this bug is because
developers have ignored this bug and instead left the community to fend
for itself and come up with half baked (if well intentioned)
It's not only Vino, actually, RealVNC has the very same problem... where
same workarounds work.
--
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
I find it frankly kind of embarrassing that this still doesn't work.
At very least there should be some kind of text around enabling
desktop effects that tells you that VNC will not work properly. This
functionality worked a few versions ago using both binary and open
source drivers, but has
May I point out that the last person actually stating that it had the
problem with intel graphics was back in september 2009, in comment 144?
Since then, the issue has only been confirmed on binary drivers (except
lunix which still needs to verify), while there are several reports of
things
The reports that it's working on Nouveau make it an invalid test case,
because the Ubuntu Nouveau drivers do not include Gallium which is
required to make Compiz work. Remote Desktop works fine with Compiz
disabled. The issue here is only with Remote Desktop + Compiz.
But to make you feel
My testing results:
Intel with Compiz Enabled: Works
Nvidia Blob with Compiz: Still Broken
My wife is using the TV so I cannot test my HTPC with fglrx yet to see
the status there.
Regardless, nobody has every investigated or stated why this worked for
all drivers, open or not, in 8.10. At any
This problem also affects Virtualbox in fullscreen even without using VNC! I
reported this problem months ago to the VB bug tracker, but noone has responded
yet. Seems launchpad is a lot more active than VirtualBox' bug tracker.
The bug is here: http://www.virtualbox.org/ticket/6089
The fix is
This is a video demonstrating the problem in the previous post:
http://www.youtube.com/watch?v=WOLv-9VwcTc
I think it is related (everything fits, except vnc).
--
Compiz / vnc screen refresh with nvidia-restricted driver/VirtualBox/ATI fglrx
driver using X.org prior to release 7.5
Are you still having this issue with Beta2? Does the target machine have
/desktop/gnome/remote_access/disable_xdamage checked? I have no issues
going from lucid Beta2 to lucid Beta2 without that option checked, but
had issues going to a karmic machine without it checked. Once checked on
the
The problem is still here Lucid - Lucid.
The only way it works is if all screen enhancements, i.e. Compiz is
turned off. No refresh happens if any of the special Compiz features
are deployed. With all turned off then screen refreshes to the initiating
machine.
On Thu, Apr 15, 2010 at 8:29 PM,
I'm also being affected by this bug on Lucid Beta1.I am running the
nvidia-restricted driver with Compiz. I'm trying to test for an OEM
deployment, and I think it would be really useful to come up with a
workaround which is obvious to users before final release of Lucid. I'd
be happy to test any
** Also affects: vino (Fedora)
Importance: Undecided
Status: New
--
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 member
I'm pretty sure that when the bug first appeared (in Jaunty) I was
running the same version of nvidia's drivers in both Intrepid and
Jaunty, and Intrepid didn't have the problem.
Note it's not just the nvidia driver that has a problem - VirtualBox's
video driver also doesn't refresh the screen.
Following problem occures with xorg 7.4 and 7.5 but does not appear in xorg
7.3: If a virtualbox guest has focus and Gnome screensaver locks screen and
user unlocks screen then, Virtualbox guest does not accepts keyboard entries.
After minimizing and restoring the Virtualbox window keyboard
wild.ideas: That being the case, perhaps someone ought to prove it out
by installing the Nvidia drivers from the 8.04 era into a fresh install
of 9.10 and demonstrating that binary nvidia + compiz + xdamage enabled
= no problem.
Or has this been done already?
That cannot be done since those
Using the Nouveau driver instead of Nvidia's proprietary driver fixes
this.
--
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
Using Nouveau does _NOT_ fix this bug, Nouveau does not support Compiz.
Can a developer PLEASE chime in on this? This worked in 8.10 and has
been broken since. We were told it would be fixed with Lucid and, a
month away from Lucid's release, it's still not fixed. Could someone
please at least
I think Nvidia should do something about this.
Assuming the problem is partially because the driver is not open_source, would
it help if I switched to recent ATI hardware ?
--
Compiz / vnc screen refresh with nvidia-restricted driver/VirtualBox/ATI fglrx
driver using X.org prior to release 7.5
I believe one of the problems with this bug's fix is that it can't be
nominated for Lucid because the option for Lucid is not available when
clicking Nominate.
Another problem is that there's not anyone whose job it is to manage the
project of fixing this bug.
Fixing this problem involves a
This being the case, then at least the developers/Canonical should
take the responsibility to produce the script you mention, such that
when someone connects to a machine that has desktop effects enabled, the
effects could be automatically switched off for that remote control
session, and then
FYI on my desktop Compiz works just fine with nouveau and vnc.
On Sat, Mar 27, 2010 at 12:02 PM, wild.ideas wild.id...@gmail.com
wrote:
This being the case, then at least the developers/Canonical should
take the responsibility to produce the script you mention, such that
when someone connects
Josh says:
* The remote desktop solution in Ubuntu uses the VNC backend which can't
read from hardware accelerated displays.
When I initially connect to the vino server, it gives me a snapshot of
the screen as I connect to it, it's just not feeding the updates.
Doesn't this suggest it *can* read
The remote desktop solution in Ubuntu uses the VNC backend which can't
read from hardware accelerated display
That's hardly true, testing on a few xserver 7.5 machines (running fedora 12
but that should not make any difference)
* intel + compiz + xdamage enabled = no problem
* open source
Hence it really looks like only the binary drivers (at least nvidia,
haven't tested fglrx) are affected.
That being the case, perhaps someone ought to prove it out by installing
the Nvidia drivers from the 8.04 era into a fresh install of 9.10 and
demonstrating that binary nvidia + compiz +
Just tried now on Lucid and it's not fixed.It was supposed to be fixed
on xorg 7.5 we waited for a year for this now.Please fix this.
--
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
Looks like this is the same issue that screws up Apple's built-in VNC
client - symptoms are the same: machine is visible through Bonjour, I
can connect, the mouse pointer moves, but screen doesn't get updated.
Super frustrating.
--
Compiz / vnc screen refresh with nvidia-restricted
Same problem still exists on 10.04 Beta1
- this really needs to be fixed, it's important...
--
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
I have confirmed both Rocko's (#197) and Mossroy's (#198) comments. That
is, with the latest Lucid Alpha (Xorg 1.7.5) and closed-source NVIDIA
drivers running compiz, the screen will not refresh. With the latest
Lucid Alpha and the Intel drivers running compiz, the screen will
refresh. It looks
This bug is confirmed on a fresh install of 10.04 alpha 3 (US English)
as well
--
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
On Sunday 28 February 2010 18:14:17 you wrote:
Like #197 I have the same problem with the same closed source drivers,
so the problem seems not X related, but maybe driver related.
but it works on debian with closed source nVIDIA drivers. Maybe some change
introduced via ubuntu patches is
It works great on my ubuntu 10.04 alpha 3 (with Intel drivers), accessed from
an ubuntu 9.04 VNC client, or a ubuntu 10.04 alpha 3 client.
With compiz fully activated, the screen refreshes correctly, and I can see the
desktop effects through VNC
--
Compiz / vnc screen refresh with
Like #197 I have the same problem with the same closed source drivers,
so the problem seems not X related, but maybe driver related.
--
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
This is still a problem in Lucid alpha3 (using xserver-xorg-core
2:1.7.5-1-ubuntu1 and Lucid's nvidia 195.36.03 drivers). The screen
doesn't update when I connect to the Lucid box, either when I connect
from a Karmic machine or from another Lucid machine.
--
Compiz / vnc screen refresh with
Actually this is not specific to nvidia-restricted drivers. I have the
latest stable nvidia drivers from PPA. No remote display refreshing if
compiz is enabled. If i switch to metacity (same as no desktop effects)
then everything back to normal. Ubuntu 9.10 Desktop x64.
--
Compiz / vnc screen
Lucid is using xorg 7.5 so I suppose the issue should be gone. Anyone
tested that yet?
--
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
This should be fixed before Lucid is released, as this is functionality
that business users require.
--
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
I can Confirm this bug in Karmic 9.10 i386. I have it installed and
completely updated on 2 machines in my house. Both Desktops Run Compiz
and Nvidia Proprietary 173 drivers.
I have Remote Desktop Viewer Enabled on both PCs Properly, to allow
remote control, ect. Here's a summary of my issue:
the fix seems to be 1) disable compiz or 2) upgrade to ubuntu lucid lynx
10.04 when its released or hey if your impatient you can try Alpha3 that
comes out in two weeks
On Wed, Feb 10, 2010 at 8:05 PM, DarthBrady
darthbradysm...@gmail.comwrote:
I can Confirm this bug in Karmic 9.10 i386. I have
@DarthBrady: this has already been confirmed (over, and over, and over again).
Try the workaround in
https://bugs.launchpad.net/ubuntu/+source/xorg-server/+bug/353126/comments/60
Works for me (albeit slow).
@nhasian: have you tried in lucid (current as of Feb 10, 2010? I did and
I still have to
This has nothing to do with closed source drivers. This bug only occurs
with Compiz enables, which the Nouveau drivers do not support, so they
are an invalid test case.
As stated before in this bug numerous times, this worked fine in 8.10
with all closed source drivers that supported Compiz.
instead of using the nvidia restricted drivers, has anyone tried it with
the open source Nouveau drivers for Nvidia?
http://nouveau.freedesktop.org/wiki/UbuntuPackages
Also if your using ATI restricted drivers you could try removing them
and just using the latest linux kernel 2.6.33 as it has
Hi all,
Just in case it helps (even though it looks like the solution today - as
I understood it after reading the 187 posts - is to wait for Lucid with
the new X.org server) :
Environment : Ubuntu AMD64 9.10, 2 Go RAM, NVidia 185, Effects set to Normal,
Vino Server
I'm accessing it from an
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
I think the solution is to wait for X.org 7.5 on Lucid Lynx as said on
comment #175.
--
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
But it works on Debian Squeeze using X.org 7.4. This is an ubuntu bug.
--
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 member of
I can also confirm I had this problem on a ASUS M3N-H/HDMI with a fresh
install of Ubuntu 9.10 and the most recent NVIDIA drivers. However,
disabling desktop effects resolved this issue for me.
--
Compiz / vnc screen refresh with nvidia-restricted driver/VirtualBox/ATI fglrx
driver using X.org
This is an ubuntu 9.04 and 9.10 bug, of course, this is a X.org prior to
7.5 bug and Ubuntu 9.04 and 9.10 had X.org buggy. Nothing new. If Debian
Squeeze has X.org 7.4 or 7.5 of course the bug is not present, like
Ubuntu 10.04.
--
Compiz / vnc screen refresh with nvidia-restricted
my workaround is the folowing:
i use ssh.
ssh to the mashine by using 'ssh -CY remotehost',
with this ssh conection i can turn compis off by typing:
'metacity --replace '
vith that done i can run vinagre on the remotehost and connect to 'localhost'
works for me.
when done i run
'compiz
@Vpablo Sorry... I missed post 175.
--
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 member of Ubuntu
Bugs, which is subscribed
** Description changed:
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
I believe 1.7.1 is xorg R7.5.
On Thu, Nov 26, 2009 at 7:22 PM, KruyKaze kruyk...@gmail.com wrote:
I was under the impression that yo needed xorg 7.5
On Thu, Nov 26, 2009 at 7:11 PM, jocefus cjbr...@nctv.com wrote:
Fresh install ubuntu x86_64 with nvidia prop drivers 190.42
managed to
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
I was under the impression that yo needed xorg 7.5
On Thu, Nov 26, 2009 at 7:11 PM, jocefus cjbr...@nctv.com 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
62 matches
Mail list logo
