- This topic has 6 replies, 2 voices, and was last updated 5 days, 19 hours ago by
.
-
Posts
-
I am unable to connect to my Plasma 6 computer on Arch with Wayland. When I try to connect, I get a white screen which times out, cycles a couple of times, and I eventually get a 104 error.
Both computers run Arch, and plasma 6.2 and are using !M 8.14.2
I tried to attach the server logs, but they are just over the file size limit. I am attaching the client logs, but I can send the server logs as instructed. I tried tuning off my firewall to see if that was the issue, which didn’t do anything. FYI I have other computers on the network running plasma 6 and wayland which I can connect without issue.
Thanks in advance
This looks like the following known issue with Plasma 6, https://kb.nomachine.com/TR05V11141.
Are there any workarounds other than using X11 because none of the other capture methods seem to work either?
Hi, unfortunately there is no other alternative workaround other than using X11, but if you send us the server side logs, we can check to see what the problem is with the other capture methods? Send them to forum[at]nomachine[dot]com. The instructions are the same as before 🙂 https://kb.nomachine.com/DT07S00243, steps 1, 2 and 3 for the server machine you are connecting to.
Also useful to know:
i) Is the server running in a VM?
ii) Are you using proprietary drivers? If you are, can you possibly try the open source ones?
Hi, an update on this. You sent us the logs and you also told us you were already using open source drivers. The logs show that the capture method fails with the same errors that we have seen when proprietary drivers are in use. Can you tell us more about the open source drivers you are using? And also confirm whether the server is running in a VM or not.
Apologies for replying sooner, the notice ended up in my spam folder. I am using the opensource amd drives which are part of mesa 1:24.2.7. What addition info on the driver can I provide? Also this is not a VM.
Ok, thanks for the additional info. We confirm that the issue is https://kb.nomachine.com/TR05V11141, which developers are currently working to resolve.
You must be logged in to reply to this topic. Please login here.