Britgirl

[Britgirl]

The attachments were not working for some reason and so they have been removed. Can you send them directly to forum[at]nomachine[dot]com, please?

[Britgirl]

I assume you’ve got 8.14 on the Windows computer as well.

When you say “after rest” in the title, do you mean you start the session to the Mac and leave the session open/running, and then go back to it after some time?

[Britgirl]

UDP traffic goes through port 4000, this has been the case since the first release of version 8. Using ports 4011-4999 would not improve performance.

[Britgirl]

Is the display server X11 or Wayland? On Kubuntu it’s x11 by default, maybe you installed Wayland and are you using that?

Logs would be useful from both sides. You can extract them using the instructions here: https://kb.nomachine.com/DT07S00243

Send them to forum[at]nomachine[dot]com. Please use the title of this topic as the subject of your email. Thanks!

[Britgirl]

Thanks for your input. We will evaluate whether offering a shortcut for activating/releasing keyboard grab is feasible.

[Britgirl]

Our Multi Monitor fullscreen spans a window across multiple displays. On macOS this is not possible in the default configuration, where every display has its own “Space”. A workaround consists in disabling such option (“Displays have separated Spaces”).

[Britgirl]

Hi, we would still like to send you a debug package if that’s ok with you, it would allow us to debug EGL capture. Please check your inbox for emails from us, there will be a link to a package for you to download along with further instructions.

 

[Britgirl]

The problem with right-click was actually fixed in an older version of NoMachine for Mobile.

Here is the original Trouble Report: https://kb.nomachine.com/TR07P08723.

Successive Android system updates, namely 12 and later versions, introduced changes to properties of some events, and the problem has unfortunately re-appeared, but it does not occur on all models of devices. We opened a new Trouble Report,  https://kb.nomachine.com/TR08V11198. The next NoMachine update for mobile will include the fix.

[Britgirl]

emilianoheyns, can you confirm that you are still experiencing this issue on Sequoia after updating to NoMachine 8.14 and after following the instructions in the article I linked earlier?

https://kb.nomachine.com/AR09V01251

[Britgirl]

Confirm the exact desktop environment you are using (KDE, Gnome ?, and its build version).

[Britgirl]

All NoMachine Linux Terminal Server products support VirtualGL, including the evaluation version. You need to enable VirtualGL first, so this is the first thing you should check. How to do that is explained in the following article:

How to enable VirtualGL support on Linux in NoMachine
https://kb.nomachine.com/AR05P00982

In short, the commands to use are sudo /etc/NX/nxserver --virtualglinstall and sudo /etc/NX/nxserver --virtualgl yes. But please consult the article for full steps.

Let us know if following those steps helps.

In your output of the client, we can see that HW encoding is working correctly. On the client side the session is using software decoding, and not hardware decoding. If this is not what you expected on the client side (we are not sure from what you wrote), you should send us logs from the device you are connecting from and we will check them. See this article (step 4) https://kb.nomachine.com/DT07S00243.

[Britgirl]

We could send you a package for you to install with higher debug enabled for mdns discovery which could allow us to investigate (given that we can’t reproduce it). Are you available to try that?

[Britgirl]

Your connection logs say that server uses resolution 3840×2160, and connecting client tries to change it to 1698×965 since the resize display mode is enabled. However the desktop turns it back again to 3840×2160 (this is up to the desktop environment) and the client is forced to enable the viewport mode, because the resolution is too big for the client display.

Can you confirm that, in this particular test, the reason why you see only part of the screen is not due to the client running in viewport mode? (i.e check whether the client is running or not running in viewport mode)

We also need to ask you for some additional information:

– Output of the command xrandr -q executed in a terminal window on the server

– We would like to try again to get server side logs. You don’t need to restart the
server after enabling the debug logging, just reproduce the issue and get a set
of logs:

1. sudo /etc/NX/nxserver --debug --enable all
2. Connect to the server, reproduce the issue and while the session is connected go to the next step
3. sudo /etc/NX/nxserver --debug --collect
4. sudo /etc/NX/nxserver --debug --disable all

Send everything as before 🙂

[Britgirl]

I don’t know what Wayland or Xorg are, but I did modify some setting to disable something related to Wayland

So please check that Wayland has been correctly disabled.

As sudo, edit GDM file with a text editor:

sudo vim /etc/gdm/custom.conf

Find the WaylandEnable line and modify it to this:

WaylandEnable=false

Remove the pre-prending # to force the login screen to use Xorg

If there is no such line, you can add it in [daemon] section.

Save, and then reboot.

[Britgirl]

You can change the shortcuts how you want using the panel here. There must be at least 2 keys for each shortcut.

See this guide, https://kb.nomachine.com/DT07S00236#2.1, and scroll to “Use keyboard shortcuts for quick actions”.

[Author]

Posts