GNOME Bugzilla – Bug 625265
allow specifying bookmark names on command line
Last modified: 2021-05-26 09:24:52 UTC
With Vinagre 2.28.1 running on Ubuntu 9.10 I mistakenly assumed that I could specify the name of a bookmark on the command line. The resulting error: Connection Closed Connection to host <bookmark> was closed. Lacked sufficient detail (such as saying "hostname not found") to suggest what I was doing wasn't possible. I was also misled due to some of my bookmarks having names that are identical to the server's local hostname, and I had been using those names on the command line. After closer scrutiny of the documentation, I learned that it is strictly host:port accepted on the command line. This ticket is a suggestion to allow specifying bookmark names on command line. It could be implemented either with by having Vinagre look for a matching bookmark, the an automatic fallback to a DNS lookup, which would be the intuitive way, or by adding a new command line switch specifically for this purpose.
I like your suggestion to fallback to a DNS lookup if a bookmark is not found, which is similar to how the command-line ssh client works with aliases. The unhelpful error message is covered in bug 626415. Setting the target milestone to 3.4 for this enhancement.
I was interested by this feature as well and found an (undocumented?) work-around by reading the code: when run from the command-line with a host name (and optionally a port, default is 5900), Vinagre will search for a bookmark with a matching host and port. If one is found, the bookmark’s extra setting (such as "Use host ___ as a SSH tunnel") will be used. I created ~/.local/share/applications/EXAMPLE.desktop like so: [Desktop Entry] Name=EXAMPLE Exec=vinagre localhost:5910 Icon=preferences-desktop-remote-desktop Terminal=false Type=Application
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.