Ubuntu 17.10
tigervnc-xorg-extension 1.7.0+dfsg-7ubuntu1
xorg 1:7.7+19ubuntu3
cinnamon 3.4.6-1
nvidia-384 384.111-0ubuntu0.17.10.1
Bug exactly the same.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
Launchpad has imported 29 comments from the remote bug at
https://bugzilla.redhat.com/show_bug.cgi?id=214446.
If you reply to an imported comment from within Launchpad, your comment
will be sent to the remote bug automatically. Read more about
Launchpad's inter-bugtracker facilities at
@Josh: being gratis does not mean it is free. Ubuntu, like Debian,
values software freedom, so a proprietary software can ever be the
default one.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/353126
I have discovered a useful workaround:
Splashtop.
It is a much more functional remote desktop solution than VNC or Vino.
It has sound. You can play 3D games over it and even Second Life works
beautifully.
And it's available in the Ubuntu Software Center for free.
This really should be the
I'm closing the maverick-backports task on this bug due to Ubuntu 10.10
(Maverick Meerkat) no longer being supported.
This bug is being closed by a bot. If you feel the change was made in
error, please feel free to re-open the bug. However, backports requests
for Ubuntu 10.10 (Maverick Meerkat)
** Also affects: maverick-backports
Importance: Undecided
Status: New
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/353126
Title:
Compiz / vnc screen refresh with nvidia-restricted
This bug still exists, but we are tracking it at bug #772873; this
report is a dupe of that one. I would set this as a dupe, but because
this one has so many dupes on it, launchpad chokes.
Anyway, subscribe to bug #772873 if you want to follow it.
The short story is, it seems to be a bug in
Unfortunately, I'm still seeing this issue in Oneric Beta 1.
Steps to reproduce:
1) log in to guest session
2) Enable Desktop Sharing
3) Open Remote Desktop Viewer
4) Open VNC connection to localhost:5900
You'll see the initial screen, and the mouse will move around, but no
screen updates are
Confirmed: 10.04
Removing NVida proprietary drivers, and suddenly all the windows and menus that
were invisible on the remote show up.
On the local machine they were always visible.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
That's because removing the driver eliminates the source of the problem
along with the acceleration required to use Desktop Effects.
You might want to read the bug report before posting a comment.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed
This is still a problem on Ubuntu 10.10 (maverick):
kernel 2.6.25-29-generic
gnome 2.32.0
fglrx 2:8.780-0ubuntu2
compiz 1:0.8.6-0ubuntu9.2
vino 2.32.0-0ubuntu1.2
xorg 1:7.5+6ubuntu3
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
This is still a problem on Ubuntu 11.04:
fglrx 2:8.840-0ubuntu4
compiz 1:0.9.4+bzr20110415-0ubuntu2
vino 2.32.1-0ubuntu2
xorg 1:7.6+4ubuntu3
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/353126
I am having the problem with ATI video card on 11.04.
I don't understand why this VNC server is still shipping with Ubuntu
with this problem after several major releases.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
I can confirm that I'm also having this issue on 10.10 x32 with nVidia
drivers.
Was having this issue with 10.04 as well.
yes with Visual effects disabled you can get Client side info but with
visual effects enabled it does not automatically disable when someone
connects.
If you setup a
I can confirm this is still an issue with Ubuntu 10.10 x64 and ATI/AMD
Proprietary FGLRX graphics drivers installed.
Linux brutus 2.6.35-25-generic #44-Ubuntu SMP Fri Jan 21 17:40:44 UTC
2011 x86_64 GNU/Linux
With Visual Effects enabled, I get no client-side visual refresh from
VNC (using
** Changed in: xorg-server
Importance: Unknown = High
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/353126
Title:
Compiz / vnc screen refresh with nvidia-restricted
driver/VirtualBox/ATI fglrx
** Changed in: xorg-server
Importance: High = Unknown
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/353126
Title:
Compiz / vnc screen refresh with nvidia-restricted
driver/VirtualBox/ATI fglrx
My apologies, I found out i was not using the current NVIDIA driver.It is
working fine now :)
On Thu, Oct 21, 2010 at 10:42 PM, Rocko rockoreq...@hotmail.com wrote:
The open-source ATI driver doesn't have this problem; it's only a
problem with the proprietary ATI driver, so it's a problem that
I am still experiencing this bug on Maverick 64bit
--
Compiz / vnc screen refresh with nvidia-restricted driver/VirtualBox/ATI fglrx
driver using X.org
https://bugs.launchpad.net/bugs/353126
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
I don't understand how the most user friendly Linux distribution in the
world can have such a fundamental problem for *four years*.
--
Compiz / vnc screen refresh with nvidia-restricted driver/VirtualBox/ATI fglrx
driver using X.org
https://bugs.launchpad.net/bugs/353126
You received this bug
I think it's more like 2 years the problem is that it was working before and
then it broke.What I don't understand is that I know it's not uncommon to
use compiz and vnc at the same time.
On Thu, Oct 21, 2010 at 9:46 PM, Josh 353...@bugs.launchpad.net wrote:
I don't understand how the most user
The open-source ATI driver doesn't have this problem; it's only a
problem with the proprietary ATI driver, so it's a problem that the
Ubuntu developers cannot solve (and the same goes for the X developers).
It might therefore be worth raising the bug directly with AMD if you are
experiencing it.
** Changed in: vino
Status: Incomplete = Fix Released
** Changed in: vino
Importance: Unknown = Wishlist
--
Compiz / vnc screen refresh with nvidia-restricted driver/VirtualBox/ATI fglrx
driver using X.org
https://bugs.launchpad.net/bugs/353126
You received this bug notification
This should be a Stable Release Update and not a Backport.
Please see https://wiki.ubuntu.com/StableReleaseUpdates for information
on how to request an SRU
** Changed in: lucid-backports
Status: Confirmed = Invalid
--
Compiz / vnc screen refresh with nvidia-restricted
I do not have any idea what you are talking about.
I reported a bug.
I hope this does not mean you are marking the whole bug invalid, and
therefore the bug is quietly ignored.
Kris
On Thu, August 5, 2010 2:13 pm, Steve Stalcup wrote:
This should be a Stable Release Update and not a Backport.
** Changed in: xorg-server (Ubuntu)
Status: Fix Released = Fix Committed
** Changed in: xorg-server (Ubuntu)
Status: Fix Committed = Fix Released
--
Compiz / vnc screen refresh with nvidia-restricted driver/VirtualBox/ATI fglrx
driver using X.org
Not working for me. 10.04 AMD64 with NVIDIA Drivers. Connection from
Android OS to Ubuntu via VNC. Had to disable Visual Effects to be able
to receive screen refreshes.
--
Compiz / vnc screen refresh with nvidia-restricted driver/VirtualBox/ATI fglrx
driver using X.org
swatspyder: For Lucid, It requires the drivers from the right PPA -- see
comment 280.
--
Compiz / vnc screen refresh with nvidia-restricted driver/VirtualBox/ATI fglrx
driver using X.org
https://bugs.launchpad.net/bugs/353126
You received this bug notification because you are a member of Ubuntu
Thank you Troy.
--
Compiz / vnc screen refresh with nvidia-restricted driver/VirtualBox/ATI fglrx
driver using X.org
https://bugs.launchpad.net/bugs/353126
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
I have this issue with both remote desktop server and client running
Ubuntu 10.4, server uses ATI/AMD FGLRX graphics driver; either disabling
desktop-effects or setting noxdamage to true in gconf-editor are
verified workarounds, but it would be great to have a fix.
--
Compiz / vnc screen refresh
As the fix has been released in the nvidia drivers, couldn' they be
backported for Jaunty/Karmic/Lucid ?
** Changed in: nvidia-drivers-ubuntu
Status: In Progress = Fix Released
** Also affects: lucid-backports
Importance: Undecided
Status: New
** Changed in: lucid-backports
It needs to be backported xserver 1.7.0 on Karmic and Jaunty too as
mentioned Aaron on #278. I don't think this could be done on previous
distros.
--
Compiz / vnc screen refresh with nvidia-restricted driver/VirtualBox/ATI fglrx
driver using X.org
https://bugs.launchpad.net/bugs/353126
You
I've spent 3 days to solve this problem. And finally I found this link.
Changing disable_xdamage value works fine. thanks.
I think this option would be default value.or many people have to spend their
time searching for the solution.
--
Compiz / vnc screen refresh with nvidia-restricted
after I added the nvidia ppa and installe the nvidia drivers, I checked to see
if it was installed and running by 1) checking the hardware drivers to see if
nvidia current driver was installed and active, I also checked sysinfo which
also showed that it was installed. I then ran sudo
There is an nvidia ppa with the updated drivers, if you use that with
lucid then the problem is fixed. I've tested it and it works as expected
--
Compiz / vnc screen refresh with nvidia-restricted driver/VirtualBox/ATI fglrx
driver using X.org
https://bugs.launchpad.net/bugs/353126
You received
Using that PPA i cannot activate compiz lately
On Tue, Jun 29, 2010 at 10:49 AM, jose j...@cybergalvez.com wrote:
There is an nvidia ppa with the updated drivers, if you use that with
lucid then the problem is fixed. I've tested it and it works as expected
--
Compiz / vnc screen refresh with
I couldn't either until I actually set up xorg. Apparently after installing the
driver the xorg.conf file did not get created so it wasn't actually using the
driver, even though sysinfo said it was being used
Jose
--
Compiz / vnc screen refresh with nvidia-restricted driver/VirtualBox/ATI
Can you tell us how you setup xorg so we can get this working?
thanks
On Tue, Jun 29, 2010 at 2:36 PM, jose j...@cybergalvez.com wrote:
I couldn't either until I actually set up xorg. Apparently after installing
the driver the xorg.conf file did not get created so it wasn't actually using
Just backported the 256.35 version for maverick and it WORKS. At last.
So maybe we could add a bug in lucid-backports and make it work at last
for everyone.
--
Compiz / vnc screen refresh with nvidia-restricted driver/VirtualBox/ATI fglrx
driver using X.org
** Branch linked: lp:ubuntu/nvidia-graphics-drivers
--
Compiz / vnc screen refresh with nvidia-restricted driver/VirtualBox/ATI fglrx
driver using X.org
https://bugs.launchpad.net/bugs/353126
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to
Nvidia proprietary driver version 256.35 claims to fix this issue.
See: http://www.nvidia.com/object/linux-display-amd64-256.35-driver.html
Quote:
Fixed an interaction problem between Compiz and 'screen-scraping' VNC servers
like x11vnc and vino that caused the screen to stop updating. Fixes
Added /etc/modprobe.d/modprobe.conf with
alias nvidia nvidia-current
and rebooted. Now modprobe nvidia no longer complains, but I still
have all of the other issues noted earlier.
/lib/modules/2.6.32-22-generic/updates/dkms contains one nvidia file,
nvidia-current.ko, dated when I installed
Please, stop complaining about nvidia drivers installation not working here.
Open a related bug, don't litter this
--
Compiz / vnc screen refresh with nvidia-restricted driver/VirtualBox/ATI fglrx
driver using X.org
https://bugs.launchpad.net/bugs/353126
You received this bug notification
Okay. I was hoping to be able to confirm this fix, but Im sure someone
else can.
--
Compiz / vnc screen refresh with nvidia-restricted driver/VirtualBox/ATI fglrx
driver using X.org
https://bugs.launchpad.net/bugs/353126
You received this bug notification because you are a member of Ubuntu
Since installing version 256 I haven't been able to turn on compiz on my
system, let alone have it work remotely. System / Appearance / Visual
Effects / Extra causes the screen to blink a bit and then Desktop
effects could not be enabled.
From Xorg.0.log it is loading the new driver and seems
I had not installed binary from NVidia so I only updated with Synaptic.
It will update both nvidia-settings and drivers from 195 to 256.
Later I will test vino with compiz active.
--
Compiz / vnc screen refresh with nvidia-restricted driver/VirtualBox/ATI fglrx
driver using X.org
OK. With x-swat PPA drivers vino works with Desktop-Effects active in
Lucid. I think this bug is solved for Lucid and NVidia.
--
Compiz / vnc screen refresh with nvidia-restricted driver/VirtualBox/ATI fglrx
driver using X.org
https://bugs.launchpad.net/bugs/353126
You received this bug
PPA with the 256 driver version for Lucid:
https://launchpad.net/~ubuntu-x-swat/+archive/x-updates
I will install them later.
--
Compiz / vnc screen refresh with nvidia-restricted driver/VirtualBox/ATI fglrx
driver using X.org
https://bugs.launchpad.net/bugs/353126
You received this bug
After installing the ubuntu-x-swat PPA, do I need to:
1. Remove the prior driver, which was downloaded from nvidia and installed via
sh NVIDIA-Linux-x86-195.36.24-pkg1.run? By doing sh
NVIDIA-Linux-x86-195.36.24-pkg1.run --uninstall?
2. Launch synaptic and install nvidia-current?
3. Also
Nvidia drivers 256 for Karmic available on Nvidia Vdpau Team PPA:
https://launchpad.net/~nvidia-vdpau/+archive/ppa?field.series_filter=karmic
Not yet for Lucid.
--
Compiz / vnc screen refresh with nvidia-restricted driver/VirtualBox/ATI fglrx
driver using X.org
The code I added relies on a feature I added to xserver 1.7 to work
correctly. It should still be broken in Karmic, since it ships xserver
1.6.
--
Compiz / vnc screen refresh with nvidia-restricted driver/VirtualBox/ATI fglrx
driver using X.org
https://bugs.launchpad.net/bugs/353126
You
Lucid comes with 1.7.6 version of xserver:
http://packages.ubuntu.com/lucid/xserver-common
Do you mean 1.7.7 version?
--
Compiz / vnc screen refresh with nvidia-restricted driver/VirtualBox/ATI fglrx
driver using X.org
https://bugs.launchpad.net/bugs/353126
You received this bug notification
Right, the code was added for xserver 1.7.0, so Lucid should work since
it ships a newer point release of the same server branch.
You mentioned Karmic, which ships xserver 1.6.4:
http://packages.ubuntu.com/karmic-updates/x11/xserver-common
I would not expect that to work correctly with
Ok, thanks.
--
Compiz / vnc screen refresh with nvidia-restricted driver/VirtualBox/ATI fglrx
driver using X.org
https://bugs.launchpad.net/bugs/353126
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
ubuntu-bugs mailing list
Status updates:
- The cause of the issue is not X anymore
- The issue has been fixed in the latest nvidia beta driver, see
http://www.nvnews.net/vbulletin/showthread.php?p=2255561
- The issue does still affect fglrx with unknown status
** Changed in: xorg-server (Ubuntu)
Status:
That is Fantastic! can't wait to try it out!
--
Compiz / vnc screen refresh with nvidia-restricted driver/VirtualBox/ATI fglrx
driver using X.org
https://bugs.launchpad.net/bugs/353126
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
Is there a way to install this version (256.25) of nvidia drivers on
Karmic?
--
Compiz / vnc screen refresh with nvidia-restricted driver/VirtualBox/ATI fglrx
driver using X.org
https://bugs.launchpad.net/bugs/353126
You received this bug notification because you are a member of Ubuntu
Bugs,
In karmic it should be no problem:
- Uninstall any nvidia packages installed from the ubuntu repos
- Download the beta driver and make it executable (chmod +x
/path/to/NVIDIA-Linux-(x86|x86_64)-256.25.run)
- Switch to a virtual terminal (i.e. ctrl+alt+f2), login
- Stop X: sudo service gdm
About time but i'm still happy i'll try it when i get home.
Did anyone have issues installing on lucid64?
On Sat, May 22, 2010 at 10:52 AM, Sandro Mani manisan...@gmail.com
wrote:
In karmic it should be no problem:
- Uninstall any nvidia packages installed from the ubuntu repos
- Download
Actually since the issue has been reported to the nvidia devs only about
a month ago I'd say they have been really quick. Anyhow, for lucid users
which don't want to fiddle around too much it may be more convenient to
look if the updated driver appears in the proprietary-video-improvements
PPA
It works in lucid64, and I find that 3d performance is nicely improved
in wine apps. But the PC with the nvidia card now sends *both* my
monitors to vinagre's window, which makes vinagre continually become
unresponsive and grey out unless I turn on compression and scaling (and
this is just over
Speaking of all this great news, does Compiz automatically turn itself
off and get out of the way of games like Aero does in Windows 7?
On Sat, May 22, 2010 8:39 pm, Rocko wrote:
It works in lucid64, and I find that 3d performance is nicely improved
in wine apps. But the PC with the nvidia
Also having the same problem. of not refreshing the clients (viewers)
display with the hosts actual state.
Both box's are running Ubuntu 10.04LTS and have NVidia graphics cards.
--
Compiz / vnc screen refresh with nvidia-restricted driver/VirtualBox/ATI fglrx
driver using X.org
i tried running compiz --use-root-window --replace and then
connecting over vnc. while the screen updates under this setting, it
was noticeably slower than having visual effects set to none (no
compiz). i’m not sure if it was the use root window setting or compiz
itself causing the slowness,
while the screen updates under this setting, it was noticeably slower
than having visual effects set to none (no compiz)
This is expected. When no composite manager is running, the X server
sends damage events only for the parts of the screen that changed.
Because Compiz uses a much more
So I guess setting System Preferences Appearance to none and adding
compiz --use-root-window --replace to System Preferences Startup
Applications. Should serve as a workable workaround.
This can be added to the key
/desktop/gnome/session/required_components/windowmanager which is a
@Doug
Good point.
@misterhaan co
Same issue. When I tested before, I was testing a local connection (localhost).
When trying to actually use it over a dsl connection, things went terribly
wrong. As in, nearly unresponsive and in fact completely unusable.
--
Compiz / vnc screen refresh with
Using Aarons workaround i.e. running: compiz --use-root-window --replace
solves the problem for me on lucid 64 bit with a nvidia 8500 GT card and
current driver 195.36.15
--
Compiz / vnc screen refresh with nvidia-restricted driver/VirtualBox/ATI fglrx
driver using X.org
Same here. Fix working. About the same config (64 bit lucid, and 8500
card).
So I guess setting System Preferences Appearance to none and adding
compiz --use-root-window --replace to System Preferences Startup
Applications. Should serve as a workable workaround.
--
Compiz / vnc screen
@Spang
If you look at my post #248, you can change the /usr/bin/compiz script
easily to make compiz always run with --use-root-window option (albeit
this involves changing a file in /usr/bin, a technical no-no, but in
this case helpful to ensure a program always runs with the correct
options, for
[This is an automatic notification.]
Hi Andrew,
This bug was reported against an earlier version of Ubuntu, can you
test if it still occurs on Lucid?
Please note we also provide technical support for older versions of
Ubuntu, but not in the bug tracker. Instead, to raise the issue through
I am not the original reporter but I can still reproduce this bug in
lucid.
On Tue, May 4, 2010 at 2:36 PM, Bryce Harrington
br...@bryceharrington.orgwrote:
[This is an automatic notification.]
Hi Andrew,
This bug was reported against an earlier version of Ubuntu, can you
test if it still
yes the bug still exists in Lucid release.
--
Compiz / vnc screen refresh with nvidia-restricted driver/VirtualBox/ATI fglrx
driver using X.org
https://bugs.launchpad.net/bugs/353126
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
Yep, still broken on my laptop and desktop.
--
Compiz / vnc screen refresh with nvidia-restricted driver/VirtualBox/ATI fglrx
driver using X.org
https://bugs.launchpad.net/bugs/353126
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
--
I have reported my data of ubuntu-bug xorg in bug 575405 (with lucid)
--
Compiz / vnc screen refresh with nvidia-restricted driver/VirtualBox/ATI fglrx
driver using X.org
https://bugs.launchpad.net/bugs/353126
You received this bug notification because you are a member of Ubuntu
Bugs, which is
Same here. Bug still exists In lucid on all my machines. Did anyone
figure out Aaron from nividia's workaround, or test it?
-
Daniel Brady (iPhone)
darthbradysm...@gmail.com
On May 4, 2010, at 5:04 PM, Lazy ubuntu-b...@oittaa.net wrote:
Yep, still broken on my laptop
Doug, the code to enable damage events for this sort of use case is only
available in relatively recent driver releases. The code in the X
server that allows it to work was only added in the xserver 1.7
timeframe.
--
Compiz / vnc screen refresh with nvidia-restricted driver/VirtualBox/ATI fglrx
Thanks Aaron!
Ubuntu 9.10 Karmic /w updates presently has X at 1.7. from dpkg -l |
grep xorg:
ii xserver-xorg 1:7.4+3ubuntu10
the X.Org X server
So, I'm guessing I just need to download the latest 96.43.16 drivers
(vs. the 96.43.13 I presently have installed) and
No, the legacy branches do not have the code to take advantage of the
code I added to the X server, and are unlikely to get it because those
branches are limited to support for new kernels and X servers, and
critical bug fixes only. This is basically a new feature. The latest
drivers do have
For all those affected with nVidia hardware, nvidias Aaron Plattner has
just announced that the issue will be investigated, see
http://www.nvnews.net/vbulletin/showthread.php?p=2239566 .
--
Compiz / vnc screen refresh with nvidia-restricted driver/VirtualBox/ATI fglrx
driver using X.org
I looked into this today and found that the NVIDIA driver does not
correctly generate damage events for a given window when the OpenGL
rendering is actually happening to a child window. In this case, x11vnc
is listening for damage events on the root, but Compiz is rendering to
the Composite
Can someone give me the steps to implement this workaround on Ubuntu?
The user never needs to execute Compiz so there is no opportunity to
implement a command line switch.
--
Compiz / vnc screen refresh with nvidia-restricted driver/VirtualBox/ATI fglrx
driver using X.org
@Josh: I used this command from a terminal:
compiz --use-root-window --replace
and it fixes the problem. I can't see a way of enabling it via gconf-
editor, though.
** Description changed:
Binary package hint: compiz
When using the nvidia-restricted or some ATI drivers and compiz
Thanks to Aaron from NVidia for his assistance and post (#245) on this.
I implemented his --use-root-window workaround by modifying the
/usr/bin/compiz script (after first backing it up, of course). I simply
changed the line:
COMPIZ_OPTIONS=--ignore-desktop-hints --replace
to
I forgot to mention:
When running compiz.real with '--use-root-window' with nvidia 96.43.13,
the directly-connect display showed update problems, that is, portions
around windows and frames w/in windows would be black. The only way to
correct this was to switch to another viewport and then back
What I wonder is what changed too, because when desktop effects first
appeared several versions ago, I was able to use VNC and everything
worked perfectly. (I think it was about a year ago that it stopped
working). So at some point the handling for this changed in a way
that open source drivers
Koshari writes that a fix has been released, has it been tested? and if
so will it make it into 10.4?
--
Compiz / vnc screen refresh with nvidia-restricted driver/VirtualBox/ATI fglrx
driver using X.org
https://bugs.launchpad.net/bugs/353126
You received this bug notification because you are a
The problem is fixed as far as all open drivers are concerned. The issue
with the binary driver remains and will probably remain as long as no-
one with hardware that is affected cares to report the issue to the
respective places (i.e. nvnews for nvidia, virtualbox bug tracker for
virtualbox, and
** Bug watch added: Red Hat Bugzilla #214446
https://bugzilla.redhat.com/show_bug.cgi?id=214446
** Changed in: vino (Fedora)
Importance: Undecided = Unknown
** Changed in: vino (Fedora)
Status: New = Unknown
** Changed in: vino (Fedora)
Remote watch: None = Red Hat Bugzilla
I have posted a report on this bug with nvidia:
http://www.nvnews.net/vbulletin/showthread.php?p=2239566
Incidentally, it is still a problem with the latest nvidia driver
(195.36.24).
--
Compiz / vnc screen refresh with nvidia-restricted driver/VirtualBox/ATI fglrx
driver using X.org
Hi,
I am sympathetic to both Dan Burke's and Sandro Mani's points of view.
I agree with Dan that this affects way too many folks to just be left
be. On the other hand, I agree with Sandro that there's not much Ubuntu
developers can do about it re: closed-source drivers. I also think
Sandro
Hi again,
Just reading Rocko's post #239, I'm more convinced that there's more to
this than just Xdamage. The problem does *not* occur and the -noxdamage
workaround is *not* needed if one turns off all compiz special effects,
right? So, doesn't that suggest that it's not just an Xdamage issue,
(formatting problem: ... does *not* occur and the '-noxdamage'
workaround is *not* needed...)
--
Compiz / vnc screen refresh with nvidia-restricted driver/VirtualBox/ATI fglrx
driver using X.org
https://bugs.launchpad.net/bugs/353126
You received this bug notification because you are a member
** 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
1 - 100 of 156 matches
Mail list logo
