Forum Replies Created
-
Posts
-
It should be ok client side. Check the list of trouble reports here for current known issues regarding Wayland.
https://kb.nomachine.com/trouble-reports?s=waylandis the move to the new Intel APIs still coming in the next release?
Yes, it is.
Hi, the extraction location is not important, as
--subscriptionsetinstalls the license in our etc folder 😉Hi, from the logs you sent we confirm that you are encountering two issues, both already known, initially reported on different distributions. The main capture method nor the fallback work correctly.
Capture of the Wayland desktop by EGL doesn’t work with KDE Plasma 6
https://kb.nomachine.com/TR05V11141Attaching to the physical desktop could fail on Rocky Linux 8 with Wayland
https://kb.nomachine.com/TR03U10784Until the fixes are released for those Trouble Reports, you can try disabling Wayland and use X.Org instead, or try with an alternative desktop environment.
If the monitor on the Win11 machine (server) is on, it connects fine. If the monitor on the Win11 machine is off, it fails.
In the logs that you sent us we see that every capture method fails when you have the monitor off. The best workaround, if you don’t want to keep the monitor on, is to try with a dummy HDMI dongle.
Related article is this: https://kb.nomachine.com/AR05S01124
New logs were clean. So I come back to my original question. Is the NoMachine server you are connecting to headless (i.e without a monitor) or maybe there is a monitor but is turned off? If it is turned off, turn it on and try again.
This article handles what to do if the Linux machine is headless
https://kb.nomachine.com/AR03P00973Hi, what you need is the rpm package for ARMv8 (aarch64). We have not tested Fedora Asahi, but we are happy to receive your feedback about it (and we can update the installation notes in the knowledge base). We are working on improving support for Wayland on ARM devices, so in the meantime you should disable Wayland and use X.org instead.
Hi, yes we did. Apologies for not coming back to you sooner. Feedback from our developers suggests that further investigation might require a debug package. I’ll come back to you if that’s the case.
This might be related to a known issue for which we have a Trouble Report open, but we’d like to check the logs first if that’s possible. Can you send us the NoMachine logs from the Raspberry device? You can extract them using the instructions here: https://kb.nomachine.com/DT07S00243. Logs from the Mac client as well can be useful as well.
Send them to forum[at]nomachine[dot]com. Please use the title of this topic as the subject of your email. Thanks!
Then after that can you try disabling Wayland? This is the link to the issue already known.
Black screen when connecting to Raspberry Pi boards
https://www.nomachine.com/TR10U11031When you say you “can’t control it”, what do you mean exactly? You can’t click on anything or something else? Have you tried the other view modes such as resizing the remote display? You can access the from the connection menu (Ctrl-Alt-0 or page peel)
You can read more about these view modes here: https://kb.nomachine.com/DT09T00266#5.4
If you’ve tried changing the view mode and that doesn’t help, please send us the logs from both the Windows and Ubuntu machines. You can extract them using the instructions here: https://kb.nomachine.com/DT07S00243.
Send them to forum[at]nomachine[dot]com. Please use the title of this topic as the subject of your email. Thanks!
Let us know because, as I said, and albeit we don’t officially support Manjaro, our tests show that it installs ok and there are no boot problems.
Development is in its final stages. We don’t have an official date for the release yet, but we are working hard to make it available by the end of this summer.
This looks like a problem with permissions on the macOS side. Please check this article for the steps to perform: https://kb.nomachine.com/AR11Q01061. You should make sure that you see NoMachine in Accessibility, Screen Recording, Full Disk Access. If NoMachine is not among the allowed apps, add it. If it is present, remove and re-add.