June 16, 2020 at 19:47 #28157
NoMachine makes available today a minor software update aimed at solving issues affecting the previous release such as green screen when connecting from Windows clients to high resolution monitors and audio not working properly when connecting to macOS server.
Here’s a few of the Trouble Reports that are fixed in this release…..
TR05R09713 – The NoMachine client on Windows suddenly terminates when connecting to high resolution monitors
TR05R09689 – Green screen when connecting by NoMachine client for Windows v. 6.10.12 to high resolution monitors
TR05R09708 – Audio and disk sharing stop working after automatic updates to v. 6.10.12
TR05R09720 – Audio is not working when NoMachine v. 6.10.12 is installed on macOS Catalina
The full list of fixes and implementations available is at the following link: https://www.nomachine.com/SU06R00210June 22, 2020 at 15:48 #28241
I updated my Windows client to this version, but after this upgrade I’m met with just a black screen when I connect to my Linux machine. Even after also upgrading the Linux machine to the same version.
Two of my colleagues experienced the exact same problem. We did have an older version lying around 6.8.1 after downgrading our clients to that version it started working again.June 24, 2020 at 13:26 #28257
I would also like to add the the problem me and my colleagues have is probably a corporate IT problem, because I can connect to my Linux machine if I install 6.11.2 on a clean Windows 10 and run that as the client. But it would be nice with some guidance on how to find the problem.June 24, 2020 at 13:50 #28263
Can you tell me what the distribution is and what desktop environment it is? What product is installed on the Linux host?
Have I understood correctly that updating the NoMachine Windows client to the latest 6.11, you cannot connect to a Linux NoMachine server also updated to 6.11?August 17, 2020 at 15:52 #29016
Strange, I wrote a reply to this in June, but I will try again.
I got these problems with 6.11.2_1 on both client and host.
Host Ubuntu 18.04 with ‘nomachine_6.11.2_1_amd64.deb’
Client Windows 10 Pro version 1903August 17, 2020 at 16:51 #29023
Can you send us the logs from both the connecting Windows client and remote Linux server? So there will be two separate sets.
Please see here for instructions on how to extract logs (once you’ve reproduced the problem) and send them to forum[at]nomachine[dot]com.August 18, 2020 at 13:14 #29029
What desktop environment are you connecting to by the way?
There’s not enough information in the logs to know what is going wrong. You would need to enable debug on the server side, reproduce and resubmit the logs. Make sure the player logs are included from the client side.August 19, 2020 at 15:09 #29055
Please check your email inbox, I’ve sent you precise instructions on what to submit.August 20, 2020 at 14:18 #29064
Thanks for the correct logs 🙂
They show that you are possibly encountering this issue here: https://www.nomachine.com/TR06R09772 . There is a workaround in the TR. Please try that and let us know.August 21, 2020 at 11:46 #29067
Well, using H264 did not make a difference, but I found a workaround:
Going into display settings (with the black screen) and checking “Disable client side hardware acceleration” I notice in the background that the image appears, so I uncheck this option again and escapes out from settings leaving everything unchanged.
Changing any of the other display setting doesn’t help.
Having “Disable client side hardware acceleration” checked when I connect doesn’t work either, then I have to click the check box twice for the image to appear.August 24, 2020 at 07:30 #29092
Perhaps I did not make it clear, the temporary change in the display setting makes it work, for that session.August 24, 2020 at 10:24 #29103
Make sure you sign up for notification of the fix 😉August 24, 2020 at 13:30 #29113
Will it come as a reply to this thread? Or where do I sign up for that notification?August 24, 2020 at 13:31 #29115
The link to the TR that I published last week shows a ‘notify me’ checkbox. Please use that 😉August 24, 2020 at 15:43 #29116
Are you referring to TR06R09772? Because that does not represent this problem since it doesn’t help to switch encoding, right?
This topic was marked as solved, you can't post.