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.
** Changed in: compiz (Ubuntu)
Status: Confirmed => Invalid
** Package changed: compiz (Ubuntu) => xorg
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
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
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
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 co
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.
--
Compiz / vnc screen refresh with nvidia-restricted driver/VirtualBox/ATI fg
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.
--
Compiz / vnc screen refresh with nvidia-r
-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 so
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
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
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.
--
Compiz / vnc screen refresh with nvidia-restricted driver/VirtualBox/ATI fglrx
driver
https://bugs.launchpad.net/bugs/353126
You r
I'm using x11vnc as an alternative. The performance isn't great but it
works.
--
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 member of compiz
packagers, which is
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?
--
Compiz / vnc screen refresh with nvidi
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
wrote:
> Is this any closer to being fixed? Or, is there a way for a normal
> person that doesn't
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.la
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.
--
Compiz / vnc screen refresh with nvidia-restricted driver/Virtual
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 ++;
--
Compiz / vnc screen refresh with nvidia-restricted driver/VirtualBox/ATI fglrx
driver
https://bugs.launchpad.net/bugs/353126
You received this
17 matches
Mail list logo
