After an evaluation, GNOME has moved from Bugzilla to GitLab. Learn more about GitLab.
No new issues can be reported in GNOME Bugzilla anymore.
To report an issue in a GNOME project, go to GNOME GitLab.
Do not go to GNOME Gitlab for: Bluefish, Doxygen, GnuCash, GStreamer, java-gnome, LDTP, NetworkManager, Tomboy.
Bug 636811 - Cannot copy from remote and paste in local
Cannot copy from remote and paste in local
Status: RESOLVED DUPLICATE of bug 633691
Product: vinagre
Classification: Applications
Component: general
2.30.x
Other Linux
: Normal normal
: ---
Assigned To: vinagre-maint
vinagre-maint
Depends on:
Blocks:
 
 
Reported: 2010-12-08 20:54 UTC by Acorn Pooley
Modified: 2011-03-21 23:56 UTC
See Also:
GNOME target: ---
GNOME version: ---


Description Acorn Pooley 2010-12-08 20:54:43 UTC 
To duplicate:
  - select and copy text in the remote machine.
  - paste in the local machine

Does not work in 2.30.2.  This used to work in 2.28.1.
Does not work when pasting 'PRIMARY' selection (e.g. with middle mouse click in xterm).
Does not work when pasting with 'CLIPBOARD' selection (e.g. with ^V in firefox)

(Note: copy in local machine and paste to remote machine still works.)

Environment:
Local machine:
  vinagre 2.30.2
  32 bit Ubuntu linux 'lucid' on x86
Remote machine:
  Windows 7 on x86
Comment 1 David King 2011-03-20 10:42:15 UTC 
Can you check which version of gtk-vnc you are using? It seems that this is a bug in gtk-vnc that was fixed in 0.4.2. See bug 633691 for details. If you are using a version of gtk-vnc older than 0.4.2, please try upgrading, and if that solves the problem, this bug can be closed as a duplicate.
Comment 2 Acorn Pooley 2011-03-21 23:55:26 UTC 
Bug has been fixed in latest version (confirmed to work with
  libgtk-vnc-1.0-0   0.3.10-2ubuntu2
  vinagre            2.30.0-0ubuntu2

Closing as dup of bug 633601
Thanks!!

*** This bug has been marked as a duplicate of bug 633601 ***
Comment 3 Acorn Pooley 2011-03-21 23:56:35 UTC 
oops - dup of bug 633691  (not 633601)

*** This bug has been marked as a duplicate of bug 633691 ***