← Back to team overview

ubuntu-x-swat team mailing list archive

Re: [Bug 493889] Re: remote desktop viewer does not refresh remote display

 

*** This bug is a duplicate of bug 353126 ***
    https://bugs.launchpad.net/bugs/353126

That is not a fix it's just a workaround.Some of us use compiz for window
rules etc.. so this won't fix the problem.

On Wed, May 5, 2010 at 3:20 PM, Tom McCoy <speedmccoy@xxxxxxxxx> wrote:

> *** This bug is a duplicate of bug 353126 ***
>    https://bugs.launchpad.net/bugs/353126
>
> Setting "Visual Effects" to NONE fixed it for me too (Karmic). Thank you
> all for this thread.
>
> --
> remote desktop viewer does not refresh remote display
> https://bugs.launchpad.net/bugs/493889
> You received this bug notification because you are a direct subscriber
> of the bug (via bug 353126).
>
> Status in “vinagre” package in Ubuntu: New
>
> Bug description:
> Binary package hint: vinagre
>
> I am able to log in to the remote pc and the inittial display state show
> up, but if i try to click or open anything nothing happens in desktop
> viewer. if i look at the actual monitor connected to the remote pc i could
> control everything remotely. Also to add to the oddness on the remote
> desktop viewer i could see the mouse refresh only but none of the actions or
> screen gets refreshed. very odd! i'm using ubuntu 9.10 on both pcs.
>
> ProblemType: Bug
> Architecture: i386
> Date: Mon Dec  7 21:56:56 2009
> DistroRelease: Ubuntu 9.10
> ExecutablePath: /usr/bin/vinagre
> Package: vinagre 2.28.1-0ubuntu1
> ProcEnviron:
>  LANG=en_US.UTF-8
>  SHELL=/bin/bash
> ProcVersionSignature: Ubuntu 2.6.31-14.48-generic
> SourcePackage: vinagre
> Uname: Linux 2.6.31-14-generic i686
>
> To unsubscribe from this bug, go to:
> https://bugs.launchpad.net/ubuntu/+source/vinagre/+bug/493889/+subscribe
>

-- 
remote desktop viewer does not refresh remote display
https://bugs.launchpad.net/bugs/493889
You received this bug notification because you are a member of Ubuntu-X,
which is subscribed to xorg-server in ubuntu (via bug 353126).



References