[UFO Chicago] gnome-terminal problem

[Greg Neumarke]

On 11/27/2012 5:14 PM, Jay F Shachter wrote:
>   I also keep a gnome-terminal window up on each of those
> remote computers, with DISPLAY=m5:0, so I can execute commands on each
> of my remote computers without leaving my station in front of m5.
>
>
>
>   $ ssh nomad
>   Warning: Permanently added 'nomad' (RSA) to the list of known hosts.
>   jay at nomad's password:
>   Last login: Tue Nov 20 15:47:03 2012 from m5
>   [jay at nomad ~]$ export DISPLAY=m5:0
>   [jay at nomad ~]$ gnome-terminal &
>   [1] 2860
>   [jay at nomad ~]$ Failed to get the session bus: Failed to connect to socket /tmp/dbus-VSgG90UqPG: Connection refused
>   Falling back to non-factory mode.
>   Failed to summon the GConf demon; exiting.  Failed to contact configuration server; some possible causes are that you need to enable TCP/IP networking for ORBit, or you have stale NFS locks due to a system crash. See http://projects.gnome.org/gconf/ for information. (Details -  1: Failed to get connection to session: Failed to connect to socket /tmp/dbus-VSgG90UqPG: Connection refused)
>
>   [1]+  Exit 1                  gnome-terminal

Brainstorming:
Of what benefit is exporting gnome-terminal back to your home display, 
over just keeping an ssh window open?

Not sure if this would work or do anything, but would encapsulating any 
parts of the ssh sessions using the "screen" command allow some 
additional redirection that might make it easier to clear out these sockets?

-Greg