Britgirl

[Britgirl]

This topic was spun off from another post about audio (on Alma Linux) by the admins. Are you still having problems with getting audio to work?

For some tips on how to set up NoMachine with Pipewire, take a look at the following articles:

How to enable audio on systems relying on PipeWire for sound
https://kb.nomachine.com/AR07T01168

How to support audio in NoMachine virtual desktops on Linux host using PipeWire
https://kb.nomachine.com/AR12U01215

[Britgirl]

The logs didn’t include var/log/node logs which is what we would need to be able to see any errors, warnings and reasons for not being able to connect.

Maybe the issue is with it being headless? If you attach a monitor, does anything change? If that is not an option, you could disable the xserver and then sudo /etc/NX/nxserver --restart and connect again (tips are available here for that: https://kb.nomachine.com/AR03P00973).

If that does not help, we need full logs from the server machine you are connecting to. You can gather up by following the instructions here: https://kb.nomachine.com/DT07S00243. Thanks.

[Britgirl]

Hi, streaming mic from the server side to the client side is not supported. Can I ask what your use-case is?

[Britgirl]

That post is 3 years old and we released a new mobile version since then that correctly supports window resizing 🙂

Is your actual problem that the window bar is visible on top? This is a common problem on DeX, for example
https://us.community.samsung.com/t5/Suggestions/Dex-mode-full-screen/td-p/2343762

One user of that thread said “I did Force Stop Dex for PC and cleared the apps cache. It now works”. Could you try the same?

If, instead, the problem is not the bar showing, what is it? Is the remote desktop not supporting the resolution of the DeX screen geometry? What OS/version is on the remote desktop by the way?

[Britgirl]

You can use the same checkbox that you use in the server settings to blank the screen when you are connected to that computer. During the NoMachine session just go to the !M icon of the desktop you are connected to and open the Server settings. Enable screen blanking on the fly. Once you’ve finished, you can disable it and then disconnect.

Edit: We thought deeply about what you requested, and it can indeed be a very useful feature, something the user can do “on the fly”, when needed. And so this is the result (see attached).

We’ll be adding it to NoMachine 9. 🙂

 

Attachments:

1. 

   4-System-Tray-Win-5.jpg
   

[Britgirl]

We were unable to reproduce this problem of not being advertized on the LAN. Can you send us the logs of the server side? Please follow the instructions here and submit them to forum[at]nomachine[dot]com using the title of this topic as the subject of your email.

https://kb.nomachine.com/DT07S00243

 

[Britgirl]

If you are going to use the free NoMachine and not the SBTS which seems to be what you were using before, please install from scratch by first uninstalling completely first, removing traces of NoMachine etc, then reproduce the problem, send new logs of the affected session.

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

[Author]

Posts