-
Notifications
You must be signed in to change notification settings - Fork 7
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Paste from outside VNC does not work #3
Comments
Just contacted the current maintainer of GTK VNC, the VNC library that BTW, I just pushed a new version, with updated version numbers for GTK (needs 3) and GTK VNC:
|
There are two errors. First, configure_xvnc() in vnc_server.py has an error: the check for "vncconfig -list" is missing the "-display" parameter, leading always to the message "vncconfig not available". I changed the following lines:
to:
This is at least a step in the right direction. I can now connect to Xvnc using:
and clipboard works in the vncviewer. But it doesn't work in the GtkVnk widget created by vncdesk. Seems there's a bug with this widget. I searched Gnome's bugzilla, but didn't find anything. A wild guess: could it be that the vncdesk client must implement/react on the signal "vnc_server_cut_text" in main.py ?!? See https://lazka.github.io/pgi-docs/GtkVnc-2.0/classes/Display.html for API docs. |
It really seems that vncdesk must implement cut/copy/paste in both directions, using signal "vnc_server_cut_text" and method "vnc_client_cut_text". Vinagre does the same, see methods vnc_server_cut_text_cb and vinagre_vnc_tab_paste_text in https://github.com/GNOME/vinagre/blob/master/plugins/vnc/vinagre-vnc-tab.c |
Not necessary over here, on an Arch system. Anyhow, I added the display parameter. AFAICT it doesn’t hurt. New release is 1.4.1. Thanks for the report! Thanks also for the link to the vinaigre code. Perhaps it allows me to figure out how to implement copy & paste. Patches are always welcome. ;) |
@dmoebius Just tried Vinagre 3.20.2, but copy and paste doesn’t work. Does it for you? With TightVNC it does work when connecting to the exact same VNC server. |
Here on Fedora, TigerVNC is being picked up and used - not sure if that's relevant.
The text was updated successfully, but these errors were encountered: