X2Go Bug report logs - #1371

version graph

Package: x2goclient; Maintainer for x2goclient is X2Go Developers <x2go-dev@lists.x2go.org>; Source for x2goclient is src:x2goclient.

Reported by: Joseph Kolibal <joseph.kolibal@gmail.com>

Date: Thu, 14 Feb 2019 02:25:01 UTC

Severity: normal

Found in version

Reply or subscribe to this bug.

Toggle useless messages

View this report as an mbox folder, status mbox, maintainer mbox

Report forwarded to x2go-dev@lists.x2go.org, X2Go Developers <x2go-dev@lists.x2go.org>:
Bug#1371; Package x2goclient. (Thu, 14 Feb 2019 02:25:01 GMT) (full text, mbox, link).

Acknowledgement sent to Joseph Kolibal <joseph.kolibal@gmail.com>:
New Bug report received and forwarded. Copy sent to X2Go Developers <x2go-dev@lists.x2go.org>. (Thu, 14 Feb 2019 02:25:01 GMT) (full text, mbox, link).

Message #5 received at submit@bugs.x2go.org (full text, mbox, reply):

From: Joseph Kolibal <joseph.kolibal@gmail.com>
To: submit@bugs.x2go.org
Subject: socket-error
Date: Wed, 13 Feb 2019 21:22:13 -0500
Package: x2goclient

When I invoke x2goclient it gives:
  socket-error, disconnected

in popup. No other message. All hosts are running ubuntu 16.04 with exactly
the software listed above. Am using MATE desktop, but even shell access
disconnects with the same error.

When I call x2goclient from a shell, I get these message dumped on the

 x2go-INFO-1> "Starting X2Go Client"
 x2go-WARNING-1> English language requested, not loading translator.
 x2go-WARNING-1> English language requested, not loading translator.
 Object::connect: No such slot ONMainWindow::slotCheckAgentProcess()
 x2go-INFO-3> "Started X2Go Client."
 x2go-INFO-8> "Starting connection to server: eos:22"
 x2go-ERROR-2> "Connection error: Cannot connect to eos:22: Socket error:
 disconnected" x2go-INFO-6> "Closing X2Go Client ..."
 x2go-INFO-7> "Finished X2Go Client closing hooks."

These are the Ubuntu 16.04 packages that are installed:
 libx2go-log-perl  all
 libx2go-server-db-perl  amd64
 libx2go-server-perl  all
 x2goclient      amd64
 x2goserver      amd64
 x2goserver-common  amd64
 x2goserver-extensions  all
 x2goserver-fmbindings  all
 x2goserver-printing  all
 x2goserver-x2goagent  amd64
 x2goserver-xsession  all
 libnx-x11-6:amd64       2:  amd64
 nxagent                 2:  amd64

The solution:

The solution was to remove the $HOME/.ssh/config file. I do not understand
why this caused a problem as the remote host (eos) had nothing listed in the
config file. It turns out that any Proxy, e.g., I had:

 ProxyCommand ssh math nc %h %p 2> /dev/null

causes a socket-error message.

Hope this helps other users.  It took me several months to find it.

In addition if the $HOME/.x2go directory does not exist on the remote
host, there is an error message that the .ssh files could not be created.

Thank you.


 Joseph Kolibal
 31 Sullivan Road
 Flemington, NJ 08822

 Contact information:
  Email:  Joseph.Kolibal@gmail.com
  Web:    http://kolibal.homeip.net/kolibal
  Phone:  908-483-5155  ☎
  Cell:   601-325-6500  ☎

Sent: From athena .- - .... . -. .-

Send a report that this bug log contains spam.

X2Go Developers <owner@bugs.x2go.org>. Last modified: Tue May 28 01:05:22 2024; Machine Name: ymir.das-netzwerkteam.de

X2Go Bug tracking system

Debbugs is free software and licensed under the terms of the GNU Public License version 2. The current version can be obtained from https://bugs.debian.org/debbugs-source/.

Copyright © 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson, 2005-2017 Don Armstrong, and many other contributors.