Britgirl

[Britgirl]

If you need the latest version of the software, please go to https://downloads.nomachine.com/download-enterprise/ and scroll down to the Small Business Terminal Server link and click to download. Provided your subscription licenses are valid, you can install that package.

If your subscription has expired, please get in contact with the Sales Team (Go to Contact Us in the footer of the website).

Please also consult this link article “How to upgrade NoMachine products v7 to v8” available here: https://kb.nomachine.com/AR12S01147. From version 8 onwards, there is only a single license file, server.lic, for each server side product. When replacing license 7 with the new v8 server.lic, the old node.lic file is simply ignored by server software v8 and no further actions are required.

[Britgirl]

It could be related to this already known bug:

White screen occurs when connecting to a KDE/Plasma Wayland desktop on Kubuntu
https://kb.nomachine.com/TR07U10921

Try disabling Wayland and use X.org instead. Does this help?

[Britgirl]

We cannot be sure that these problems are not coming from the fact that you are installing from the AUR repository. We are not aware of any issues with detecting LXQT sessions. So, what you should do is try the packages from our website:

uninstall:

sudo /usr/NX/scripts/setup/nxserver --uninstall

download and install:

wget https://www.nomachine.com/free/linux/64 -O nomachine.tar.gz
sudo tar zxf nomachine.tar.gz -C /usr/
sudo /usr/NX/nxserver --install redhat

[Britgirl]

This is not a NoMachine problem but one created by the Arch repository.

You need to edit KGBUILD and set _autoservice=y and _autofirewall=n

### BUILD OPTIONS
# Set to y to enable nomachine service autostart
_autoservice=n
# Set to y to enable firewall autorules
_autofirewall=n
### END BUILD OPTIONS

You can also just set this:

sudo /etc/NX/nxserver --startmode nxd automatic

and set in /usr/NX/etc/server.cfg

EnableFirewallConfiguration 1

after installation.

Or better still, download and install manually from the NoMachine website:

wget https://www.nomachine.com/free/linux -O nomachine_current.tar.gz

sudo tar zxf nomachine_current.tar.gz -C /usr

sudo /usr/NX/nxserver --install redhat

[Britgirl]

Hi, whilst I can’t confirm pricing here, subscriptions will be priced so as to be a viable option for everyone 😉  Watch this space or sign up for news to know when Network has been released.

[Britgirl]

Hi, logs show a lot of errors, but they also show that you have a Small Business Server Subscription file installed in a NoMachine server free edition package. From version 8, the product subscription file and the installed server type must match.

You should install the Small Business Terminal Server package v8. Please install that, and start from this clean installation, then try to connect again. If you continue to have errors, resubmit the logs.

Valid subscriptions are entitled to technical assistance from the support team, so please consider opening a support enquiry from the customer area. If you can’t access the customer area, please submit your issue to our team via the Report Issues link here: https://www.nomachine.com/report-an-issue

[Britgirl]

That’s right. The Trouble Report I linked applies to all RPi boards.

[Britgirl]

Hi, the logs didn’t attach. Can you send them to forum[at]nomachine[dot]com? Thanks!

[Britgirl]

This will be closed because we didn’t receive the logs. What we suggest is that you update to the latest version and resubmit a new topic if you are still not seeing the balloon pop up to accept. We are not aware of any issues. We will need to know the operating systems being used, and versions, and if you are using Linux, also the desktop environment.

[Britgirl]

There must be a bug in latest drivers that causes a resource leak. Until it is fixed by AMD or unless you downgrade the drivers, you can only disable HW decoding in NoMachine.

[Britgirl]

Hi, can you tell us the Linux distro and desktop environment of the Linux server?

[Britgirl]

Could it be a permissions problem? Can you try removing NoMachine from Accessibility and Screenrecording lists and then restarting NoMachine (you can do it from terminal with sudo /etc/NX/nxserver --restart) and follow the prompts that should direct you to enabling both permissions?

[Britgirl]

Hi, the logs you pasted indeed show the same errors of the problem we investigated. The bug occurs in all situations in which the X server “goes offscreen”. We are, in any case, we are looking at ways we can work around this X.org bug by delaying the lock the screen after making sure the screen blanking is deactivated. So watch out for this in upcoming software updates.

[Britgirl]

The behaviour is normal, because the client is configured to be always at the same size of the remote desktop, and the lock screen changes its size to a geometry not supported by the client. Whether this can be improved is not easy to say. The desktop and the lock screen have different geometries.

[Britgirl]

Hi, yes, this is what we suggested in other topics on the forums, for example here: https://forum.nomachine.com/topic/windows-display-scaling-nomachine-makes-it-blurry#post-44040

We are planning to support different scaling factors for Windows in the future. At the moment, our priority is version 9 with NoMachine Network and other important features planned for that. Development can most likely start after that.

[Author]

Posts