No desktop on fresh login

[jschweg]

Hi folks, I just installed the ARM Debian Package on my Pi4 running Debian 12 with Gnome/Wayland, I do have a physical monitor connected to the host. If I already have a gnome session logged in, and I use NoMachine, it takes me to the existing desktop and all works well. If I do not have an existing gnome session logged in already, I can connect with NoMachine, I can see the gnome login screen, but after entering my credentials, NoMachine goes to an empty grey screen, while the physical display will continue along to the desktop environment.

I tried switching to egl capture per some of the KB articles I read though, but still have this problem.

[Britgirl]

Hi, there is Trouble Report open for a problem that looks like yours.

NoMachine displays an inactive session as active on Wayland
https://kb.nomachine.com/TR07U10910

It will be fixed in the next maintenance.

[jschweg]

Thanks for replying! Mine sounds a little different, but definitely in the same ballpark. Maybe I’ll wait for this release and see what happens after that. When is that next maintenance expected?

[Britgirl]

If you send us the logs of the server side, we can check them to see if it is indeed the same problem. Check out this article to know what to do to get those:

https://kb.nomachine.com/DT07S00243

Send them to forum[at]nomachine[dot]com.

The MR is planned in the next couple of weeks.

[jschweg]

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.

[Britgirl]

Did you update to 8.10?

That TR we mentioned https://kb.nomachine.com/TR07U1091 was fixed in the latest release.

[jschweg]

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.

[Author]

Posts