Forum Replies Created
-
Posts
-
Hello zSeries.
can you send the client and server log files? You can gather logs in this way:
Create a compressed archive of the NoMachine /var/log directory
The NoMachine /var/log directory on Linux is: /usr/NX/var/log. Create a compressed archive (tar.gz) archive from command line.
Run a terminal and move to /usr/NX/var :
$ cd /usr/NX/var/
$ sudo tar cvfz NoMachine-log.tar.gz log
Create a compressed archive of the .nx directory in the user’s homeRun from a terminal:
$ tar -cvp –exclude ‘cache*’ –exclude ‘images’ –exclude ‘recording’ -f – $HOME/.nx | gzip -c >nxdir.tar.gz
How to gather client side logs
Run from a terminal:
$ tar -cvp –exclude ‘cache*’ –exclude ‘images’ –exclude ‘recording’ -f – $HOME/.nx | gzip -c >nxdir.tar.gz
Hello.
May I ask you for mode information:
Does it occur with any client platform you tried (Windows, Ubuntu, CentOs)?
Does it show up accessing an existing desktop or using a virtual desktop session?
Is the target Fedora 12 desktop KDE or Gnome?
Is there any clipboard manager running in the Fedora 12 desktop (e.g. klipboard in KDE)?
Could you send client and server logs of an affected session?
nxlier,
could you provide more information about Windows and Outlook version:
– Is Windows 7 the 32 or 64-bit version? With or without Service Pack 1?
– Is Outlook 2013 the 32 or 64-bit version?
Hello,
are you experiencing those problems in a physical or virtual display?
Have you tried restarting the server rather than rebooting (/usr/NX/bin/nxserver –restart)?We had issues in the past with window managers grabbing the mouse and never releasing, so try also this one: compiz –restart
If you want to provide log files, please create a tarball including:
– the directory $HOME/.nx
– the directory /usr/NX/var/log
Geekazoid,
this issue looks very specific to some SUSE Linux distribution versions. For some reason, modules pam_unix.so and pam_unix2.so are not
linked to libpam.so. This looks solved in more recent versions of SUSE.It will be fixed in the next release.
hchan, it looks that authentication stage simply hangs and it is killed after a 20 seconds timeout. Do you have SELinux or similar protection running on your server? You can try to temporary set SELinux in permissive mode using the command:
# setenforce 0
Geekazoid, we are investigationg your issue to find why the load of PAM module fails. Could you check the PAM configuration of command “su” (look at files /etc/pam.d/su or /etc/security/pam.d/su) and if the “su” command works as expected?
Can you tell us what version of NoMachine you are connecting to and what language and model you want to use fo the keyboard? As far as we are aware there are no keyboard issues on the latest version.
NoMachine client doesn’t emulate the right mouse button using the ctrl key, because this would affect the remote applications that actually interpret ctrl+click as a command. I suggest changing the trackpad settings to emulate the right click in a different way (for example using two fingers).
Hello.
Could you post the messages printed in /usr/NX/var/log/nxerror.log? They would give us hints about the reason of the authentication failure.
Hello.
In version 4, fonts are not necessary, unless you are running NoMachine in single application (floating window) mode. Or are you connecting to a 3.5 server?
Hello.
In http://pastebin.com/1xVjAR4k, shouldn’t it be
ubuntu@ip-172-31-15-216:~$ DISPLAY=:0 /etc/X11/Xsession xfce4-session
I’m guessing you want to launch the Xfce desktop.