I was having issues today after installing x2go. Here is was I did to fix them.
My first issue happened trying to install the x2gognomebindings. This is the error I was getting:
Setting up x2gognomebindings (2.0.1.3-0~47~oneiric1) ...
Settings menu not found in /etc/xdg/menus at /usr/sbin/update-gnome-menu-x2go li
ne 43.
dpkg: error processing x2gognomebindings (--configure):
subprocess installed post-installation script returned error exit status 2
Errors were encountered while processing:
x2gognomebindings
E: Sub-process /usr/bin/dpkg returned an error code (1)
This would happen every time I tried anything with apt. What I did to fix it was simple.
sudo cp /etc/xdg/menus/gnome-settings-x2go.menu /etc/xdg/menus/gnome-settings.menusudo apt-get install x2gognomebindings
My second issue happened when I tried to connect to x2go for the first time. I was getting this error:
Authentification Failed The host key for this server was not found but an othertype of key exists.An Attacker might change the default server key toconfuse your client into thinking the key does not existThis will happen if you SSH into the server before installing x2go. SSH by default likes ecdsa keys, and x2go doesn't. On the server, edit the ssh config:
sudo nano /etc/ssh/sshd_configThen comment out this line with a #:
HostKey /etc/ssh/ssh_host_ecdsa_key
Now restart ssh:
sudo service ssh restart
On your client you need to remove your old key. I just removed all of them.
rm .ssh/known_hosts
thx - the host key solution was very useful for me!
ReplyDeleteThe text in your "Repeated here for the bots:" is wrong. You used the right word "Authentication Failed", but the dialog actually says "Authentification Failed" which is what I searched for and didn't show this helpful looking blog entry. Thankfully Google suggested the tweak you made.
ReplyDeleteThanks for sharing your fixes though!
I updated it. Thanks for letting me know.
ReplyDeleteHey John... I use x2go also. Could you see if the x2go wiki has your tip(s) and if not add them?
ReplyDeleteAnyone can edit the x2go wiki as its an open community:
http://wiki.x2go.org/doku.php/wiki:start
Thanks for these notes, which have just come in useful re the ecdsa key problem. And thanks for making the error search engine friendly, as yours was the only reference tot he problem.
ReplyDeleteThanks, this was what I was looking for!
ReplyDeleteTHANK YOU! Sometimes we think our little blurb on an obscure item is worthless. you saved me HOURS of frustration as I am a NOOB. I appreciate this post, and it helped immensely
ReplyDeleteMuito obrigado!
ReplyDelete¡Muchas gracias!
ReplyDeletethanks, much appreciated
ReplyDeleteBetter way:
ReplyDeletessh-keygen -R (the ip addr)
Try again from x2go, accept the key, and you are good to go. No need to disable anything.
Many thanks John. It's info like this that makes the world go 'round.
ReplyDeleteThanks! I am getting the same key error :( .. I will try this out.. :)
ReplyDeleteThanks John, this fixed it for me. Very Appreciative!
ReplyDeleteTexas USA
Thank you kindly for the solution. x2goclient's message wasn't helpful at all in debugging the issue.
ReplyDeleteCheers, regards from Russia.
Thank you! Just came across this by searching for that error message. The weird one for me though is that I had to do the opposite: by default that line in /etc/ssh/sshd_config is comment out in openSuse 12.3. Only after uncommenting it and restarting sshd would the error msg. go away.
ReplyDeleteThanks for the info! I followed the step and was able to connect to the X2Go server now.
ReplyDeleteVery helpful!! thanks!
ReplyDeleteThanks John. It helped me too.
ReplyDeleteMany thanks :)
ReplyDelete