Forum Replies Created
-
Posts
-
So it seems to work “better” To get it to work correctly, I have to manually start the GDM service and then NoMachine seems to be able to generate a desktop with the display manager.
So I didn’t pull the verbose log because it was really hard to see anything in there, but here is the error that I’m getting on a clean login. NoMachine does display a graphical login prompt, but I never get the desktop after that.
1880 1880 2023-10-31 18:51:48 716.341 NXSERVER Connected from remote machine '192.168.68.52' using protocol 'NX'.Info: Handler started with pid 1880 on Tue Oct 31 18:51:48 2023.Info: Handling connection from 192.168.68.52 port 59444 on Tue Oct 31 18:51:48 2023.1880 1880 2023-10-31 18:51:55 185.346 NXSERVER User 'myuser' logged in from '192.168.68.52' using authentication method NX-password.
unable to link authority file /usr/NX/var/tmp/nx, use /usr/NX/var/tmp/nx-n
Authorization required, but no authorization protocol specified
Authorization required, but no authorization protocol specified
794 1916 2023-10-31 18:51:55 581.817 HostWmRunningHelper: WARNING! Failed to open display ':1024'.
794 794 2023-10-31 18:51:55 582.196 NXSERVER WARNING! Cannot check WM on display :1024 EEXIST
Info: Connection from 192.168.68.52 port 59444 closed on Tue Oct 31 18:51:57 2023.
Info: Handler with pid 1880 terminated on Tue Oct 31 18:51:57 2023.
794 794 2023-10-31 18:52:24 142.207 NXSERVER WARNING! Node b072c19d-fab2-4d6c-9ab0-e67799e52620 from session 3B492D91CE291F76680BC20BBF165090 reporte>
794 987 2023-10-31 18:52:24 356.580 ServerPhysicalSession/ServerConnectOnDisplaySocket: ERROR! Can't connect to socket @'/tmp/.X11-unix/X1' proto UNI>
794 987 2023-10-31 18:52:24 357.161 ServerPhysicalSession/ServerConnectOnDisplaySocket: Error is 11, Resource temporarily unavailable.