title: falling back to vnc link: https://onemoretech.wordpress.com/2013/12/28/falling-back-to-vnc/ author: phil2nc description: post_id: 6846 created: 2013/12/28 02:59:58 created_gmt: 2013/12/28 07:59:58 comment_status: closed post_name: falling-back-to-vnc status: publish post_type: post

falling back to vnc

Decided to try using the companion remote desktop tools for Gnome Shell on Fedora, vinagre (client) and vino (server). I really wanted them to work out for me. They didn't. After a few hours struggling with NetworkManager on a new host (a self-inflicted wound, I was trying to get an old Dell PCI-e wireless adapter to work on the machine while still reserving the onboard NIC for a hardwire connection that wasn't managed by NM -- yeah, it didn't work... at all), I decided to give vino another try. The viagre client had already proved itself usable, although not with all the options available with the TigerVNC or any number of other older clients. It didn't take long for me to realize that while vino worked, it really didn't address my typical sysadmin's use case: connecting over to a headless server and then accessing a graphical environment for various tasks like downloading files with a web browser. In fact vino works pretty well if someone already has a gdm session, but there's really no easy way to initiate one in a remote ssh console. All the vnc servers, on the other hand, let you create a new desktop session using a single command, "vncserver". That convenience is what I need to get the job done. While vino should be able to coexist with a vnc server, I ran into some trouble when running both on the same host. As a result I removed both vino and vinagre, replacing them with the latest rpms for tigervnc and tigervnc-server.

Copyright 2004-2019 Phil Lembo