jjgalvez

[jjgalvez]

Thank you! Editing the DisplayServerExtraOptions and the PAM config in from su to system-login fixed the issue. You are awesome, Wayland is now working again.

[jjgalvez]

Thank you for getting back to me so quickly.

distro: Arch
kernel: 5.3.1
video card: Radeon R7 240 (MSI)
other info: using opensource drivers, DE Gnome 3.34

I have access to the server, when screen is locked and blank, when I try to connect with NoMachine I see a white screen on the client. Nothing happens on the server the screens remains blank. I can wake the server with its keyboard or mouse and the screen opens to the lock screen, which then comes up in the client as well. At this point I can interact with the server again from the client.

[jjgalvez]

I am having a similar issue with the latest gnome release, using opensource ati drivers. if the computer screen powers off or goes blank nomachine is unable wake up the display and I see only a white screen on the remote side. This only happens with Wayland, If I disable Wayland the display wakes up as expected. Also this only became an issue with the most recent release of gnome 3.34, it was not an issue with gnome 3.32.  I would prefer to use Wayland so I hope this can be fixed in a future release. Happy to include any logs which may be helpful or do further testing

[jjgalvez]

Thank you Mth, at least I feel better that it is not some NoMachine issue that causing the problem. The problem does not seem to be connected with a service. Ordinarily I don’t connect to any unless I need to and then it’s usually only the drive for a short period of time. I suspect it is a connection problem with my mother’s ISP. I’ll have to trouble shoot that the next time I am there.

Thank you again for all your help

[jjgalvez]

I reproduced the error again this morning and I am sending the server and client logs.

Thank you again for your help with this issue

[jjgalvez]

Thank you, on the client side the screen becomes unresponsive for a couple of seconds and then I get the “spinning wheel” and eventually I get a time out error.

I will reproduce the error again and generate regenerate both the server and client logs and send them to you again. Of note the error happens regardless of of the client host. I was on the machine this morning from a mac on a different network and got the same error.

[jjgalvez]

I send the log files today. Sorry it took me several days to get back to this, things got busy at work and I was unable to log into this machine to reproduce the issues until now.

Thank you for reviewing the log files, hopefully something will reveal itself.

[jjgalvez]

Fantastic, thank you, for now I think that’s the easiest solution.

[jjgalvez]

Thank you. This morning I created a pair of keys using the NoMachine native nxkeygen following the instructions here: https://www.nomachine.com/DT09M00103&dn=nxkeygen and they are working well. Is it ok to continue to use this pair or should I follow the instructions you outlined above?

[jjgalvez]

OK so one thing I did wrong is that I created the cert pair on the server and not on the client was the connecting to the server, once I created the cert on the client and imported the correct pub cert on the server I was able to connect with just my certs.

 

[jjgalvez]

I looked at the nxserver log and there I see a public key not recognized error

[jjgalvez]

So I followed those instructions

Created a key, appended the pub cert to the end of .nx/config/authorized.crt

On the client I checked “private key” and imported my private cert

But when I try to connect nothing happens. BTW the cert has not passphrase so none was entered

Not sure where to go from here

[Author]

Posts