I’m trying to log into an LXDE workstation over FreeNX/NX. I’ve recently upgraded from 11.4 to 12.1. New users created after the upgrade can log in while users that existed on 11.4 cannot.
The NX authentication succeeds and the !M window appears for about 3 or 4 seconds, then disappears. Looking in the ~/.nx/C-host-xxxx/sessions file shows the following errors below. Also a core file appears in the user’s home directory, but I don’t know how to analyze it.
Any ideas on what is failing and how to fix it?
Info: Established X client connection.
Info: Using shared memory parameters 1/1/0/0K.
*** glibc detected *** /usr/lib/NX/nxagent: free(): invalid pointer: 0x084f0e48
======= Backtrace: =========
/lib/libc.so.6(+0x6ed8b)[0xb73a0d8b]
/lib/libc.so.6(cfree+0x9b)[0xb73a528b]
/usr/lib/NX/nxagent[0x80b4830]
/usr/lib/NX/nxagent[0x80b5c5e]
/usr/lib/NX/nxagent[0x80c2e9d]
/usr/lib/NX/nxagent[0x80543c9]
/lib/libc.so.6(__libc_start_main+0xf3)[0xb734b003]
/usr/lib/NX/nxagent[0x8054cd9]
======= Memory map: ========
…
Warning: Parent process appears to be dead. Exiting keeper.
xrdb: Connection refused
xrdb: Can’t open display ‘:1002’
Further debugging has shown that the problem is not with xrdb. The xrdb errors appear to be symptoms/side-effects of a problem with /usr/lib/NX/nxagent.
I noticed - in your other posts already - that you can not access display 1002. I wonder if there is not a lock on that particular display (from an older session). Maybe you could try to change DISPLAY_BASE in node.conf from 1000 to something else (for example 2000) and restart the NX server, then see what happens when your client tries to access display 2000+n (or if it still insists on opening display 1002).
And again - I don’t know if I suggested that already - you should try to connect as the same user (the one who cannot connect) from another computer (to exclude problems on that client’s side).
The display increments by one each time I try to connect, so I don’t think stale lock files are a problem. I also have /tmp clear itself each boot to try to prevent that.
Can you make sure that both FreeNX and NX packages are from the same repo? Use
zypper info FreeNX
zypper info NX
FreeNX 0.7.3-22.1 and NX 3.4.0-83.1 are the ones I have at the moment in my repo. They run on several 11.4 machines, one 32bit an another 64bit 12.1 systems.
I assume you already set the maximum verbosity for server log in node.conf. If not, set
NX_LOG_LEVEL=7
Not sure it will help, but you can try to install NoMachine NX (as well) and run it on a different SSH port while FreeNX remains the main server and will just forward incoming connections on this port to the NoMachine server. NoMachine free edition is limited to one client connection.
If you want to try that - again not sure it will help - I can explain you how to run them in parallel. It’s not extremely complicated (but you’ll have to manually remove the nx user prior to NoMachine installation).