Forum Replies Created
-
Posts
-
Adding to the article:
Don’t worry if xauth says “file /var/run/Xvfb-0.auth does not exist”. The file will be created at that time.
Just in case this puzzled you ;-).
I understand perfectly. I’m certainly not going to blame you. Finding where the problem can be it’s often difficult also for us ;-).
Please check the step 3. You must create that file using:
$ sudo xauth -f /var/run/Xvfb-0.auth add :0 . <16 digit cookie>
Did you check this?
Michal,
I’m sorry you decided to go back to the 3, especially because I don’t think what you experienced were really NoMachine problems. Anyway I’m afraid we can’t help you with the 3 version. This forum is only for the 4 users.
Dear Michal,
bear in mind that we are NOT going add “setxkbmap -rules evdev -layout
” to the user’s profile 😉 . We cannot incur in the risk of breaking things in a perfectly working environment just to solve a YAST, or some other Linux or Desktop Environment’s bug. There were a few selected cases we tried doing that in version 3, exactly to solve tricky keyboard problems, making things worse and confusing for some of the users. NX 4 is a clean-room implementation clearing the ground from all such workarounds (or at least ought to be). After disabling the iptables service on my installation (Centos 6.4 i686 +NX server (4.0.362) and Windows 7 64bit client) it works.
OK.
The ssh tunneling, as per link, also works, while the direct ssh does not, stating the ssh is not enabled on the server. Shouldn’t ssh be enalbled by default?
Yes, on servers that support it, like the Workstation version. The free version only supports NX connections and, if you look back, other replies stated that.
Also the session on the client asks me if I want to switch to NX protocol and does not present an option/button to generate a client side log.
The client says that SSH is not supported by the server and proposes to switch to the NX protocol. I think offering the option to download a bunch of verbose logs actually telling the same wouldn’t be any more user friendly.
Starting the player from another application is certainly possible and I don’t see any problem with that. Create a .nxs file on the fly in a temporary location and feed it to the player. Remove the .nxs when the client exits. Feel free to ask in this forum would you find any option whose operation is not obvious. Consider that there is no plan to offer all options present in the nxs on the command line. This should not be a problem, given it’s just a file everybody can parse with 3 lines of shell code, but of course one can write a nxs generator using something like this.
Let me know if you are working on some open source project or have any idea on how to integrate or extend the NoMachine functionalities. If we consider it useful, we’ll be happy to sponsor your effort.
I really hope this problem can be resolved. Anyway I suggest that all of you read and understand this:
has the behavior of the ‘free’ version of NXServer changed to compare with version 3.5 of NX Free Edition
Yes. The free version of NoMachine now works as traditional remote access software.
I log on and the session hangs/disconnects
Hmmm, it seems to me that it is working fine. As far as I can see it is not hanging or disconnecting.
It seems to me similar to what another user described recently on the forum.
I don’t think it’s the same problem. What is crashing here seems to be KDE, so the X server restarts (hence possibly the disconnect because there is no server anymore). Then, after the X server is restarted (by the system, because you are at runlevel 5) KDE hangs. Unfortunately I have seen problems like this many many times.
Nov 5 14:47:37 linux-ypbf nxexec: PAM unable to dlopen(/lib64/security/pam_pwcheck.so)
Nov 5 14:47:37 linux-ypbf nxexec: PAM [error: /lib64/security/pam_pwcheck.so: undefined symbol: pam_syslog]
Nov 5 14:47:37 linux-ypbf nxexec: PAM adding faulty module: /lib64/security/pam_pwcheck.soI checked with the author of the nxexec module and that message is just PAM not finding one of its modules (something outside our control). It’s not a crash. I don’t even think it’s a real problem. Probably just some PAM auth methods that can’t be used. Anyway if nxexec can’t use PAM it will fall back to shadow passwd. The remaining crashes are from KDE. This is not to say that it can’t be a NoMachine bug, of course. It’s just that it’s difficult to say from 1000 miles away. You should ensure that everything else is working, that your desktop environment runs 100% OK, that your KDE and Xorg and drivers are up-to-date. Debugging X problems is always a tedious process.
OK, interesting. I’m not sure we have the possibility to test on a OpenSUSE 10.3 and I’m not sure I understand what’s happening here but I’m passing the info.
Thanks.
It seems to me that NoMachine is running fine but the problem is that no desktop environment is running on that X display.
Try pointing at that display and run something, like xterm. See if the xterm window comes up and it is displayed correctly.
Are you sure you installed the the free version? Can you see what –version says?
> /usr/NX/bin/nserver –version
With the free version, the server should connect you to the local screen (:0) without returning the list first.
when I disconnect it it disconnects my own session
I don’t understand this, I’m afraid. Can you post a screenshot of what you see in the client?