Inconsistent redraws on Sequoia

[fggf]

Hi,

I’m having problems on a MacOS Sequoia server. I have 2 clients I can use, either Android or Ubuntu 22.0.4 Aarch64 (no desktop just DWM as a window manager).

[All NoMachine versions are free versions]

I didn’t experience the problem until I updated NoMachine. I’m on 8.14.2 now, and the problem was there on the previous version which I think was 8.14.1. But I didn’t notice it before but I’m not sure what version I was on, guessing 8.14.0 (as I only installed NoMachine for the first time a few days ago). Sorry I know this is annoyingly vague but I don’t have a record of what version I was on.

Whichever client I connect with, the symptoms are the same.

It seems the display doesn’t always update on small changes. For example, in a terminal:

I type: a
terminal displays: a

I type: b
terminal displays: a

I type: c
terminal displays: abc

 

Another example: If I tap on a menubar item in the OS, the menu doesn’t appear, until I move the mouse/pointer.

Another: In this box on the forum to type this post, if I use the arrow keys to move the cursor, if I press it 5 times, 3 or 4 times it will move, but at some point it won’t move, until I press again, then it will move 2 jumps.

 

Things I’ve tried:

Updating NoMachine – MacOS server is on 8.14.2,  Android client is 8.7.1, Ubuntu Aarch64 is on 8.14.2

Restarting NoMachine server many times

Restarting Mac many times

Updating Sequioa – Was on 15.0.0, updated to 15.0.1

Different resolutions, modes eg full-screen, scale to window etc. Strange thing is, very occasionally (maybe 1 in 20 times) a change will seem to randomly fix the problem and everything is ok for hours. But then at some point it just returns, without changing any settings. I can see no pattern to which settings cause the temporary fix, it seems almost like the act of changing something is what causes it to work.

Adding DisplayServerExtraOptions “-nodamage” to /Applications/NoMachine.app/Contents/Frameworks/etc/node.cfg

and restarting the server. This seemed to fix it for a while, but was temporary as above and the problem came back. I don’t actually think the option fixed it, more likely it was just the ‘random’ fix that happens occasionally.

Any ideas of what else I can try please. NoMachine is really nice (and thank you for it btw), but this is making it feel so awkward that [removed] feels nicer just because it’s consistent (if slower).

Are there perhaps old versions archived somewhere so I can try a downgrade?

Thanks again 🙂

[fra81]

Hi,

we can’t reproduce this issue in our labs, so we would need some more info from you.

1) You say you weren’t experiencing the problem before updating. Do you mean updating the client or the server?

2) As I understand, both clients run on ARM architecture. Would it be possible to try a different client? And, if using the same two clients, do you have the possibility to connect to a different server machine and check whether the issue is present also there?

3) What is the model of your Mac?

4) Can you please try to rename this library on the server:

sudo mv /Applications/NoMachine.app/Contents/Frameworks/lib/libnxsck.dylib /Applications/NoMachine.app/Contents/Frameworks/lib/libnxsck.dylib-bak

and restart the NoMachine server? Does it help?

5) May you send us the logs from the server? See https://kb.nomachine.com/DT07S00243. You can send them to forum[at]nomachine[dot]com.

[Author]

Posts