Forum Replies Created
-
AuthorPosts
-
July 13, 2020 at 08:47 in reply to: Waiting for the desktop user to authorize your connection #28496rprParticipant
I followed your advice and set the following option in /etc/gdm3/custom.conf:
# Uncomment the line below to force the login screen to use Xorg
WaylandEnable=falseAfter system restart I can confirm that this change solved the issue.
— rpr.
rprParticipantI forgot to mention two things:
- Wayland is not used for the desktop on that machine:
$ echo $XDG_SESSION_TYPE
x11 - The machine does not have a monitor connected.
— rpr.
rprParticipantHello, Mth!
Here are the information about the machine where the issue occurs:
Physical machine: HP dc5850sM with AMD Athlon X2 5200B, 4 GiB DDR2, on-board ATI Radeon 3100
OS: Ubuntu 20.04 LTS
Architecture: AMD64
Desktop environment: GNOME (default for Ubuntu 20.04)
NoMachine for Linux 6.11.2 (free version)Client: NoMachine Enterprise Client 6.11.2 on MS Windows 10 19.03 x64
I’ve just sent the debug logs.
— rpr.
rprParticipantI’ve done some more testing on the Ubuntu 20.04 machine which has only two ordinary users (with UID >= 1000). It is running the free version of NoMachine for Linux 6.10.12.
After rebooting the machine I tried to connect to it with NoMachine Enterprise Client 6.10.12. The login to the NX server was successful but then the client displayed “Waiting for the desktop user to authorize your connection” although there was no desktop user logged in. After a few seconds I closed the client.
Here are the NX log records I found about the session (after logged in via SSH):
/usr/NX/var/log/nxserver.log
2020-05-29 16:38:32 483.721 799 NXSERVER Starting LS 6.10.12 and services.
2020-05-29 16:38:32 570.233 799 NXSERVER System information: Ubuntu 20.04 LTS, standalone.
2020-05-29 16:40:41 833.970 1674 NXSERVER User ‘rpr’ logged in from ‘192.168.33.30’ using authentication method NX-password.
2020-05-29 16:40:49 689.909 1674 NXSERVER User ‘rpr’ from ‘192.168.33.30’ logged out./usr/NX/var/log/nxerror.log
799 1121 16:38:39 608.816 ServerNetworkInfoHandler: WARNING! Obtaining network data failed.
Info: Handler started with pid 1674 on Fri May 29 16:40:35 2020.
Info: Handling connection from 192.168.33.30 port 54246 on Fri May 29 16:40:35 2020.
Info: Connection from 192.168.33.30 port 54246 closed on Fri May 29 16:40:49 2020.
Info: Handler with pid 1674 terminated on Fri May 29 16:40:49 2020./usr/NX/var/log/nxd.log
Info: Server started with pid 1110 on Fri May 29 16:38:32 2020.
Info: Listening for connections on any interface on port 4000.
Info: Accepting connections from any host with encryption enabled.
Info: Connection from 192.168.33.30 port 54246 accepted on Fri May 29 16:40:34 2020.
Info: Connection from 192.168.33.30 port 54246 process 1674 started on Fri May 29 16:40:34 2020.
Info: Connection from 192.168.33.30 port 54246 process 1674 closed on Fri May 29 16:40:49 2020./usr/NX/var/log/node/C-mypc-1001-5A2D779FBAC40F198A4A621338E99811/options
nx/nx,slave=1,id=mypc-1001-5A2D779FBAC40F198A4A621338E99811,cookie=36E1262303CC4A808E619685898BA889,audioin=5:5:vorbis:socket-/run/nxdevice/D-1001-5A2D779FBAC40F198A4A621338E99811/audio/native.socket:1,voiceout=5:5:speex:socket-/run/nxdevice/D-1001-5A2D779FBAC40F198A4A621338E99811/audio/native.socket:1,cpus=2,hwenc=1,encmode=auto,monitor=9,threads=auto,priority=realtime,dxgrab=0,legacykb=0,shadow=:1024:1001/usr/NX/var/log/node/C-mypc-1001-5A2D779FBAC40F198A4A621338E99811/session
NXAGENT – Version 6.10.12
Copyright (C) 2001, 2019 NoMachine.
See http://www.nomachine.com/ for more information.Session: Starting session at Fri May 29 16:39:06 2020.
Info: Agent running with pid 1378.
Info: Slave server running with pid 1400.
Info: Listening to slave connections on port 12001.
Info: Display running with pid 1401.
Info: Audio server started with pid 1415.
Info: Audio client started with pid 1416.
Info: Display server started with pid 1417.
Session: Session started at Fri May 29 16:39:07 2020.In the logs I don’t see any obvious problem.
The same thing happens if I use the other user’s credentials for NX login in the client.
As I wrote, the only solution to the problem is to set
PhysicalDesktopAuthorization 0
in /usr/NX/etc/server.cfgAny comments?
April 29, 2016 at 08:54 in reply to: How to configure automatic clean-up of session directories on the client? #11101rprParticipantTor, you are right. After disabling the “Don’t delete log files on exit” option, the session directories are removed at the end of session.
BTW, that option corresponds to the following line in “%USERPROFILE%\.nx\config\player.cfg”:
<option key=”Remove old sessions” value=”true” />
— rpr.
April 26, 2016 at 08:09 in reply to: Issue with fullscreen session after starting file transfer #10992rprParticipantI can confirm that this issue has been solved with the upgrade of NoMachine Workstation for Linux to ver. 5.1.22_6.
- Wayland is not used for the desktop on that machine:
-
AuthorPosts