July 10, 2015 at 14:40 #7668rejsmontParticipant
I am running OS X 10.10.3 (14D136) and NoMachine 4.6.4. I am unable to unlock settings. I have two admin users – one is AD mobile account, the other is a local admin account. Authentication fails for either of them. I just get the spinning over the NoMachine window and after several seconds go back to the user / password screen.
Any ideas what could be causing this? This bug makes NoMachine unusable, especially that I do not want to allow remote connections to my computer.
Thanks in advance for help.
RadekJuly 13, 2015 at 08:54 #7685rejsmontParticipant
This is what appears in system log during auth attempt:
Jul 9 12:07:21 dme-mac-0039.med.ad10.intern.kuleuven.ac.be sudo: u0078517 : TTY=ttys003 ; PWD=/Users/u0078517 ; USER=root ; COMMAND=/usr/bin/su -l root -c pwd
Jul 9 12:07:21 dme-mac-0039.med.ad10.intern.kuleuven.ac.be nxplayer: WARNING: The Gestalt selector gestaltSystemVersion is returning 10.9.3 instead of 10.10.3. Use NSProcessInfo’s operatingSystemVersion property to get correct system version number.
Jul 9 12:07:21 dme-mac-0039.med.ad10.intern.kuleuven.ac.be nxplayer: 0 CarbonCore 0x00007fff84e4e2b7 ___Gestalt_SystemVersion_block_invoke + 113
Jul 9 12:07:21 dme-mac-0039.med.ad10.intern.kuleuven.ac.be nxplayer: 1 libdispatch.dylib 0x00007fff812efc13 _dispatch_client_callout + 8
Jul 9 12:07:21 dme-mac-0039.med.ad10.intern.kuleuven.ac.be nxplayer: 2 libdispatch.dylib 0x00007fff812efb26 dispatch_once_f + 117
Jul 9 12:07:21 dme-mac-0039.med.ad10.intern.kuleuven.ac.be nxplayer: 3 CarbonCore 0x00007fff84dd7456 _Gestalt_SystemVersion + 987
Jul 9 12:07:21 dme-mac-0039.med.ad10.intern.kuleuven.ac.be nxplayer: 4 CarbonCore 0x00007fff84dd66e3 Gestalt + 144
Jul 9 12:07:21 dme-mac-0039.med.ad10.intern.kuleuven.ac.be nxplayer: 5 libqt.dylib 0x0000000100f0e946 _Z20qt_mac_create_fsspecRK7QStringP6FSSpec + 150
Jul 9 12:07:21 dme-mac-0039.med.ad10.intern.kuleuven.ac.be nxplayer: 6 ??? 0x00007fff6a588ceb 0x0 + 140734977576171July 22, 2015 at 16:28 #7789TorContributor
We’ve documented the problem causing that log, you can see it here:
Anyway it doesn’t look to be related to the authentication problem, we’ll get back to you soon with more details/questions. Thank you.September 17, 2015 at 14:02 #8190hammettParticipant
I have this problem as well, i.e., I am unable to change anything in Preferences –> Connections –> Connection Preferences that requires administrator privileges. On the “Authorization required” screen, I type in a password for my administrator account, and I get a spinning wheel for a few seconds, and then it returns to the “Authorization required” screen as if nothing happened. (I’m adding these terms to make it easier for others to google this problem.) (Curiously, I can then type in sudo commands in a terminal window without it prompting for a password, so it did in fact successfully authenticate with sudo.) I am running Mac OS X 10.10.5 and NoMachine 4.6.16. According to the 3rd post above, this problem should be fixed in version 5:October 7, 2015 at 09:52 #8528BritgirlKeymaster
Everyone, please update to version 5. The TR https://www.nomachine.com/TR07M05813 was fixed in this release.October 14, 2015 at 08:13 #8680iduxParticipant
I am still having this problem running 10.8.5 with NoMachine version 5.0.43. Any attempt to change something in preferences results in a warning “Authentication failed, please try again.” Is there some other way to force it to let me authenticate? I never get a prompt.October 19, 2015 at 14:47 #8752TorContributor
Could you please help by retrieving some logs? This is the list of commands to execute:
– Open Terminal
– tar -czf log.tar.gz .nx/M-*
– tar -czf system.tar.gz /var/log/system.log
– ls -l /Applications/NoMachine.app/Contents/Frameworks/bin > dir.log
– ps -ef | grep nx > ps.log
Send all the highlighted files to forum[at]nomachine[dot]com.
Thank you!November 23, 2015 at 09:59 #9153imansParticipant
Hi. I am having the same problem on OS X 10.10.5 with NoMachine 5.0.47. Any hints?
ThanksNovember 23, 2015 at 10:02 #9161BritgirlKeymaster
@imans, see the thread above. If possible, send us the additional information that Tor has already requested. Thanks!November 30, 2015 at 10:39 #9196
Closed because the user did not provide further feedback. Please notify us if you confirm that it is resolved or open a new topic if you have the same problem.