February 1, 2022 at 22:38 #37293
I am trying to set up NoMachine 7.7.4 (free version) to remote to one machine running openSUSE Tumbleweed with KDE Plasma (Wayland) from another machine with the same OS/UI stack. The remote machine has dual monitors; however, only one of them is displayed correctly. The other one shows up in the configuration as a black screen and NoMachine won’t actually display it.
Furthermore, NoMachine maps the cursor from the client’s one screen to both remote screens, so while I can only see one screen, I can click anywhere on either screen.
Any ideas for getting this resolved?February 4, 2022 at 10:54 #37323fra81Moderator
we would need to take a look at the logs. Please check here how to gather them: https://knowledgebase.nomachine.com/DT11R00182. You can send them to forum[at]nomachine[dot]com, by referencing this topic.February 4, 2022 at 20:30 #37329February 7, 2022 at 11:12 #37357
Logs received thank you!February 10, 2022 at 18:49 #37440
Hi LorenDB, we would like to send you a link for a new package to install, and you tell us if the fix helps. Please check your inbox for direct emails from us.February 14, 2022 at 19:28 #37519
I installed the patched version but now my Windows machine I’m trying to connect from refuses to connect. It gives me a 108 Reset By Peer error. I’m emailing the logs from the Windows machine. I will be happy to reproduce the Linux logs as well if needed.
Furthermore, I tested from another Windows machine but that machine wouldn’t connect due to an input/output error.February 15, 2022 at 10:07 #37523
Send the Linux logs over so we can check. The ones you got from the Windows client didn’t attach, so send them on as well.February 15, 2022 at 20:07 #37550
Ooops, I think I forgot to attach the logs to the email! :O
On a brighter note, the Wayland fix package now works when I log in from my Linux laptop, which is really all I need. I’ll go ahead and collect logs of the Windows problem though just in case you find them useful.February 15, 2022 at 20:22 #37551
Will wonders never cease? 🙂 Suddenly the Windows connection works as well.
While you have my previous logs, you may want to look into another problem that I’ve noticed: screen blanking doesn’t work on Wayland.February 16, 2022 at 12:06 #37565
If the patched package solves the problem and the connection problems you were experiencing are no longer there (I doubt these were caused by the package), then logs are no longer necessary.
Regarding the screen blanking on Wayland, D-Bus and PipeWire must be present and properly working on the system. You should follow the tips and instructions here:
Notes for connections to Linux physical desktops running Wayland
This topic was marked as solved, you can't post.