zaq

[zaq]

We sent the right link privately. Sorry.

[zaq]

Hello

Thank you for your cooperation. We prepared another debug package.

Could you reproduce again the problem and send us logs like in the previous case?

If it isn’t problem for you, could you download Process Explorer:
https://technet.microsoft.com/pl-pl/sysinternals/bb896653.aspx
When the installation freezes again in Process Explorer check ‘nxserver’ processes:

1. Click the right mouse button.
2. Choose ‘Properties’.
3. Choose ‘Threads’.
4. Maximize the window and do screenshot.

Please send the screenshots together with logs.

[zaq]

Thank you for the logs. Unfortunately the log dir
which you sent doesn’t contain logs from installation.
Logs have timestamps day after an installation. Could
you reproduce the problem again and gather log dir
right after installation (~10 min. after the freez)?
Please send also Setup-Log… like previous.

[zaq]

Hi lexcorp

Could you use this debug installation package to reproduce the problem:

(sent link privately)

Then pack the log dir:

Documents and Settings/All Users/NoMachine/var/log

and send the dir and a installation log file (Setup…) to:

forum[at]nomachine[dot]com

Thank you

• This reply was modified 9 years, 5 months ago by zaq.

[zaq]

Hello,

It is a quick fix:

1. Comment out a  line with the ‘DefaultDesktopCommand’ key in /usr/NX/etc/node.cfg.

Only add in the beginning of the line ‘#’.
2. Add below old key:

DefaultDesktopCommand “/etc/gdm/Xsession ‘gnome-session
–session=gnome'”

If this doesn’t help you, could you prepare more logs for us:
1. Uncomment ‘SessionLogLevel’ in /usr/NX/etc/server.cfg and set a value 7:

before:
#SessionLogLevel 6

after:
SessionLogLevel 7

2. After that restart nxserver:

sudo /usr/NX/bin/nxserver –restart

3. Reproduce the problem (try to run a new virtual desktop)

4. Send to NoMachine:
– /var/log/syslog
– /var/log/Xorg.*.log
– home $HOME/.xsession-errors
– /usr/NX/var/log dir.

• This reply was modified 9 years, 6 months ago by Britgirl.

[zaq]

Dear bhupiss,

Could you answer on below questions:

– Which type of Windows do you use (Win8,Win7,…, x32/x64)?

– Which version of NoMachine you installed before the update?

– Which version of NoMachine did you use to do the update?

– Do you have on the machine alone NoMachine Client or also
NoMachine Server?

[zaq]

Dear krusher,

Upgrade from older versions to NoMachine 4 is supported only for NX 3.5.0.
We have verified that there can be problems when upgrading from version 3.4.0 to 4.
We strongly advise to uninstall your current installation, remove the /usr/NX directory
and proceed with a fresh new install of NoMachine (free) 4.4.12.

[zaq]

Hi,

Could you tell me, when did you get the empty AvailableSessionTypes problem, please?

Did you add the line yourself or did it happen during an update/installation process?

If you aren’t sure or if it happened during a setup, could you send the compressed log dir:

/usr/NX/var/log

to

forum[at]nomachine[dot]com

Thank you

[zaq]

Hello,
Could you try to update to 4.4.6, please? There is a fix for SELinux
Fedora 21.
If the issue persists please gather debug information following the
instructions here:

https://www.nomachine.com/AR07K00677

Also please save active processes:

ps -Af | grep nx > processes.txt

Send debug information and ‘processes.txt’ to issues[at]nomachine[dot]com.

[zaq]

Hello,

We aren’t able to reproduce your problem in our lab. We need more
details. Could you answer the questions which you skipped previously, please?

1. Is your Norton AV set at the default configuration. If not, what has changed?
2. Is there any clue as to which NoMachine file Norton AV treats as dangerous.
Is it the installation package “nomachine_4.4.6_11.exe”(md5sum:
7d9f1515598b562a0c61dcdc526a3a05)?
3. Could you export the Norton report and send to us please?
Anyway you can try to install once more NoMachine and check if your
problem happens again. Please send attachments to forum[at]nomachine[dot]com.

[zaq]

Hello,

We aren’t able to reproduce your problem in our lab. Could you tell me more details, please?

1. Which version of NoMachine are you using? A full installation package name is enough.

2. Which version of Norton AV do you have installed?
In this link it tells you how to find the version:
https://support.norton.com/sp/pl/pl/home/current/solutions/kb20080417101717EN_EndUserProfile_en_us

3. Is your Norton AV set at the default configuration If not, what has changed?

4. Is there any clue as to which NoMachine file Norton AV treats as dangerous.

5. Which operating system do you have? (Windows XP, Windows Vista …; x64 or x32)

6. Could you export the Norton report and send to us please?
How to find the report:
https://support.norton.com/sp/en/us/home/current/solutions/v23920762_NAV_Retail_2014_en_us

[zaq]

Hello,

The free version of NoMachine doesn’t support SSH connections. You should check point 1.3 of the installation guide:

https://www.nomachine.com/DT09K00056

TR06J02727 is related to the a very early beta version of NoMachine, which supported the SSH protocol.

In answer to your questions, when you use a NoMachine product with SSH support then:

1. In /var/NX/nx/.ssh/known_host is a public key.
Files: default.id_dsa.pub and restore.id_dsa.pub are only backups.

2. The privet key of a user nx is in: /usr/NX/share/keys/server.id_dsa.key

[zaq]

Hello,

The free version of NoMachine doesn’t support SSH connections. You should check point 1.3 of the installation guide:

https://www.nomachine.com/DT09K00056

This is why ‘nxserver –checkssh reports an error. This is used by other NoMachine products, which support the SSH protocol.

Instead of using ‘nxserver –checkssh’ to verify your installation you can use:

/etc/NX/bin/nxserver –status

The output of the command should be:

NX> 161 Enabled service: nxserver.
NX> 161 Enabled service: nxnode.
NX> 161 Enabled service: nxd.

In the case of NoMachine (free), ‘–checkssh’ is unnecessary but harmless. We will remove it.

[zaq]

Hi,

We have reproduced your issue. We have inserted a new Trouble Report at http://www.nomachine.com/TR06L04470. We will fix this problem in the next release.

[zaq]

Hi,

We reproduced the issue related with the main menu in our test laboratory. We also have a workaround for it:

In file:

/usr/share/desktop-directories/NoMachine-dir.directory

Change the line from:

‘Comment=’

to

‘Comment=NoMachine’

This should be enough. If not then log out and log in.

We will fix this issue in the next release.

[Author]

Posts