graywolf

[graywolf]

Hello, the authorization requires a local account belonging to the sudoers group or the root account. If that doesn’t help, please create archives with server-side log files :

sudo tar zcf NoMachine-log.tar.gz /usr/NX/var/log
tar zcf nxdir.tar.gz $HOME/.nx

and gather the output of the command:
sudo -l -U {username} > sudo.txt.

Please senda data to: forum at nomachine dot com.

[graywolf]

Could you provide a screenshot showing the image quality that made you switch to ProxyExtraOptions pack=16m-png?
It is possible that tweak also affected performace. Do you experience the same keyboard delays if you removed it?
Is AgentX11VectorGraphics to its default value (AgentX11VectorGraphics 1)?

[graywolf]

Hello, would you show the output of the following commands issued in a terminal window running in the virtual desktop:

setxkbmap -print > setxkbmap.txt
setxkbmap -query > layout.txt
xprop -root | grep XKB > xprop.txt
xmodmap -pke > xmodmap.txt
xkbcomp -xkb $DISPLAY - > xkbcomp.txt

[graywolf]

Hello.

Likely the xmodmap command is launched before the keybord setup is completed in the remote session. Some key is already defined as modifier (e.g. Meta_L could be in use as Mod1) so the “add” expression fails.

You could take in account and change the script accordingly, but I think it’d be better if .cshrc is modified to avoid launching xmodmap in the case of remote NoMachine session, i.e.

if ( ! $?NX_SESSION_ID ) xmodmap ~/.Xmodmap

In the remote NoMachine session you can instruct NoMachine to run a custom script: use UserScriptAfterSessionStart and UserScriptAfterSessionReconnect in node.cfg.

Here you find some examples to create a custom script: Some examples to use custom scripts triggered on server and node events

[graywolf]

You need to add the “trusted” qualification to your user profile in order to get access to the login screen. Try this:

/etc/NX/nxserver --useredit <username> --trusted physical

[graywolf]

Update.

The problem looks fixed in the latest version (6.3.6). Would you upgrade rather than patching v. 6.2.4 ?

[graywolf]

Likely we found the source of the problem. We’ll send you a library that should fix it.

[graywolf]

Could you check if any crash is reported by the command

sudo apport-cli

May I look at the lightdm process tree when nobody is logged in the physical console? This command should be able to dump it:

pstree $(ps --ppid 1 | grep lightdm | awk '{print $1}')

[graywolf]

Server logs don’t say very much. Could you search the systemd journal for errors? Just run the command
journalctl

You can restict the search to the last boots using the option -b:
journalctl -b -0 (the last boot)
journalctl -b -1 (the boot before last)
journalctl -b -2 (and so on)

[graywolf]

Which version of NoMachine are you using?

In order to disable automatic startup of NoMachine on boot, get a shell as first thing. If you are next to the server, just type key-combo Ctrl+Alt+Fn (where Fn = F2 or F3 or F4 …).

After you logged in and got the shell, type the command:

/usr/NX/bin/nxserver --startmode manual

then reboot the system with
reboot

Could you create an archive of /usr/NX/var/log folder? Use the command
tar zcvf NoMachineLogs.tar.gz /usr/NX/var/log

then send the file NoMachineLogs.tar.gz to the email address: forum[at]nomachine[dot]com

[graywolf]

Is the server headless? In that case you could turn off display manager and let NoMachine create its own virtual display:

sudo systemctl stop gdm (turns display manager off)

sudo systemctl disable gdm (disables display manger start on boot)

[graywolf]

Could you create an archive of folder /usr/NX/var/log ?

Could you check if any crash file is created in /var/crash?

Please, send everything to the email address forum[at]nomachine[dot]com.

[graywolf]

Please create an archive of folder /usr/NX/var/log and send it by email.

[graywolf]

“Physical display gdm, Ubuntu X server on :1024” seems correct. Did you try to double-click that icon?

[graywolf]

Please, reproduce with SessionLogClean 0 (node.cfg) so session folders in /usr/NX/var/log/node are not removed. Could you then send the whole folder /usr/NX/var/log ?

[Author]

Posts