GNOME Bugzilla – Bug 617795
Way to leverage the xvnc4viewer engine instead of the present one?
Last modified: 2021-05-26 09:25:10 UTC
The VNC performance of the vinagre engine seems to be a lot slower than the xvnc4viewer on Ubunutu. Also, xvnc4viewer shows the local cursor position using a nice "dot" where I am getting no local cursor in vinagre. Also xvnc4viewer supports changing the options on the fly (color depth, encoding, etc) but I also do not see this as an option of vinagre. I like the fact that Vinagre remembers my connections and has a tab layout with toolbars, but much prefer the xvnc4viewer for the actual VNC features and performance. Any chance to make the vnc engine swappable?
As vnc is implemented as a plugin, I think one could write another plugin that uses libvncserver or whatever instead of gtk-vnc. That said, feel free to come with a patch for that.
Scenario: Connecting from my lower resolution laptop to higher resolution server. Issue: Vinagre slow scaling Issue: Vinagre poor scaling Issue: Slow Vinagre performance (some search engine optimization keywords above) Performance of VNC is poor when scaling remote screen to fit within local screen. About 1 screen refresh in 4 seconds. If I disable scaling, I may reach 1 screen refresh per second if things go well. Jonh Wendell commented above that a patch would be an acceptable option. Really? Nice reply. Since that is the reply, I might as well provide a workaround in the "spirit" of that note. WORKAROUND FOR FOLKS READING THIS BUG WHO DONT WANT TO SUBMIT A PATCH: The "Remmina" GTK+ Remote Desktop Client has tremendously good performance and fine feature set. Please give it a try. It is the tool I have switched to just today given the feedback from Vinagre dev. I am getting near instant screen refresh performance, outstanding!
GNOME is going to shut down bugzilla.gnome.org in favor of gitlab.gnome.org. As part of that, we are mass-closing older open tickets in bugzilla.gnome.org which have not seen updates for a longer time (resources are unfortunately quite limited so not every ticket can get handled). If you can still reproduce the situation described in this ticket in a recent and supported software version of Vinagre, then please follow https://wiki.gnome.org/GettingInTouch/BugReportingGuidelines and create a new enhancement request ticket at https://gitlab.gnome.org/GNOME/vinagre/-/issues/ Thank you for your understanding and your help.