Bug 16361

(In reply to Michel ABRAHAM from comment #0)

> 
> Note: Server is fully functional with windows client !
> 
> When attempt to connect to the server with client software, I have just a
> message 
> "Attenth failed" NO another message or precision.

"Attenth failed", exaclty spelled like that and not one word more?
> 
> user code and password are ok.
> 

user code = user name and
password = user password
or
user code = ~/.ssh/id_rsa
password = password to access ~/.ssh/id_rsa ?

CC: (none) => mageia, marja11, oliver.bgr, thierry.vignaud
Summary: x2go client => x2go client cannot connect to x2go server in Mageia 5 (neither after upgrade from 4 -> 5, nor in fresh Mga5 install), "Autenth
Source RPM: (none) => x2goclient-4.0.1.3-4.mga5

Created attachment 6840 [details]
screen capture error client x2go

The only message I have to describe the problem is this little message

user code= username and password = user password
(In reply to Marja van Waes from comment #1)
> (In reply to Michel ABRAHAM from comment #0)
> 
> > 
> > Note: Server is fully functional with windows client !
> > 
> > When attempt to connect to the server with client software, I have just a
> > message 
> > "Attenth failed" NO another message or precision.
> 
> "Attenth failed", exaclty spelled like that and not one word more?
I wanted to write the "authentication failed", sorry for that.
> > 
> > user code and password are ok.
> > 
> 
> user code = user name and
> password = user password
Yes
> or
> user code = ~/.ssh/id_rsa
> password = password to access ~/.ssh/id_rsa ?

I think it is very easy to reproduce it.

Thanks for the feedback and no problem about the typo, I make them all the time ;-)

Personally, I don't use x2go at all, so I won't try to reproduce. I'm only trying to collect as much information as possible to help whoever is going to look into this problem (unfortunately, we do currently not have a maintainer for x2go).

Would it be possible for you to try whether it also fails with an advanced authentication method, e.g. with a pair of ssh keys?

Summary: x2go client cannot connect to x2go server in Mageia 5 (neither after upgrade from 4 -> 5, nor in fresh Mga5 install) => x2go client cannot connect to x2go server in Mageia 5, neither after upgrade from 4 -> 5, nor in fresh Mga5 install (authentication failed)

(In reply to Marja van Waes from comment #5)
> Thanks for the feedback and no problem about the typo, I make them all the
> time ;-)
> 
> Personally, I don't use x2go at all, so I won't try to reproduce. I'm only
> trying to collect as much information as possible to help whoever is going
> to look into this problem (unfortunately, we do currently not have a
> maintainer for x2go). 
Ok, I understand :-(
> 
> Would it be possible for you to try whether it also fails with an advanced
> authentication method, e.g. with a pair of ssh keys?

Well, next to your idea, I have been in different paths :

- authentication via ssh :
on client:
ssh-keygen -t rsa
ssh-copy-id -i ~/.ssh/id_rsa.pub michel@my-srv-x2go-mageia

test and results :
ssh  michel@my-srv-x2go-mageia
 -> it's long, but it's works, I solved later this long time of wait
with x2go client, many problems go to crash, sometimes connects, but finally crash

some way to solve those problems (seen in differents forums)
on server side :
nano /etc/ssh/ssh_config
add/modify keys :
RSAAuthentication yes
PubkeyAuthentication yes
GSSAPIAuthentication no
UseDNS No
 
and a restart of sshd

Solve nothing, same as before, sometimes connects and crash (close client x2go brutally) and other time, doesn't work

For long time to ssh connect, good news, and I note this idea for my machines :
change in /etc/nsswitch.conf
before :
hosts:          mdns4_minimal files nis dns myhostname mdns4 
after :
hosts:           files dns nis mdns4_minimal myhostname mdns4 

Now, connections are very very fast !!!
But problem with x2go is same.
I add some trace of server side, to memory...

Created attachment 6844 [details]
system log file server side of connection x2go client evenement

Created attachment 6845 [details]
try to restore after the crash, crash again

Next to the precedent crash, I try to reconnect, it's seems to do the job, but, finally, crash again.

Those actions works very well in windows client X2go version. :-(

Hi,

Did you make it work ? I have exactly the same issue with the same small window saying the authentication has failed.
But if I connect to the x2go server with ssh :
ssh eric@ordi4 
and then enter my password on the server, I don't have any problem.

x2go-DEBUG-../onmainwindow.cpp:1167> Removing apps from tray
x2go-INFO-8> "Starting connection to server: ordi4:22"
x2go-DEBUG-../onmainwindow.cpp:2817> Start new ssh connection to server:"ordi4":"22" krbLogin: false

Regards.

Xuo.

CC: (none) => xuoy

Thx Michel and Eric, for all the extra information and for reminding me this bug exists.

There is still no maintainer, but something else happened: we can now assign such bugs to all packagers collectively. Doing so, now :-)

Assignee: bugsquad => pkg-bugs

Hi All
I have reproduced this as well and can't expand the error message. I increased the log level on sshd to verbose and still only got one line in journalctl on the server "sshd[3433]: Connection closed by 192.168.3.15 [preauth]"
This message suggests a timeout waiting for password but since it appears almost immediately it seems unlikely.

I have tried PyHoca-GUI as a client and it works well. Possibly a workaround until x2go client is sorted.
I will investigate further but I am by no means an expert.

Nic

CC: (none) => nic

I had no luck getting 4.0.1.3 to work but got 4.0.5.0 compiled and it dose not have the same problem. was able to compile it to an rpm using the original spec file whith only the version changed

CC: (none) => kangaroo800

I can confirm the observation of Simeon G. In my case I compiled with 4.0.5.1 and the connection problem was solved.

CC: (none) => Michael.Riss

Created attachment 8394 [details]
spec file to build with version 4.0.5.1 to solve the connection problems

The connection problems is solved with 4.0.5.1. Bug can be marked as "Resolved".

Status: NEW => RESOLVED
CC: (none) => phaleon
Resolution: (none) => FIXED

Actually, version 4.0.5.1 is not available in our repositories yet, so reopening the bug report.

Can someone tell if the bug is also present on Mageia cauldron too? It has the same x2go version as Mageia 5.

Status: RESOLVED => REOPENED
Resolution: FIXED => (none)

Hi all,

Thanks for having taken the needed time to report this issue, to do tests and, Michel, to even come with a working spec file 

We regret if this issue didn't get fixed in Mageia 5.

Mageia 5 has officially reached its End of Life on December 31st, 2017 https://blog.mageia.org/en/2017/11/07/mageia-5-eol-postponed/
It only continued to get important security updates since then, but non-security bugs have no chance of still getting fixed.

Fortunately, we have version 4.0.5.2 in Mageia 6.

Closing as OLD.

Status: REOPENED => RESOLVED
Resolution: (none) => OLD