Estou usando o x2go para se conectar a um servidor Redhat 7 remoto que executa a área de trabalho do MATE. O problema que estou tendo é quando eu adiciono o export PATH="/opt/apps/anaconda2/5.0.1/bin:$PATH" ao meu .bashrc, isto quebra completamente a minha capacidade de login com o x2go. No entanto, se eu estiver no site, posso fazer login no sistema bem no console do servidor usando a área de trabalho MATE.
A razão pela qual eu preciso ter export PATH="/opt/apps/anaconda2/5.0.1/bin:$PATH" no meu .bashrc é quando executo which python recebo /opt/apps/anaconda2/5.0.1/bin , que é a minha versão desejada do python e não /usr/bin/python , que é a versão padrão do sistema do python.
O problema parece ser específico para o x2go não gostar de export PATH="/opt/apps/anaconda2/5.0.1/bin:$PATH" no meu .bashrc. É possível fazer isso funcionar?
Aqui estão as mensagens de erro do x2go.
Aquiestãoalgunsregistrosde/var/log/messagesparaacompanharoerroacima
Mar2810:08:58mv-dev-rhel7-clonesystemd-logind:Newsession106ofuserscott.Mar2810:08:58mv-dev-rhel7-clonesystemd:StartedSession106ofuserscott.Mar2810:08:58mv-dev-rhel7-clonesystemd:StartingSession106ofuserscott.Mar2810:09:03mv-dev-rhel7-clone/usr/sbin/x2gocleansessions[981]:scott-50-1522246141_stDMATE_dp32:statefileforthissessiondoesnotexist:/tmp/.x2go-scott/C-scott-50-1522246141_stDMATE_dp32/state(thiscanbeignoredduringsessionstartups)Mar2810:09:03mv-dev-rhel7-clone/usr/bin/x2gostartagent:successfullystartedX2GoagentsessionwithIDscott-50-1522246141_stDMATE_dp32Mar2810:09:06mv-dev-rhel7-clone/usr/bin/x2gomountdirs[85085]:[email protected]:35193/Users/scott/.x2go/S-scott-50-1522246141_stDMATE_dp32/spoolto/tmp/.x2go-scott/spool/C-scott-50-1522246141_stDMATE_dp32Mar2810:09:07mv-dev-rhel7-clone/usr/bin/x2goruncommand:launchingsessionwithXsession-x2gomechanism,usingSTARTUP="mate-session" Mar 28 10:09:09 mv-dev-rhel7-clone mate-session[85249]: WARNING: Could not make bus activated clients aware of XDG_CURRENT_DESKTOP=MATE environment variable: Could not connect: Connection refused Mar 28 10:09:09 mv-dev-rhel7-clone mate-session[85249]: WARNING: Could not make bus activated clients aware of DISPLAY=:50 environment variable: Could not connect: Connection refused Mar 28 10:09:09 mv-dev-rhel7-clone mate-session[85249]: WARNING: Could not make bus activated clients aware of MATE_DESKTOP_SESSION_ID=this-is-deprecated environment variable: Could not connect: Connection refused Mar 28 10:09:09 mv-dev-rhel7-clone mate-session[85249]: dconf-WARNING: failed to commit changes to dconf: Could not connect: Connection refused Mar 28 10:09:09 mv-dev-rhel7-clone mate-session[85249]: WARNING: Could not make bus activated clients aware of SESSION_MANAGER=local/unix:@/tmp/.ICE-unix/85249,unix/unix:/tmp/.ICE-unix/85249 environment variable: Could not connect: Connection refused Mar 28 10:09:15 mv-dev-rhel7-clone mate-session[85249]: Gtk-CRITICAL: gtk_main_quit: assertion 'main_loops != NULL' failed Mar 28 10:09:15 mv-dev-rhel7-clone mate-session[85249]: CRITICAL: dbus_g_proxy_new_for_name: assertion 'connection != NULL' failed Mar 28 10:09:16 mv-dev-rhel7-clone mate-session[85249]: Gtk-CRITICAL: gtk_main_quit: assertion 'main_loops != NULL' failed Mar 28 10:09:16 mv-dev-rhel7-clone mate-session[85249]: GLib-GObject-CRITICAL: g_object_unref: assertion 'G_IS_OBJECT (object)' failed Mar 28 10:09:16 mv-dev-rhel7-clone gnome-keyring-daemon[85468]: couldn't access control socket: /run/user/1000/keyring/control: No such file or directory Mar 28 10:09:16 mv-dev-rhel7-clone gnome-keyring-daemon[85468]: couldn't connect to dbus session bus: Could not connect: Connection refused Mar 28 10:09:16 mv-dev-rhel7-clone gnome-keyring-daemon[85468]: couldn't connect to dbus session bus: Could not connect: Connection refused Mar 28 10:09:16 mv-dev-rhel7-clone gnome-keyring-daemon[85468]: couldn't connect to dbus session bus: Could not connect: Connection refused Mar 28 10:09:16 mv-dev-rhel7-clone mate-session[85249]: WARNING: Could not make bus activated clients aware of GTK_OVERLAY_SCROLLING=0 environment variable: Could not connect: Connection refused Mar 28 10:09:16 mv-dev-rhel7-clone mate-session[85249]: WARNING: keycode1 not existent Mar 28 10:09:16 mv-dev-rhel7-clone mate-session[85249]: WARNING: keycode2 not existent Mar 28 10:09:16 mv-dev-rhel7-clone mate-session[85249]: WARNING: GSIdleMonitor: IDLETIME counter not found Mar 28 10:09:16 mv-dev-rhel7-clone mate-session[85249]: GLib-GObject-CRITICAL: object GSIdleMonitor 0xa5fd20 finalized while still in-construction Mar 28 10:09:16 mv-dev-rhel7-clone mate-session[85249]: GLib-GObject-CRITICAL: Custom constructor for class GSIdleMonitor returned NULL (which is invalid). Please use GInitable instead. Mar 28 10:09:16 mv-dev-rhel7-clone mate-session[85249]: CRITICAL: error getting session bus: Failed to connect to socket /tmp/dbus-1aBwJG1rzI: Connection refused Mar 28 10:09:16 mv-dev-rhel7-clone mate-session[85249]: WARNING: Unable to register presence with session bus Mar 28 10:09:16 mv-dev-rhel7-clone mate-session[85249]: CRITICAL: dbus_g_proxy_new_for_name: assertion 'connection != NULL' failed Mar 28 10:09:16 mv-dev-rhel7-clone mate-session[85249]: CRITICAL: error getting session bus: Failed to connect to socket /tmp/dbus-1aBwJG1rzI: Connection refused Mar 28 10:09:17 mv-dev-rhel7-clone /usr/bin/x2goumount-session[85540]: successfully unmounted "/tmp/.x2go-scott/spool/C-scott-50-1522246141_stDMATE_dp32" Mar 28 10:09:38 mv-dev-rhel7-clone /usr/sbin/x2gocleansessions[981]: scott-50-1522246141_stDMATE_dp32: found stale X-server process (84761), sending SIGKILL
A resposta foi atualizar para a versão mais recente do x2goserver no lado do servidor com yum update x2goserver . Eu sei, eu sei, mas em minha defesa, a primeira coisa que fiz foi checar por atualizações, mas não havia nenhuma atualização na época.
Versão incorreta de x2goserver version 4.0.1.20
Boa versão de x2goserver version 4.0.1.22
Eu tive um problema semelhante, mesmo usando as versões mais recentes do x2goserver listadas na última resposta.
Parece que o anaconda vem com sua própria versão das ferramentas dbus nas quais o x2goserver se baseia, em particular dbus-run-session e dbus-launch. Adicionar o diretório anaconda ao caminho faz com que o x2goserver escolha as versões do anaconda em vez daquelas fornecidas com a distro (Centos 7.5 no meu caso). Eu suponho que haja algum tipo de incompatibilidade entre as versões.
Uma vez que eu removi os utilitários dbus do diretório anaconda, eu pude logar novamente.