First blank screen, next ‘Connection reset by peer’

[jsbien]

I try to connect to a laptop (Debian buster) from a desktop (Debian buster) and occasionally a Raspberry (raspbian). For a fresh install on the laptop at first I get the connection with blank screen. I made the changes suggested in https://forums.nomachine.com/topic/white-screen-when-tried-to-access-a-linux-ubuntu-machine-from-windows-10 but now I cannot connect at all.

I’m familiar with https://forums.nomachine.com/topic/blank-screen-upon-connection but it doesn’t seem applicable to my situation.

I hope the enclosed log contains some useful information. I found several different instruction how to collect logs and I’m slightly confused which is the proper way.

I will appreciate your help.

Attachments:

1. nxserver.zip

[Mth]

Hello.

The logs indicate that nxnode process that is responsible for physical session is terminating with segfault. It is either system segfault or our abort procedure, we are not sure.

Please check the system logs for nxnode process with pid 11286. If there are any crash reports we would be grateful for a backtrace.

Also please include the rest of log files from our log directory besides the nxserver.log. We would require the nxerror.log and the node directory.

/Mth

[jsbien]

In logs I found only several occurrences of messages like this:

[removed]

I try enclose the requested logs. The nxserver.log is from today only but it covers the today’s unsuccessful connection.

 

 

[Britgirl]

can you send the logs to forum[at]nomachine[dot]com making sure you use the title of the topic in the subject of your email. I’m not sure what link you wanted to include, if the linked webpage doesn’t contain the stored logs nor be related to the problem in discussion the keymaster will remove it. Thanks.

[jsbien]

Another attempt to upload the logs. BTW, I’m afraid I don’t understand you, as I haven’t include any links in my previous post.

Attachments:

1. node.zip
2. nxserver20-12-01.zip

[Britgirl]

There was a link pointing to bitbucket.org which from what you wrote was a mistake, nevermind 😉

[Mth]

Hello.

The logs suggest that there is still problem with wayland and pipewire.

Since the forum post you mentioned we have changed the Wayland handling, so I would suggest to revert the change you made: edit the /usr/NX/etc/node.cfg config file and comment the key:

DisplayServerExtraOptions "-wlmode compositor"

or remove the “-wlmode compositor”

Then please follow the article:

https://www.nomachine.com/AR04R01083

on how to enable Wayland capturing.

Please let us know if there are any problems with this solution.

/Mth

[Author]

Posts