Forum Replies Created
-
Posts
-
Hi, sorry for the delay in coming back to you. Ideally we would need logs with debug enabled to dig deeper. Today, we are going to release 9.7, so what I advise is you update your installation with this new release and if you are still able to reproduce, enable debug (level Debug – 9 in the UI), reproduce and submit new logs.
Hi, on further analysis of the logs, we can see that the issue you were encountering was a minor bug that we reproduced recently and was specifically related to the update of the Enterprise Client package and only when updating through the player. A fix was already released in 9.5, but a fresh install is recommended. Future updates through the player should not be affected.
Hi, thanks for reporting this. We are also testing the preview, and our developers are currently investigating the issue further. As Golden Gate is still in Preview/Beta, there may be additional updates from Apple that could affect or change this unexpected behaviour. In any case, thanks again for flagging it, we’ll keep investigating and share any updates here.
Hi, thanks for reporting this. We are also testing the preview, and our developers are currently investigating the issue further. As Golden Gate is still in Preview/Beta, there may be additional updates from Apple that could affect or change this unexpected behaviour. In any case, thanks again for flagging it, we’ll keep investigating and share any updates here.
We have tested on the fly to see if we can reproduce and we were not able to. You say “even in”, which would suggest that for you it was broken before (?) Did you already submit a topic or perhaps a support enquiry about this issue? If you submitted a support enquiry through our website, it would be better to continue through that channel, so the support team can link up previous requests with your new report.
Please submit the logs from the Cloud Server after having reproduced the issue. You can gather logs through the UI or from the command line, further instructions are available here: kb.nomachine.com/DT08U00298. Send them to forum[at]nomachine[dot]com making sure to use the title of this topic as the subject of your email. Thanks!
Ah sorry I didn’t provide the link, check here for instructions on how to get the logs: https://kb.nomachine.com/DT08U00298. Let’s get logs from both sides – not just the server, but also the device you are connecting from when you encounter the problem.
Hi Jesse, thanks for your nice feedback 🙂
NoMachine already fully supports CachyOS with Plasma KDE on Wayland. Did you recently try? If you’re experiencing problems with the latest NoMachine version, send us the logs.
Regarding your question about desktop scaling, do you use Linux on both server and client side? Is the client using 200% desktop scaling or the server? Can you show us the problem with a screenshot or describe in more detail?
Hi, so it’s a drivers-related problem. It could have been caused by a drivers update since the last time you used NoMachine maybe? Maybe there is a more recent update that you can try?
Please tell us:
- graphics card model
- version of the drivers
- a screenshot (or a video) showing the screen tearing (you’ll have to re-enable HW decoding again)
- client side logs taken while reproducing the issue (during the session > Ctrl-Alt-O > Connection > Take the Logs)
You can attach them here or send directly to forum[at]nomachine[dot]com.
We looked at the logs and it’s as if the suggested option wasn’t set. Did you set it in server side node.cfg? Can you send us the node.cfg file from the server side to check?
Did you restart the NoMachine server after changing the WaylandModes key? If you did, send us a new set of logs from the Kubuntu machine.
How about if you connect from the Linux PC to the Windows 11 PC? Do you get the same issues? This would help us to understand if the issue is on the Win11 side or on the client side.
If it’s happening only when connecting from Win10, please try disabling HW decoding. You can do that within the session. Open the menu (Ctrl-Alt-0), go into Display > Change settings > Modify (Advanced settings) and tick the box Disable client side hardware decoding. Does that help?
If nothing changes, we need to logs from both sides. For client-side logs, simply open the menu again > Connection > Take logs. For the server side system you are connecting to, go to Settings > Server > Security > Take logs. Submit everything here or send to forum[at]nomachine[dot]com. Please use the title of this topic as the subject of your email. Thanks!
It looks like a drivers issue and very similar to this problem:
Updating the drivers would be the solution as suggested by everstar. If that’s not possible, you could try changing the screen capture mode by setting this key in node.cfg:
WaylandModes drm,egl,compositorI’m sorry, I just noticed I gave you the wrong command to use in 2. It should be:
2. ([Security.Principal.WindowsPrincipal][Security.Principal.WindowsIdentity]::GetCurrent()).IsInRole(544)
although it seems you are a system user anyway.
What is the OS on the system you are trying to add to Network? And can you send us the logs from that machine? (Settings > Server > Security , Take logs). Please send them to forum[at]nomachine[dot]com to avoid any sensitive information being made available here.
Hi, we are unable to reproduce and can run that command successfully as a system user in Powershell and the machine was added to NoMachine Network. Can you show us the output of the following?
1. whoami
2. $(([Security.Principal.WindowsPrincipal][Security.Principal.WindowsIdentity]::GetCurrent()).IsInRole(544))” | Out-File $log -Append
3. $env:USERPROFILE
4. $env:COMPUTERNAME
5. Get-CimInstance Win32_ComputerSystem | Select-Object -ExpandProperty UserNameNoMachine streams sound that you have playing on the default output sink. So you can either disable that in NoMachine in the node.cfg or disable it from the connection (https://kb.nomachine.com/DT08U00290#6). Or maybe you could stream MPV to another sink?