Forum Replies Created
Wow! I had a hunt through the Gnome Issues list and that’s… messy.
Thanks for the solution – “loginctl unlock-sessions” works fine, thanks. It does unlock the physical desktop too, but that’s OK for my purposes. I think that I could use “loginctl unlock-session <session>” according to the man page, but I’ve not investigated.
I could disable the automatic screen lock (through “Settings”, I found) , but I’m not sure that I want the screen to be unlocked all the time.
Thanks again, Britgirl!
I do know what the apt commands mean but I’m not sure what they are supposed to achieve, in the context of my problem. However I carried them out, as suggested, with no change.
Incidentally, on my Ubuntu 22.04 system [Ctrl][Alt][F1] appears to restart X. However I can use other VTs from 3 on up. I didn’t need the VT as I can ssh into the ‘server’ system.
So, I did a command line shutdown/startup of the NoMachine server, (/usr/NX/bin/nzserver –shutdown/startup), logged into the desktop of the server machine, then connected to server from the client machine, and it worked.
A little later I tried again and it didn’t work! The remote screen on the server machine was locked and as soon as I unlocked it, the NoMachine client connection worked. So it appears that the remote machine must be logged in and not locked before I can connect from the remote machine.
Thanks Britgirl. I will try to get the logs.
In the meantime, I’ve discovered that if I go to the ‘server’ and login there, when I come back the login has completed.
I opened a terminal session on the server, and the NX session on the ‘client’ does not have that terminal session.
Does that help?
1) The login screen doesn’t go away. See screenshot.
2) No messages of any sort.
3) The trouble report TR07S10316 does not apply. The login never proceeds. (https://kb.nomachine.com/TR07S10316)
4) I’ve attached a screenshot. (I’ve blurred out the login account, which is probably overcautious.)
5) I forgot to say that I’m using the free version.