There are some NX-3.0.0 RPMS that currently seem to work OK with the current freenx (0.6.0-13) backend (for centos-5).
They do not do all the new things that nx-3.0 can do (we are waiting on a new freenx that does those things) ... however this version does compile on x86_64 (and there is also a version of freenx for x86_64 as well).
Currently there is a symlink to /usr/lib/NX for 64bit OSes as well ... but that also should be cleared up when the new FreeNX is released.
For anyone who wants native x86_64 support, these should be OK, at least for testing.
Thanks, Johnny Hughes
On Thu, 2007-06-28 at 07:41 -0500, Johnny Hughes wrote:
There are some NX-3.0.0 RPMS that currently seem to work OK with the current freenx (0.6.0-13) backend (for centos-5).
They do not do all the new things that nx-3.0 can do (we are waiting on a new freenx that does those things) ... however this version does compile on x86_64 (and there is also a version of freenx for x86_64 as well).
Currently there is a symlink to /usr/lib/NX for 64bit OSes as well ... but that also should be cleared up when the new FreeNX is released.
For anyone who wants native x86_64 support, these should be OK, at least for testing.
They are in the testing REPO ... since I did not mention that :D
On 6/28/07, Johnny Hughes mailing-lists@hughesjr.com wrote:
There are some NX-3.0.0 RPMS that currently seem to work OK with the current freenx (0.6.0-13) backend (for centos-5).
They do not do all the new things that nx-3.0 can do (we are waiting on a new freenx that does those things) ... however this version does compile on x86_64 (and there is also a version of freenx for x86_64 as well).
Currently there is a symlink to /usr/lib/NX for 64bit OSes as well ... but that also should be cleared up when the new FreeNX is released.
For anyone who wants native x86_64 support, these should be OK, at least for testing.
I am testing it on a C5 x86_64 machine. First, I needed to uninstall the existing nx-2.x to install the new nx-3.x. Otherwise, I get an error:
unpacking of archive failed on file /usr/lib/NX: cpio: rename
Now, nx-3 has been installed but does not work. I get connected but with a black screen. After 1 minute or so, the whole thing disappears.
Any suggestions?
Akemi
On 6/28/07, Akemi Yagi amyagi@gmail.com wrote:
On 6/28/07, Johnny Hughes mailing-lists@hughesjr.com wrote:
There are some NX-3.0.0 RPMS that currently seem to work OK with the current freenx (0.6.0-13) backend (for centos-5).
I am testing it on a C5 x86_64 machine. First, I needed to uninstall the existing nx-2.x to install the new nx-3.x. Otherwise, I get an error:
unpacking of archive failed on file /usr/lib/NX: cpio: rename
Now, nx-3 has been installed but does not work. I get connected but with a black screen. After 1 minute or so, the whole thing disappears.
Any suggestions?
Akemi
Tested on a C5 i386 box that had never seen nx before. Exactly the same symptom as the x86_64 box above. Authentication completes but just black screen. :(
Akemi
On Thu, Jun 28, 2007 at 04:32:41PM -0700, Akemi Yagi wrote:
On 6/28/07, Akemi Yagi amyagi@gmail.com wrote:
On 6/28/07, Johnny Hughes mailing-lists@hughesjr.com wrote:
There are some NX-3.0.0 RPMS that currently seem to work OK with the current freenx (0.6.0-13) backend (for centos-5).
I am testing it on a C5 x86_64 machine. First, I needed to uninstall the existing nx-2.x to install the new nx-3.x. Otherwise, I get an error:
unpacking of archive failed on file /usr/lib/NX: cpio: rename
Now, nx-3 has been installed but does not work. I get connected but with a black screen. After 1 minute or so, the whole thing disappears.
Any suggestions?
Akemi
Tested on a C5 i386 box that had never seen nx before. Exactly the same symptom as the x86_64 box above. Authentication completes but just black screen. :(
Do you have bash-completion installed? Could you remove it?
On 6/29/07, Axel Thimm Axel.Thimm@atrpms.net wrote:
On Thu, Jun 28, 2007 at 04:32:41PM -0700, Akemi Yagi wrote:
On 6/28/07, Akemi Yagi amyagi@gmail.com wrote:
On 6/28/07, Johnny Hughes mailing-lists@hughesjr.com wrote:
There are some NX-3.0.0 RPMS that currently seem to work OK with the current freenx (0.6.0-13) backend (for centos-5).
I am testing it on a C5 x86_64 machine. First, I needed to uninstall the existing nx-2.x to install the new nx-3.x. Otherwise, I get an error:
unpacking of archive failed on file /usr/lib/NX: cpio: rename
Now, nx-3 has been installed but does not work. I get connected but with a black screen. After 1 minute or so, the whole thing disappears.
Any suggestions?
Akemi
Tested on a C5 i386 box that had never seen nx before. Exactly the same symptom as the x86_64 box above. Authentication completes but just black screen. :(
Do you have bash-completion installed? Could you remove it?
Axel.Thimm at ATrpms.net
I don't have bash-completion installed (client, server). Could you elaborate? How is bash-completion related here?
Akemi
On Thu, Jun 28, 2007 at 04:32:41PM -0700, Akemi Yagi wrote:
On 6/29/07, Axel Thimm Axel.Thimm@atrpms.net wrote:
Do you have bash-completion installed? Could you remove it?
Axel.Thimm at ATrpms.net
I don't have bash-completion installed (client, server). Could you elaborate? How is bash-completion related here?
There used to be a bug where bash-completion would stop freenx from working (causing similar effects as you described). This doesn't seem to be case anymore (I tested with newest server/client rpm's from nomachine).
Seán
On 6/29/07, Seán O Sullivan seanos@seanos.net wrote:
On Thu, Jun 28, 2007 at 04:32:41PM -0700, Akemi Yagi wrote:
On 6/29/07, Axel Thimm Axel.Thimm@atrpms.net wrote:
Do you have bash-completion installed? Could you remove it?
Axel.Thimm at ATrpms.net
I don't have bash-completion installed (client, server). Could you elaborate? How is bash-completion related here?
There used to be a bug where bash-completion would stop freenx from working (causing similar effects as you described). This doesn't seem to be case anymore (I tested with newest server/client rpm's from nomachine).
Thanks Johnny, Axel and Seán for your notes. Looks like I am the only one who cannot get the 3.x version to work. I will continue to look for the cause but am totally at a loss at this moment.
Akemi
On 6/29/07, Akemi Yagi amyagi@gmail.com wrote:
Thanks Johnny, Axel and Seán for your notes. Looks like I am the only one who cannot get the 3.x version to work. I will continue to look for the cause but am totally at a loss at this moment.
OK, I've made some progress. I created a new user (and named it "johnny") on the server and was able to connect as johnny. Hmm.. the name "johnny" must have some magical power. :D
I am currently checking what in my shell is the source of the problem. I had previously removed ~/.nx but that had no effect. So, it must be something of more general nature.
Akemi
On 6/29/07, Akemi Yagi amyagi@gmail.com wrote:
OK, I've made some progress. I created a new user (and named it "johnny") on the server and was able to connect as johnny. Hmm.. the name "johnny" must have some magical power. :D
I am currently checking what in my shell is the source of the problem. I had previously removed ~/.nx but that had no effect. So, it must be something of more general nature.
Got it working! Not only I needed the 3.x client as Johnny pointed out, but I had to run the Connection Wizard. [Was using the existing icon on my Desktop]. My bad. Sorry for the hubbub on this ML.
Akemi
Akemi Yagi wrote:
On 6/29/07, Akemi Yagi amyagi@gmail.com wrote:
OK, I've made some progress. I created a new user (and named it "johnny") on the server and was able to connect as johnny. Hmm.. the name "johnny" must have some magical power. :D
I could have told you that name would make it work :D
I am currently checking what in my shell is the source of the problem. I had previously removed ~/.nx but that had no effect. So, it must be something of more general nature.
Got it working! Not only I needed the 3.x client as Johnny pointed out, but I had to run the Connection Wizard. [Was using the existing icon on my Desktop]. My bad. Sorry for the hubbub on this ML.
That is all good info though, we can get it in the wiki later.
Akemi Yagi wrote:
I am testing it on a C5 x86_64 machine. First, I needed to uninstall the existing nx-2.x to install the new nx-3.x. Otherwise, I get an error:
unpacking of archive failed on file /usr/lib/NX: cpio: rename
the prev nx-2.x was a i386 package, the nx-3 one is x86_64, but rpm does not like dir's changing to symlinks iirc, which might be the cause of this issue.
Now, nx-3 has been installed but does not work. I get connected but with a black screen. After 1 minute or so, the whole thing disappears.
anything interesting in the nxsever logs ? if not, try setting up your node.conf and turn on logging to debug level and see ( this is on the server end )
Also, what client version are you using ? Is the client installed on the server end as well ?
- KB
On 6/28/07, Karanbir Singh mail-lists@karan.org wrote:
Akemi Yagi wrote:
I am testing it on a C5 x86_64 machine. Now, nx-3 has been installed but does not work. I get connected but with a black screen. After 1 minute or so, the whole thing disappears.
anything interesting in the nxsever logs ? if not, try setting up your node.conf and turn on logging to debug level and see ( this is on the server end )
/var/log/nxserver.log is empty. Will try debugging.
Also, what client version are you using ? Is the client installed on the server end as well ?
client version is nxclient-2.1.0-17.i386. client is not installed on the server.
Akemi
On 6/28/07, Akemi Yagi amyagi@gmail.com wrote:
On 6/28/07, Karanbir Singh mail-lists@karan.org wrote:
Akemi Yagi wrote:
I am testing it on a C5 x86_64 machine. Now, nx-3 has been installed but does not work. I get connected but with a black screen. After 1 minute or so, the whole thing disappears.
anything interesting in the nxsever logs ? if not, try setting up your node.conf and turn on logging to debug level and see ( this is on the server end )
/var/log/nxserver.log is empty. Will try debugging.
Also, what client version are you using ? Is the client installed on the server end as well ?
client version is nxclient-2.1.0-17.i386. client is not installed on the server.
I have turned debugging on. Here are some lines from /var/log/nxserver.log:
(after successful logging in) NX> 1000 NXNODE - Version 1.5.0-60 OS (GPL) NX> 700 Session id: server.name.here-1000-F674848DB47BBE6AC0E40B8D03BAE14C NX> 705 Session display: 1000 NX> 703 Session type: unix-kde NX> 701 Proxy cookie: 31e555a2c4487ae9b5a2893143f3d5b0 NX> 702 Proxy IP: 127.0.0.1 NX> 706 Agent cookie: 31e555a2c4487ae9b5a2893143f3d5b0 NX> 704 Session cache: unix-kde NX> 707 SSL tunneling: 1 NX> 1009 Session status: starting NX> 710 Session status: running NX> 1002 Commit NX> 1006 Session status: running NX> 105 bye Bye NX> 999 Bye NX> 1009 Session status: terminating NX> 1006 Session status: closed NX> 1001 Bye.
So many bye bye's! I have also installed client on the server. This did not make any difference.
Akemi
On Thu, 2007-06-28 at 17:26 -0700, Akemi Yagi wrote:
On 6/28/07, Akemi Yagi amyagi@gmail.com wrote:
On 6/28/07, Karanbir Singh mail-lists@karan.org wrote:
Akemi Yagi wrote:
I am testing it on a C5 x86_64 machine. Now, nx-3 has been installed but does not work. I get connected but with a black screen. After 1 minute or so, the whole thing disappears.
anything interesting in the nxsever logs ? if not, try setting up your node.conf and turn on logging to debug level and see ( this is on the server end )
/var/log/nxserver.log is empty. Will try debugging.
Also, what client version are you using ? Is the client installed on the server end as well ?
client version is nxclient-2.1.0-17.i386. client is not installed on the server.
I have turned debugging on. Here are some lines from /var/log/nxserver.log:
(after successful logging in) NX> 1000 NXNODE - Version 1.5.0-60 OS (GPL) NX> 700 Session id: server.name.here-1000-F674848DB47BBE6AC0E40B8D03BAE14C NX> 705 Session display: 1000 NX> 703 Session type: unix-kde NX> 701 Proxy cookie: 31e555a2c4487ae9b5a2893143f3d5b0 NX> 702 Proxy IP: 127.0.0.1 NX> 706 Agent cookie: 31e555a2c4487ae9b5a2893143f3d5b0 NX> 704 Session cache: unix-kde NX> 707 SSL tunneling: 1 NX> 1009 Session status: starting NX> 710 Session status: running NX> 1002 Commit NX> 1006 Session status: running NX> 105 bye Bye NX> 999 Bye NX> 1009 Session status: terminating NX> 1006 Session status: closed NX> 1001 Bye.
So many bye bye's! I have also installed client on the server. This did not make any difference.
Akemi
The 3.0.0 server may not work with the 2.1.0 client ...
Try the 3.0.0 client on the machine connection to the server.
On Fri, 2007-06-29 at 04:34 -0500, Johnny Hughes wrote:
On Thu, 2007-06-28 at 17:26 -0700, Akemi Yagi wrote:
On 6/28/07, Akemi Yagi amyagi@gmail.com wrote:
On 6/28/07, Karanbir Singh mail-lists@karan.org wrote:
Akemi Yagi wrote:
I am testing it on a C5 x86_64 machine. Now, nx-3 has been installed but does not work. I get connected but with a black screen. After 1 minute or so, the whole thing disappears.
anything interesting in the nxsever logs ? if not, try setting up your node.conf and turn on logging to debug level and see ( this is on the server end )
/var/log/nxserver.log is empty. Will try debugging.
Also, what client version are you using ? Is the client installed on the server end as well ?
client version is nxclient-2.1.0-17.i386. client is not installed on the server.
I have turned debugging on. Here are some lines from /var/log/nxserver.log:
(after successful logging in) NX> 1000 NXNODE - Version 1.5.0-60 OS (GPL) NX> 700 Session id: server.name.here-1000-F674848DB47BBE6AC0E40B8D03BAE14C NX> 705 Session display: 1000 NX> 703 Session type: unix-kde NX> 701 Proxy cookie: 31e555a2c4487ae9b5a2893143f3d5b0 NX> 702 Proxy IP: 127.0.0.1 NX> 706 Agent cookie: 31e555a2c4487ae9b5a2893143f3d5b0 NX> 704 Session cache: unix-kde NX> 707 SSL tunneling: 1 NX> 1009 Session status: starting NX> 710 Session status: running NX> 1002 Commit NX> 1006 Session status: running NX> 105 bye Bye NX> 999 Bye NX> 1009 Session status: terminating NX> 1006 Session status: closed NX> 1001 Bye.
So many bye bye's! I have also installed client on the server. This did not make any difference.
Akemi
The 3.0.0 server may not work with the 2.1.0 client ...
Try the 3.0.0 client on the machine connection to the server.
The 3.0.0 client seems to connect OK to the a nx-2.1.0 / freenx-0.6.0 machine too.
I did install both the i386 and x86_64 versions of mx-3.0.0 to newly installed machines and connected with the 3.0.0 nomachine client from Linux and Windows.
I also connected from the same 3.0.0 clients (on windows and linux) to a nx-2.1.0 / freenx-0.6.0 machine.
On 6/29/07, Johnny Hughes mailing-lists@hughesjr.com wrote:
On Thu, 2007-06-28 at 17:26 -0700, Akemi Yagi wrote:
On 6/28/07, Akemi Yagi amyagi@gmail.com wrote:
On 6/28/07, Karanbir Singh mail-lists@karan.org wrote:
Akemi Yagi wrote:
I am testing it on a C5 x86_64 machine. Now, nx-3 has been installed but does not work. I get connected but with a black screen. After 1 minute or so, the whole thing disappears.
anything interesting in the nxsever logs ? if not, try setting up your node.conf and turn on logging to debug level and see ( this is on the server end )
/var/log/nxserver.log is empty. Will try debugging.
Also, what client version are you using ? Is the client installed on the server end as well ?
client version is nxclient-2.1.0-17.i386. client is not installed on the server.
The 3.0.0 server may not work with the 2.1.0 client ...
Try the 3.0.0 client on the machine connection to the server.
After my last message above, I did try connecting from a 3.0.0 client:
rpm -qf `which nxclient` nxclient-3.0.0-65.i386
But I got the same problem.
Akemi
Hi Johnny,
On Thu, Jun 28, 2007 at 07:41:20AM -0500, Johnny Hughes wrote:
There are some NX-3.0.0 RPMS that currently seem to work OK with the current freenx (0.6.0-13) backend (for centos-5).
They do not do all the new things that nx-3.0 can do (we are waiting on a new freenx that does those things) ... however this version does compile on x86_64 (and there is also a version of freenx for x86_64 as well).
Currently there is a symlink to /usr/lib/NX for 64bit OSes as well ... but that also should be cleared up when the new FreeNX is released.
For anyone who wants native x86_64 support, these should be OK, at least for testing.
64 bit support was available for 2.1.x in form of patches, and I had also given my best to use FHS across nx/freenx. Would you like to check out http://atrpms.net/name/nx/ and http://atrpms.net/name/freenx/ (contains support for CentOS-4 and 5) and take over/sync any valuable stuff?
BTW I've been trying to split the src.rpm into one src.rpm per tarball (makes upgrading to minor NX releases easier, as well as using self-made nxagent solutions). This isn't done, yet, but would you be interested in hammering this package together to its bits?
-
Akemi Yagi -
Axel Thimm -
Johnny Hughes -
Johnny Hughes -
Karanbir Singh -
Seán O Sullivan