zaq

[zaq]

Hello,

I can see that you use package for 32 bit OS. Could you confirm that you have x32 Ubuntu?
Please run in terminal:

uname -a

uname -p

or in Unity Search:

System Settings -> Details -> Overview -> OS type

if in output you find i686 or 32-bit, please send to forum[at]nomachine[dot]com
output from installation and a packed log directory:

/usr/NX/var/log

If you have 64 bit OS, please try:

https://www.nomachine.com/download/download&id=1

sudo dpkg -i nomachine_5.1.44_1_amd64.deb

• This reply was modified 8 years, 2 months ago by zaq.

[zaq]

Hello Hugga,

Do you use on your PCs Active Directory or similar technology?
Is ‘nx’ a domain user?

Could you zip whole log dir on both machines (PC1,PC2):

C:\ProgramData\NoMachine\var\log

and sent to forum[at]nomachine[dot]com, please.

[zaq]

Hello Greenrose,

Could you zip whole log dir:

C:\ProgramData\NoMachine\var\log

and sent to forum[at]nomachine[dot]com, please.

Is it something unusual in settings of your PC?
Is the OS installed on a USB drive? Is it a virtual machine?

[zaq]

Hello Canufrank

Looks like your computer processor is 32-bit. NoMachine needs 64-bit CPU.

You can check this by run in terminal:

1. CPU name:

sysctl -n machdep.cpu.brand_string

“Core Solo” or “Core Duo” CPU it’s 32-bit only

2. Check if your CPU supports 64-bit:

sysctl hw.cpu64bit_capable

[zaq]

Hi,

open a terminal and tell me the output of this command:

sw_vers

uname -a

If the output of ‘uname’ includes i386 or x86please send also this packed dir:

tar czf log.tar.gz /Library/Application\ Support/NoMachine/var/log/

Please use this e-mail:

forum[at]nomachine[dot]com

if they are too large to attach in the forums.

[zaq]

Hello,

We have prepared a debug package and can send you the link.

Please send logs from the installation, even when everything will be ok:

forum[at]nomachine[dot]com

[zaq]

Hello,

You can use this command as a workaround:

sudo bash -c "echo \"manual\" > /etc/init/nxserver.override"

This will be fixed in the next release.
You can track this issue by enabling “Notify me when the TR is closed.”:
https://www.nomachine.com/TR01N06343

[zaq]

Hello,

Looks like you uninstalled partially your previous version of NoMachine.
The right uninstall command is:

sudo dpkg -r nomachine

When you do update, uninstallation isn’t necessary.

In your situation you can do this:

1) sudo dpkg -r nomachine

2) sudo rm -rf /usr/NX /etc/NX /var/NX

3) sudo dpkg -i nomachine_5.0.63_1_amd64.deb

• This reply was modified 8 years, 10 months ago by zaq.
• This reply was modified 8 years, 10 months ago by zaq.

[zaq]

Hello Jenefa

You most likely used ‘sudo’ a few commands earlier. Remember that
usually ‘sudo’ doesn’t prompt for password again if you’ve already
entered it. Password prompts depend of your OS configuration.
Are you sure that you use appropriate package for your OS architecture?
Packages ‘amd64’ for 64 bits and packages ‘i386’ for 32 bits.

The right command to install NoMachine Free on Ubuntu x64 is:

sudo dpkg -i nomachine_5.0.53_1_amd64.deb

More about NoMachine’s installation you can find in:

https://www.nomachine.com/DT07M00078&dn=

Are you sure that nxserver isn’t running? Do you see NoMachine Monitor
in your system tray? It’s a white-grey icon with ‘!M’ near system’s
clock.
If you don’t see it, could you check OS processes by run this command
in terminal:

ps aux | grep nx

Basics of NoMachine you can find here:

https://www.nomachine.com/getting-started-with-nomachine

[zaq]

Hello,

Unfortunately it’s a bug. It’ll be fixed in a next release.
Old kext wasn’t replaced during update.

As a workaround you can do this:

1. Uninstall NoMachine:

sudo rm -rf /Applications/NoMachine.app

2. Install again the newest package.

[zaq]

Hello,

In your case you shouldn’t get information about update blockade.
In the next release this bug will be fixed. Thank you for reporting it.
To do update you need:

1. Create file:

sudo touch /usr/NX/etc/DisableBlockingScript

2. Do the update again (NoMachine Free):

rpm -Uvh nomachine_5.0.43_1_x86_64.rpm

3. Remove the file:

sudo rm /usr/NX/etc/DisableBlockingScript

[zaq]

Hello,

We aren’t able to reproduce your problem in our lab. We need more
details. Could you run below commands and send output to
forum[at]nomachine[dot]com, please?

1) /Applications/NoMachine.app/Contents/Frameworks/bin/nxserver --version

2) system_profiler SPSoftwareDataType

3) codesign -vvv /System/Library/Extensions/nxaudio.kext/

4) find /System/Library/Extensions/nxaudio.kext/ -type f -exec md5 {} \;

• This reply was modified 9 years, 1 month ago by zaq.
• This reply was modified 9 years, 1 month ago by zaq.
• This reply was modified 9 years, 1 month ago by zaq.

[zaq]

Hello,

As is mentioned in dnf’s manual, distro-sync command searches enabled repositories.
NoMachine’s package isn’t in any repository so the command try to remove it. You
can try to run distro-sync without ‘–allowerasing’ option or in some way exclude
NM’s package from the operation. To do update Fedora’s manual recommend a command:

dnf upgrade

https://docs.fedoraproject.org/en-US/Fedora/22/html/System_Administrators_Guide/ch-DNF.html#sec-Updating_Packages

[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.

[Author]

Posts