NoMachine 5.0.43 not working with OSX El Capitan

[redgreenblue]

Since upgrading to OSX 10.11 El Capitan NoMachine 5.0.43 is not working anymore.

I am trying to connect to another Ubuntu box running 5.0.43 too.

The application fails in different ways:

– Everything works ok (connects, etc.) for 3 to 4 seconds and the NM disappears (it doesn’t crash or anything, just disappears)

– When I open NM in OSX, nothing happens. If click on the icon, I can see the menu but there is no window

– Sometimes the window appears, but when I try to connect I get a beachball and later it disappears.

All in all, I can never see a crash, it is mostly about windows disappearing and not coming back. By the way, mission control doesn’t show the windows either.

Any tips / suggestions ?

Thanks for your help.

[Tor]

Hi!
We’ve recently found a problem on OS X 10.11, in order to verify if the issue is the same, can you please do this:

– Open Terminal
– Execute the command tar -czf logs.tar.gz ~/.nx/R-*
– Execute the command tar -czf stacks.tar.gz ~/Library/Logs/DiagnosticReports/nx*
– Execute the command open .

In the Finder window you’ll find the files logs.tar.gz and stacks.tar.gz. Could you send them to forum[at]nomachine[dot]com?
Thank you!

[albe]

Hi!

Same problem here – starting from a clean install. I’ll send you the logs.

–albe.

[Tor]

Hi albe.

Please check this, the workaround explained there should help you:

A crash occurs when executing a call to network API on OS X 10.11 El Capitan
https://www.nomachine.com/TR10M06094

[dmingram66]

I’ve tried the fix described but I’m also having crash problems. The connection times out and the log file shows the following error

>5654 81667 12:46:03 031.293 Io/Io: WARNING! Can’t resolve IPv6 host ‘nx.xxx.xxx.xxx’.
>5654 81667 12:46:03 031.346 Io/Io: WARNING! Error is 49, ‘Can’t assign requested address’.

[Tor]

Hi dmingram66.
I’d like to be sure you’ve the same problem reported by albe, could you please send Diagnostic Reports to forum[at]nomachine[dot]com? Thanks.

[redgreenblue]

Hi,

I can confirm that the workaround fixed the problem (https://www.nomachine.com/TR10M06094)

Thanks!

[Author]

Posts