Britgirl

[Britgirl]

The user who collects NoMachine logs has to be in the sudoers list.

https://apple.stackexchange.com/questions/190883/how-to-solve-user-is-not-in-sudoers-file-incident-reported

If you can’t add yourself to the sudoers list, we can take a look at /Users/nomachine/.nx from the user’s home directory (server side). There won’t be debug since you’ve not enabled, but there might be some clues.

[Britgirl]

What version of Arch? If everything was working well with NoMachine and then these changes appeared after you updated your OS it would appear to be a problem of your system.

What version of NoMachine?

KDE starts fine, but if I start to use it, soon windows start to glitch and freeze. And soon you can’t do anything more … But firefox if opened earlier, continues to work fine.

Do you mean inside the NoMachine session window you see this behaviour?

Are the NoMachine packages you installed from the NoMachine website?

Also check the follow topics related to Arch and Manjaro.

https://forums.nomachine.com/topic/manjaro-gentoo-virtual-screen-kde-taskbar-not-showing-starting
https://forums.nomachine.com/topic/connecting-arch-desktop-to-arch-laptop-got-error-104

[Britgirl]

Screen blanking works as far as we are aware across all supported platforms. Please state the distribution and version, plus the desktop environment assuming that you are connecting to Linux.

 

[Britgirl]

Sorry for the delay in responding.

Can you update to the latest NoMachine version both sides and tell us the steps to reproduce, specifying also the OS on both of the servers you are connecting to? Also, the products you have on each of these servers and what type of session you are using to connect (physical desktop, virtual desktop?).

Thanks.

[Britgirl]

Hi,

please tell us:

1) macOS version of the iMac
2) macOS version on the Macbook Pro

We need the server-side logs (so the iMac) which show the input/output error. From a terminal on the iMac, run nxserver --debug --enable all, reproduce the problem and then sudo /etc/NX/nxserver --debug --collect and send us the file to forum[at]nomachine[dot]com. Please use the topic’s title as the subject of your email. Thanks.

[Britgirl]

Please answer these questions:

– The laptop, server-side, is Linux right? If so, what distro and version, and what desktop environment?
– Wayland or Xorg?
– Did you install the latest version of NoMachine?
– what settings did you change in NoMachine?
– can you tell us what output devices are listed in your system?

[Britgirl]

What are the exact steps to reproduce this in Mari? Also, on the NoMachine Player side (where you are connecting from) can you try disabling auto-repeat?

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

[Author]

Posts