My x2go server is my desktop at work and there is a .bashrc that launches keychain and loads my ~/.ssh/id_dsa into the session environment.
the terminal gets the following output before the prompt:
- keychain 2.7.1 ~ http://www.funtoo.org
- Found existing ssh-agent: 1829
- Known ssh key: /home/rhall/.ssh/id_dsa
Then you get a bash prompt.
This output becomes the text of the error message when I try to connect to this same box via x2go-client.
The relevant lines in .bashrc are:
/usr/bin/keychain ~/.ssh/id_dsa source ~/.keychain/rhall-sh
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Am 19.01.2015 um 17:25 schrieb Rance Hall:
My x2go server is my desktop at work and there is a .bashrc that launches keychain and loads my ~/.ssh/id_dsa into the session environment.
the terminal gets the following output before the prompt:
- keychain 2.7.1 ~ http://www.funtoo.org * Found existing ssh-agent: 1829 * Known ssh key: /home/rhall/.ssh/id_dsa
Then you get a bash prompt.
This output becomes the text of the error message when I try to connect to this same box via x2go-client.
The relevant lines in .bashrc are:
/usr/bin/keychain ~/.ssh/id_dsa source ~/.keychain/rhall-sh
Just to make things easier for others trying to debug your issue - you have an SSH agent named keychain running on the *server*, not on the client?
If so, I could imagine X2GoClient is getting confused by this output when it tries to ssh into the server. Do you think you could, for debug purposes, silence this keychain tool by running it with " 2>&1 >/dev/null" (without the quotes) appended to its call?
- -Stefan
BAUR-ITCS UG (haftungsbeschränkt) Geschäftsführer: Stefan Baur Eichenäckerweg 10, 89081 Ulm | Registergericht Ulm, HRB 724364 Fon/Fax 0731 40 34 66-36/-35 | USt-IdNr.: DE268653243 -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (MingW32)
iQEcBAEBAgAGBQJUvTh0AAoJEG7d9BjNvlEZoCkIAIj5qXLpcQAg3+4CBHF157ug FryJtbzS7OXHD/QUy+otxq9yo5moUHio79OhfsprYU7MGH+PUU0bVr2VQTC4ujJl d+mba0X9M347y96phFzCS9CIY3/16e5yfR/9GekQVn6l/h/GdrtWecoQzYnSUolm V+lhydo7d9ubyy352GQMOsL4f05bNXExnBgky5/fGz4QVfOgNpa1P+7CR7PQ4+yG e8HZ5AD6EgNPIli4AcVEomvOCWngAufVJOJPq/8rkK1clklKxdpseZd5eZYn0elZ kfui9t+SXpI9BD06Ib7tbc6hse3AVqY8jFiXtVCPad1R14XW9kmA1Eg/vmbe6qI= =iTkA -----END PGP SIGNATURE-----
Stefan:
Thanks much.
I added the redirector as you suggested. I was concerned that I could not see this output as it contains valuable information, but the output is still visible and x2go now connects to this server without issue.
Thanks for the suggestion.
On Mon, Jan 19, 2015 at 11:01 AM, Stefan Baur <X2Go-ML-1@baur-itcs.de> wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Am 19.01.2015 um 17:25 schrieb Rance Hall:
My x2go server is my desktop at work and there is a .bashrc that launches keychain and loads my ~/.ssh/id_dsa into the session environment.
the terminal gets the following output before the prompt:
- keychain 2.7.1 ~ http://www.funtoo.org * Found existing ssh-agent: 1829 * Known ssh key: /home/rhall/.ssh/id_dsa
Then you get a bash prompt.
This output becomes the text of the error message when I try to connect to this same box via x2go-client.
The relevant lines in .bashrc are:
/usr/bin/keychain ~/.ssh/id_dsa source ~/.keychain/rhall-sh
Just to make things easier for others trying to debug your issue - you have an SSH agent named keychain running on the *server*, not on the client?
If so, I could imagine X2GoClient is getting confused by this output when it tries to ssh into the server. Do you think you could, for debug purposes, silence this keychain tool by running it with " 2>&1 >/dev/null" (without the quotes) appended to its call?
- -Stefan
BAUR-ITCS UG (haftungsbeschränkt) Geschäftsführer: Stefan Baur Eichenäckerweg 10, 89081 Ulm | Registergericht Ulm, HRB 724364 Fon/Fax 0731 40 34 66-36/-35 | USt-IdNr.: DE268653243 -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (MingW32)
iQEcBAEBAgAGBQJUvTh0AAoJEG7d9BjNvlEZoCkIAIj5qXLpcQAg3+4CBHF157ug FryJtbzS7OXHD/QUy+otxq9yo5moUHio79OhfsprYU7MGH+PUU0bVr2VQTC4ujJl d+mba0X9M347y96phFzCS9CIY3/16e5yfR/9GekQVn6l/h/GdrtWecoQzYnSUolm V+lhydo7d9ubyy352GQMOsL4f05bNXExnBgky5/fGz4QVfOgNpa1P+7CR7PQ4+yG e8HZ5AD6EgNPIli4AcVEomvOCWngAufVJOJPq/8rkK1clklKxdpseZd5eZYn0elZ kfui9t+SXpI9BD06Ib7tbc6hse3AVqY8jFiXtVCPad1R14XW9kmA1Eg/vmbe6qI= =iTkA -----END PGP SIGNATURE-----
x2go-user mailing list x2go-user@lists.x2go.org http://lists.x2go.org/listinfo/x2go-user
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Am 19.01.2015 um 19:01 schrieb Rance Hall:
I added the redirector as you suggested. I was concerned that I could not see this output as it contains valuable information, but the output is still visible and x2go now connects to this server without issue.
That sounds weird. If the output is redirected, then it should not show up at all. Could it be that you have added the line to several scripts that are run at login?
Here's a snippet of information that might help you find out where to search, written down by a friend of mine: these three files are present.
- ----8<----start snippet----8<---- Bash will read the following files in the following sequence: if it is a login shell: /etc/profile (if present) afterwards: (if present) ~/.bash_profile (else, if present) ~/.bash_login (else, if present) ~/.profile -> only the first match of these last three will be used, if any of
if bash is an interactive *non*-Login-Shell: /etc/bash.bashrc afterwards: ~/.bashrc (if present)
Login-Shells are used by console-tty, ssh, other remote Logins, sometimes sudo and su. *non*-Login-Shells are used for the other cases (like xterm, other X11-Terminal-Clients, and some other caseses of sudo and su).
A classic X-Login will run /etc/X11/Xsession, which in turn checks if ~/.xsession and ~/.xsessionrc are present. If they are, .xsessionrc will be sourced, while .xsession will be spawned as a separate process.
- ----8<---- end snippet ----8<----
And if that wasn't already confusing enough, there's more to be found at https://www.gnu.org/software/bash/manual/html_node/Bash-Startup-Files.html
Thanks for the suggestion.
You're welcome! Thank you for choosing X2Go!
- -Stefan
BAUR-ITCS UG (haftungsbeschränkt) Geschäftsführer: Stefan Baur Eichenäckerweg 10, 89081 Ulm | Registergericht Ulm, HRB 724364 Fon/Fax 0731 40 34 66-36/-35 | USt-IdNr.: DE268653243 -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (MingW32)
iQEcBAEBAgAGBQJUvYcQAAoJEG7d9BjNvlEZteMH/3nBeZGmEoztCBOcCqCv3W1k 9OZzJkuHUNWBHahw+57UwU/c2TO6zgHfLnEMaxxJbgZujOAtvdcJOwAM+dwhg0f5 cYpDSFSuq+hEAt5MTAu2I/F1G98oCBstFFqKrruKpRK0jdFet0I40OT/ZWwGAnel 7NpC0XrgbQAWPhimyt8Duxnd66K4gmgvUoHQu6KNdJjBpQfbYvYepvMa7C1UxUL8 8eyKodgwGTwXf3S4umcmBLCrQF6+1xptgXaG5aHNdPxSmalXYPHJlWTkwB5fHgqP VHr+wFnzhvhfKB80B4/OQLLM1sQgHMxHRoQq/nnllKGxT7OWe6oG3glKmgYeSak= =eyy7 -----END PGP SIGNATURE-----
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
Am 19.01.2015 um 23:37 schrieb Stefan Baur:
I added the redirector as you suggested. I was concerned that I could not see this output as it contains valuable information, but the output is still visible and x2go now connects to this server without issue. That sounds weird. If the output is redirected, then it should not show up at all.
Bzzt. The error is on my side. I actually reversed the parameters. " 2>&1 >/dev/null" will not make the whole thing go silent. That's what " >/dev/null 2>&1" does.
With " 2>&1 >/dev/null", STDERR still gets printed. So you could simply use " >/dev/null" for the same effect.
- -Stefan
BAUR-ITCS UG (haftungsbeschränkt) Geschäftsführer: Stefan Baur Eichenäckerweg 10, 89081 Ulm | Registergericht Ulm, HRB 724364 Fon/Fax 0731 40 34 66-36/-35 | USt-IdNr.: DE268653243 -----BEGIN PGP SIGNATURE----- Version: GnuPG v2.0.22 (MingW32)
iQEcBAEBAgAGBQJUvaLQAAoJEG7d9BjNvlEZKt8H/i5FUeTwDeo12IK5mQz7yTue RMmkVhi1NpT3Q74Kk2fptkr2Qaz7/Yy7ye/VGx7eKz7RTI7dMqpHGFtObvCvOTHW /MlL0sQfOp9WYn1r9DjBNsg/S9UmxPWXN4iTYDw7alAH3cWz6AXNG3BcOYWoaK1+ 0mCiF+CnSom+tr8z+1seUSUnblyMurjkeI13kGFO5NIF9hwXa+8SsKEfXZUNOA7X N5pYA0+hWI3+j4r5zZz5FLZvwF/tHgH4o38zV7+CdnWcMABjfsPG2cdsiYiysxyj PfBLpS2QFXd2PiYYLvLeemwqfivh+/I95XXqJyMAJmbk/6jOWO0qsIYOs6U52wg= =K1aH -----END PGP SIGNATURE-----
Hi Rance,
On Mo 19 Jan 2015 19:01:05 CET, Rance Hall wrote:
Stefan:
Thanks much.
I added the redirector as you suggested. I was concerned that I could not see this output as it contains valuable information, but the output is still visible and x2go now connects to this server without issue.
Thanks for the suggestion.
Please see [1] and [2].
Mike
[1]
http://stackoverflow.com/questions/12440287/scp-doesnt-work-when-echo-in-bas...
[2] http://bugs.x2go.org/cgi-bin/bugreport.cgi?bug=327
--
DAS-NETZWERKTEAM mike gabriel, herweg 7, 24357 fleckeby fon: +49 (1520) 1976 148
GnuPG Key ID 0x25771B31 mail: mike.gabriel@das-netzwerkteam.de, http://das-netzwerkteam.de
freeBusy: https://mail.das-netzwerkteam.de/freebusy/m.gabriel%40das-netzwerkteam.de.xf...
-
Mike Gabriel -
Rance Hall -
Stefan Baur