não consegue fazer com que o gnome-session trabalhe com o SSH

Question

Para entrar no meu computador de escritório do meu computador doméstico pelo ssh, passo pelas duas etapas: primeiro faço login no servidor do meu escritório: ssh -X myOfficeServerID@myofficeServer , em seguida, faço login no computador usando o IP local: ssh -X myOfficeComputerID@myOfficeComputerIP . Quero poder ver minha área de trabalho remotamente e trabalhar com a GUI.

Este é o resultado da execução de gnome-session :

[myOfficeComputerID@myOfficeComputer]$gnome-session
gnome-session[17491]: WARNING: Unable to determine session: Unable to lookup session information for process '17491'
GNOME_KEYRING_SOCKET=/tmp/keyring-TokklK/socket
SSH_AUTH_SOCK=/tmp/keyring-TokklK/socket.ssh
GNOME_KEYRING_PID=17507

** (gnome-settings-daemon:17510): WARNING **: You can only run one xsettings manager at a time; exiting

** (gnome-settings-daemon:17510): WARNING **: Unable to start xsettings manager: Could not initialize xsettings manager.

** (gnome-settings-daemon:17510): WARNING **: Connection failed, reconnecting...

** (gnome-settings-daemon:17510): WARNING **: Failed to connect context: Connection refused
Window manager warning: Screen 0 on display "localhost:10.0" already has a window manager; try using the --replace option to replace the current window manager.
Window manager warning: Screen 0 on display "localhost:10.0" already has a window manager; try using the --replace option to replace the current window manager.
Starting Dropbox...Connection failure: Connection refused
pa_context_connect() failed: Connection refused
Done!

(polkit-gnome-authentication-agent-1:17571): polkit-gnome-1-WARNING **: Unable to determine the session we are in: Remote Exception invoking org.freedesktop.ConsoleKit.Manager.GetSessionForUnixProcess() on /org/freedesktop/ConsoleKit/Manager at name org.freedesktop.ConsoleKit: org.freedesktop.ConsoleKit.Manager.GeneralError: Unable to lookup session information for process '17571' org.freedesktop.ConsoleKit.Manager.GeneralError Unable%20to%20lookup%20session%20information%20for%20process%20%2717571%27
system-config-printer-applet: failed to start NewPrinterNotification service

** (gnome-panel:17538): CRITICAL **: panel_applet_frame_change_background: assertion 'PANEL_IS_WIDGET (GTK_WIDGET (frame)->parent)' failed

** (nm-applet:17578): WARNING **: <WARN>  request_name(): Could not acquire the NetworkManagerUserSettings service.
  Error: (9) Connection ":1.261" is not allowed to own the service "org.freedesktop.NetworkManagerUserSettings" due to security policies in the configuration file

Failed to play sound: Not available

** (gnome-volume-control-applet:17590): WARNING **: Connection failed, reconnecting...

** (gnome-volume-control-applet:17590): WARNING **: Failed to connect context: Connection refused
Initializing nautilus-gdu extension
Initializing nautilus-open-terminal extension
Initializing nautilus-dropbox 1.4.0
Shutting down dropbox extension
Shutting down nautilus-open-terminal extension
Shutting down nautilus-gdu extension

** (gnome-volume-control-applet:17590): WARNING **: Connection failed, reconnecting...

** (gnome-volume-control-applet:17590): WARNING **: Failed to connect context: Connection refused

** (gnome-settings-daemon:17510): WARNING **: Grab failed for some keys, another application may already have access the them.

** (gnome-settings-daemon:17510): WARNING **: Clipboard manager is already running.

** (gnome-settings-daemon:17510): WARNING **: Connection failed, reconnecting...

** (gnome-settings-daemon:17510): WARNING **: Failed to connect context: Connection refused
Initializing nautilus-gdu extension
Initializing nautilus-open-terminal extension
Initializing nautilus-dropbox 1.4.0
Shutting down dropbox extension
Shutting down nautilus-open-terminal extension
Shutting down nautilus-gdu extension
Initializing nautilus-gdu extension
Initializing nautilus-open-terminal extension
Initializing nautilus-dropbox 1.4.0
Shutting down dropbox extension
Shutting down nautilus-open-terminal extension
Shutting down nautilus-gdu extension
Initializing nautilus-gdu extension
Initializing nautilus-open-terminal extension
Initializing nautilus-dropbox 1.4.0
Shutting down dropbox extension
Shutting down nautilus-open-terminal extension
Shutting down nautilus-gdu extension
Initializing nautilus-gdu extension
Initializing nautilus-open-terminal extension
Initializing nautilus-dropbox 1.4.0
Shutting down dropbox extension
Shutting down nautilus-open-terminal extension
Shutting down nautilus-gdu extension
Initializing nautilus-gdu extension
Initializing nautilus-open-terminal extension
Initializing nautilus-dropbox 1.4.0
Shutting down dropbox extension
Shutting down nautilus-open-terminal extension
Shutting down nautilus-gdu extension
Initializing nautilus-gdu extension
Initializing nautilus-open-terminal extension
Initializing nautilus-dropbox 1.4.0
Shutting down dropbox extension
Shutting down nautilus-open-terminal extension
Shutting down nautilus-gdu extension
Initializing nautilus-gdu extension
Initializing nautilus-open-terminal extension
Initializing nautilus-dropbox 1.4.0
Shutting down dropbox extension
Shutting down nautilus-open-terminal extension
Shutting down nautilus-gdu extension
Initializing nautilus-gdu extension
Initializing nautilus-open-terminal extension
Initializing nautilus-dropbox 1.4.0
Shutting down dropbox extension
Shutting down nautilus-open-terminal extension
Shutting down nautilus-gdu extension
Initializing nautilus-gdu extension
Initializing nautilus-open-terminal extension
Initializing nautilus-dropbox 1.4.0
Shutting down dropbox extension
Shutting down nautilus-open-terminal extension
Shutting down nautilus-gdu extension
Initializing nautilus-gdu extension
Initializing nautilus-open-terminal extension
Initializing nautilus-dropbox 1.4.0
Shutting down dropbox extension
Shutting down nautilus-open-terminal extension
Shutting down nautilus-gdu extension
Initializing nautilus-gdu extension
Initializing nautilus-open-terminal extension
Initializing nautilus-dropbox 1.4.0
Shutting down dropbox extension
Shutting down nautilus-open-terminal extension
Shutting down nautilus-gdu extension
failed to create drawable
Initializing nautilus-gdu extension
Initializing nautilus-open-terminal extension
Initializing nautilus-dropbox 1.4.0
Shutting down dropbox extension
Shutting down nautilus-open-terminal extension
Shutting down nautilus-gdu extension
Initializing nautilus-gdu extension
Initializing nautilus-open-terminal extension
Initializing nautilus-dropbox 1.4.0
Shutting down dropbox extension
Shutting down nautilus-open-terminal extension
Shutting down nautilus-gdu extension
Initializing nautilus-gdu extension
Initializing nautilus-open-terminal extension
Initializing nautilus-dropbox 1.4.0
Shutting down dropbox extension
Shutting down nautilus-open-terminal extension
Shutting down nautilus-gdu extension
Initializing nautilus-gdu extension
Initializing nautilus-open-terminal extension
Initializing nautilus-dropbox 1.4.0
Shutting down dropbox extension
Shutting down nautilus-open-terminal extension
Shutting down nautilus-gdu extension
Initializing nautilus-gdu extension
Initializing nautilus-open-terminal extension
Initializing nautilus-dropbox 1.4.0
Shutting down dropbox extension
Shutting down nautilus-open-terminal extension
Shutting down nautilus-gdu extension
Initializing nautilus-gdu extension
Initializing nautilus-open-terminal extension
Initializing nautilus-dropbox 1.4.0
Shutting down dropbox extension
Shutting down nautilus-open-terminal extension
Shutting down nautilus-gdu extension
^CTraceback (most recent call last):
  File "/usr/share/system-config-printer/applet.py", line 434, in <module>
    waitloop.run()
KeyboardInterrupt
** Message: Got disconnected from the session message bus; retrying to reconnect every 10 seconds

(gnome-settings-daemon:17510): GConf-WARNING **: Directory '/desktop/gtk' was not being monitored by GConfClient 0xda21e0

(gnome-settings-daemon:17510): GConf-WARNING **: Directory '/desktop/gnome/interface' was not being monitored by GConfClient 0xda21e0

(gnome-settings-daemon:17510): GConf-WARNING **: Directory '/apps/gnome_settings_daemon/gtk-modules' was not being monitored by GConfClient 0xda21e0

(gnome-settings-daemon:17510): GConf-WARNING **: Directory '/desktop/gnome/font_rendering' was not being monitored by GConfClient 0xda21e0

(gnome-settings-daemon:17510): GConf-WARNING **: Directory '/desktop/gnome/sound' was not being monitored by GConfClient 0xda21e0
GConf Error: 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-gk7tyDBsRK: Connection refused)
GConf Error: 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-gk7tyDBsRK: Connection refused)
[myOfficeComputerID@myOfficeComputer ~]$ 
(gnome-settings-daemon:17510): GConf-WARNING **: Directory '/desktop/gnome/peripherals/mouse' was not being monitored by GConfClient 0xda21e0
GConf Error: 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-gk7tyDBsRK: Connection refused)
GConf Error: 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-gk7tyDBsRK: Connection refused)
GConf Error: 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-gk7tyDBsRK: Connection refused)
GConf Error: 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-gk7tyDBsRK: Connection refused)
GConf Error: 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-gk7tyDBsRK: Connection refused)
GConf Error: 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-gk7tyDBsRK: Connection refused)
GConf Error: 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-gk7tyDBsRK: Connection refused)
GConf Error: 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-gk7tyDBsRK: Connection refused)
GConf Error: 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-gk7tyDBsRK: Connection refused)
^C

Estes comandos continuam sem parar até que eu pressione ^ C como você viu nos comandos:

Initializing nautilus-gdu extension
Initializing nautilus-open-terminal extension
Initializing nautilus-dropbox 1.4.0
Shutting down dropbox extension
Shutting down nautilus-open-terminal extension
Shutting down nautilus-gdu extension

Por enquanto, coisas como firefox são executadas no computador do meu escritório, mas o painel inferior não para de carregar as coisas.

    

Answer 1

Ambas as sessões do SSH precisam ser iniciadas usando a opção -X.

No entanto, se você quiser toda a sua sessão, talvez queira pensar em usar algo como X2go porque ele compacta imagens e tem algumas proxies que tornam muito menos banda com fome E pode restaurar sessões ...

E a execução de toda a sessão do gnome pode ter efeitos colaterais desagradáveis, quando a sessão do gnome remoto inicia uma metacididade remota que substitui o gerenciador de janelas local.

Sua informação adicional mostra os "efeitos colaterais desagradáveis" que mencionei. Você não pode simplesmente executar gnome-session quando já tiver um ambiente de área de trabalho em execução, porque o gnome-session tentará assumir o controle e seu ambiente de desktop em execução não permitirá isso tão facilmente. Para um programa X, não faz diferença se é executado remotamente via SSH ou localmente.

Dependendo do que você deseja alcançar, você pode iniciar uma sessão xnest e usá-la para sua sessão gnome remota.

xnest -geometry 1280x1024 :123 &
DISPLAY=:123 ssh -X firsthop
ssh -X secondhop
gnome-session

NOTA: Em algumas distribuições, o binário é denominado Xnest com um x maiúsculo.

    

Answer 2

Eu tive o mesmo erro, que um monte de instâncias do Navegador de Arquivos (nautilus) é aberto e não consigo me conectar corretamente à minha conta.

A razão como eu descobri hoje é que eu tinha essa linha no meu ~ .cshrc: "setenv DISPLAY unix: 0.0"

Depois de comentar, tudo funciona bem. Então aparentemente a tela é configurada duas vezes ao conectar via ssh, uma vez por ssh e uma vez por usuário-cshrc, resultando em algum caos.

    

Answer 3

As sessões gráficas não podem ser iniciadas por SSH, você precisará usar um servidor VNC ou uma conexão de área de trabalho remota. O SSH só lhe dará acesso ao shell porque a maneira como você se conectou ao computador não permite que você abra o gnome-session em um X-Session que você possa acessar. Portanto, use o VNC se você deseja obter uma área de trabalho gráfica completa na qual possa se conectar por meio de um visualizador VNC como o RealVNC. Você pode configurar um servidor VNC em sua máquina instalando tightvncserver . Você pode então iniciar o servidor VNC digitando isso no seu shell depois de instalar o tightvnc

    username@hostname $tightvncserver --geometry 1024x760

Espero que isso ajude.

    

Answer 4

Talvez você tenha acabado de esquecer o comando: xhost + (logo antes do comando ssh: ssh -XY username@servername ).