Bugzilla – Bug 946643
x2goclient can't connect due to relocated nxproxy
Last modified: 2016-08-14 11:04:57 UTC
I just upgraded from nxproxy-3.5.0.27-5.1 to nxproxy-3.5.0.32-2.1. With this new version, x2goclient can no longer connect to a remote host. It gives the following error message: /usr/bin/nxproxy: line 29: /usr/lib/nx/bin/nxproxy: No such file or directory The problem seems to be that the binary command /usr/lib/nx/bin/nxproxy, which is referenced in the /usr/bin/nxproxy shell script, has moved to /usr/lib64/nx/bin/nxproxy. Possibly the packager of the nxproxy RPM moved the binary executable but forgot to update the corresponding reference to it in the shell script.
Seems fixed with latest patch. However still seeing errormessage: Verbindung fehlgeschlagen Can't locate File/Which.pm in @INC (you may need to install the File::Which module) (@INC contains: /usr/lib/perl5/site_perl/5.18.1/x86_64-linux-thread-multi /usr/lib/perl5/site_perl/5.18.1 /usr/lib/perl5/vendor_perl/5.18.1/x86_64-linux-thread-multi /usr/lib/perl5/vendor_perl/5.18.1 /usr/lib/perl5/5.18.1/x86_64-linux-thread-multi /usr/lib/perl5/5.18.1 /usr/lib/perl5/site_perl .) at /usr/bin/x2gomountdirs line 26. BEGIN failed--compilation aborted at /usr/bin/x2gomountdirs line 26.
The problem (or a closely related one) seems to affect x2goserver as well. I'm no longer able to connect to the upgraded machine using an X2Go client on another machine. However, in this case no error message is displayed; the connection simply terminates as soon as it's established.
(In reply to Matthias Gensler from comment #1) > Seems fixed with latest patch. Yes, I upgraded to nxproxy-3.5.0.32-3.1 (and also upgraded all other NX and X2Go packages) and the problem no longer occurs for me. > However still seeing errormessage: > > Verbindung fehlgeschlagen Can't locate File/Which.pm in @INC I don't experience this.
I added perl(File::Which) to the Requires.
Assuming this can be marked as FIXED now.