Britgirl

[Britgirl]

Did you install package from our website or from the aur repository? We tried the packages from the aur repo on the fly and they indeed behave in the same way as what you are experiencing. Maybe tell the guys who handle the repo at https://aur.archlinux.org/packages/nomachine?

You can check what you have set by running:

sudo /etc/NX/nxserver --startmode

If the output is similar to this, then it’s the packages which are messed up:

NX> 807 Service NoMachine status is: Automatic
NX> 807 Service NXD status is: Manual

To change it run sudo /etc/NX/nxserver --startmode nxd automatic

[Britgirl]

Hi, can you tell us what application it is your using (where does that menu come from?).

[Britgirl]

Yes you can but with some limitations. Please check out the section on webcams in this article:

NoMachine USB forwarding limitations
https://kb.nomachine.com/AR03R01080

[Britgirl]

Are you connecting to a virtual desktop session or a physical desktop session?

Can you disable HW decoding in NoMachine on the Mac side? You can disable it completely in the player.cfg. Please edit the file $HOME/.nx/config/player.cfg and set the configuration key “Enable hardware accelerated decoding” to “disabled”. Before changing the configuration key, you should first quit the NoMachine Player (you can do this by right clicking on the !M icon in the system tray and selecting ‘Quit NoMachine Player’).

[Britgirl]

Or passing mic from a pc client to a remote server is also not working?

Is the mic enabled in the NoMachine’s app allowed permissions? (Look in Settings -> Applications and scroll down to NoMachine).

The v8 update is in its final stages now.

[Britgirl]

Hi

Logs show nothing wrong with NoMachine, but with your environment. You have Ubuntu, but Kubuntu-Desktop is installed and we cannot be sure how it was installed. Logs show you are using GDM and even Gnome works fine. Anyway, there is a way to find out how NoMachine sessions are being created. First log on locally to the KDE desktop, then go to your NoMachine client side player and start a physical desktop session to the KDE desktop with NoMachine.

Open a terminal and run

echo $XDG_CONFIG_DIRS

The output must be used inside the CommandStartKDE command:

CommandStartKDE "/usr/bin/env XDG_CONFIG_DIRS=output_of_the_echo_command /usr/bin/dbus-launch --sh-syntax --exit-with-session /usr/bin/startplasma-x11”

If that doesn’t help, we don’t know what else to suggest. Environment configuration (beyond the default one) is not really within the scope of these forums.

[Britgirl]

I suggest you watch out for version 9 which implements NoMachine Network.

https://www.nomachine.com/network

Thanks for evaluating us nonetheless.

[Britgirl]

Submit screenshots and logs to forum [at]nomachine[dot]com. Thanks!

[Britgirl]

By setting in the Connect Policy key desktop=1 in server.cfg you should set the #CommandStartKDE “” key in node.cfg (not the DefaultDesktopCommand key)

CommandStartKDE "env XDG_DATA_DIRS=/usr/local/share:/usr/share:/var/lib/snapd/desktop /usr/bin/dbus-launch --sh-syntax --exit-with-session /usr/bin/startplasma-x11"

Does this help?

[Britgirl]

Support for Pipewire in NoMachine was added in v8. So you have two choices:

1) update to version 8. If you update you should also execute the command:
sudo /usr/NX/bin/nxnode –audiosetup

Otherwise uninstall v7 completely and install v8.

2)  if you don’t want to update, you could also try the workaround which we provided for Ubuntu.

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

[Britgirl]

Hello,

Did you set the option key=”EnableHardwareEncoding” key to 0 in the node.cfg on the server side and there was no change? You could also disable HW encoding (again on the server side) by going to: server settings -> server performance -> uncheck “Use hardware encoding”. Then try connecting again.

If that doesn’t help, next step is to try disabling HW decoding on the client side.

Try the following:

1. Quit the Player and disable hardware decoding in the player.cfg with option key=”Enable hardware accelerated decoding” value=”disabled”. Restart the Player. Try connecting again.

Assuming you have a valid subscription you can also use the official support channel if you prefer which will avoid sensitive information being published here.

[Britgirl]

Thanks for the additional info. In your earlier topic you mentioned you were using Workstation, so I assume you still are.

Could you tell us if you see any difference in how keyboard is mapped when connecting to 1) virtual NoMachine desktop 2) physical display and 3) tell us if you are connecting to a vnc session already running.

[Britgirl]

Screenshots show that nxnode is not running and that is why the systray icon is not visible. Can you enabled debug and send us the logs from the affected Windows by opening a CMD console as administrator and running:

> %ALLUSERSPROFILE%\NoMachine\nxserver\nxserver.exe --debug nxserver --debug --collect

[Britgirl]

What was your previous version when you didn’t see this behaviour? There were no changes in the client between 8.2 and 8.3 which could cause this.

You could try cleaning up the user files directory, by closing the client and deleting almost everything in C:\Users\<username>\.nx , but keeping only folders ‘config’ and ‘cache’.

[Britgirl]

I was just about to answer you when you posted a reply. Anyway, if it can help, we have this article:
https://www.nomachine.com/AR08M00857 for trouble-shooting.

We also generally recommend not to have another NX-derivative on the same server as NoMachine as we cannot guarantee that there won’t be incompatibilities.

[Author]

Posts