qqalexn

[qqalexn]

Linux Mint Cinnamon 19.3.

Clearly, it would be helpful if all the keyboard grabbing and key mapping options were documented together in an up-to-date document. It would be nice if it would explain their use for a situation like mine, which would not seem to be very novel. E.g., Linux client, Mac server.

Thanks!

 

[qqalexn]

I did this nxplayer --activegrab.

I didn’t find it did anything different. Nor did checking or unchecking the “grab the keyboard.” settings option.

So I don’t see how a Mac server is fully usable with NoMachine from a non-mac client.

[qqalexn]

No Firewall or antivirus active. When I do, rarely, connect, turning them on makes no difference and I can disconnect and reconnect with them on.

nc (netvcat) command line utility reports can connect to machine’s IP address. This happens even when nomachine client cannot connect AND after clicking “stop server”

” nc -zv 10.1.10.27 4000
Connection to 10.1.10.27 4000 port [tcp/*] succeeded!
”

If I use portqry.exe (version 2) on the problem machine, I see that nxserver is always listening on port 4000. And says established if I manage to get a connection.

I’ve found that repeatedly restarting the nxserver via “server restart” button sometimes allows NoMachine session with this machine. This approach is unpredictable. However, IF it results in being able to connect once. That ability survives connect/disconnect cycles and further server restarts, but NOT rebooting the OS.

On BOTH of my xp pro sp3, 32-bit machines, having  installed NoMachine results in this error message on windows shutdown:

“tasklist.exe unable to locate component. The application has failed to start because framedyn.dll could not be found. Reinstalling the application may fix the problem.”

Both those files are present, not corrupt and the error is gone when NoMachine is uninstalled.

This message also appears when NoMachine is restarted.

Only one of the xp computers has the connection problem. though both show this error message.

I also notice that the “server status” list box of connection ip addresses has only one or two entries (nx: ) and without any external addresses rather than the many I see in Linux NoMachine server status that have external addresses. All on same LAN.

Anyway, I’ve wasted a ton of time on this. I think what’s needed is some scrutiny of the logs to see if something is interfering with this instance of NoMachine’s server. Or I need better, straightforward, NoMachine diagnostic tools to see what’s happening in the dialog between machines.

Thanks.

[qqalexn]

Sent.

[qqalexn]

Thanks for replying.

xp pro workstation sp3 32-bit.

Which logs? Client or server?

Thanks.

[qqalexn]

FWIW Using [removed], I can connect to the XP machine just fine. Same connection topology. Only change is using (removed) instead of NoMachine.

I’m retrying to attach log from my previous post.

 

Attachments:

1. failed_excerpt_LM_to_XP_SP3_host.txt

[qqalexn]

Thanks. CTL – S doesn’t work, because CTL maps to CTL.

Mac needs CMD, but SUPER key is grabbed by Linux Mint for menu and the nomachine’s -grabkeyboard doesn’t seem to affect this behavior when nomachine’s window has the focus.

I use the Mac’s keyboard viewer to see what a Linux Client keypress maps to on Mac.

Need something that maps from Linux keyboard ? key to Mac CMD.

I can’t be the first person trying this. Must be documented somewhere, no?

Thanks!

[qqalexn]

Problem maintaining stable connection is due to mac laptops need for an active display to not sleep their GPU. When lid closed without active external monitor connection, mac goes to sleep no matter what built-in settings are set.

So need a way to fake an active display or defeat Apple’s default lid closed action.

Antisleep app (in apple store. Costs small $ for necessary functions) for mac app defeats the lid close action with “prevent sleep with lid closed” menu option.

Alternative is a mini-displayport display emulator plugged into thunderbolt port to fake presence of active display.

Do either and you can close the lid on the mac and maintain a NoMachine connection. At least with Macbook Pro Retina mid2015 on AC power.

Huge waste of time for such an obviously useful need.

Thanks for playing 😉

 

 

[qqalexn]

Thanks for the reply. The screen blanking does blank my screen, but it’s the closed lid operation that seems to have worked in the past I seek. I’m hoping someone knows the incantation that currently works.

Having now spent too much time researching this issue, it seems using Macbook pro retina with High Sierra in Clamshell mode with lid closed and no external display is mostly about the Mac Lid closed action forcing sleep. There used to be ways around this, but they seem to be deprecated / no longer work. E.g. InsomiaX, Amphetamine, etc???

Tools that relied upon terminal command pmset -c disablesleep 0 may no longer work as it seems disablesleep option is no longer offered.

I notice that nomachine seems to insert coreaudiod to prevent sleep, but seems not to work in clamshell mode.

e.g., Mac system monitor> all processes. “preventing sleep column” shown, all processes show no.

FWIW, pmset -g command reports

System-wide power settings:
SleepDisabled        0
Currently in use:
standbydelay         10800
standby              1
womp                 1
halfdim              1
hibernatefile        /var/vm/sleepimage
powernap             0
gpuswitch            2
networkoversleep     0
disksleep            0
sleep                0 (sleep prevented by coreaudiod)
autopoweroffdelay    28800
hibernatemode        3
autopoweroff         1
ttyskeepawake        1
displaysleep         0
tcpkeepalive         1
acwake               0
lidwake              1

With these settings, closing the lid results in no nomachine window going black in about 35s and then “attempting to reconnect” that times out. If I reopen the lid I get the remote screen back as it was. So lid closing is still forcing sleeping.

Here’s the log of power actions for a cycle of closing and opening lid.

pmset -g pslog
Logging IORegisterForSystemPower sleep/wake messages
pmset is in logging mode now. Hit ctrl-c to exit.
2020-03-23 10:20:28 -0700 IOPSNotificationCreateRunLoopSource
Now drawing from ‘AC Power’
-InternalBattery-0 (id=4587619)    100%; charged; 0:00 remaining present: true

2020-03-23 10:20:45 -0700 IORegisterForSystemPower: …Sleeping…

2020-03-23 10:20:50 -0700 IORegisterForSystemPower: …HasPoweredOn…
Wake Reason = EC.LidOpen
wakeType = HID Activity

…

Still hoping for resolution.

Thanks much for the help!

 

[Author]

Posts