Forum Replies Created
-
Posts
-
Hi, yes, this is what we suggested in other topics on the forums, for example here: https://forum.nomachine.com/topic/windows-display-scaling-nomachine-makes-it-blurry#post-44040
We are planning to support different scaling factors for Windows in the future. At the moment, our priority is version 9 with NoMachine Network and other important features planned for that. Development can most likely start after that.
HI
thanks for the updated information. So the problem was in the drivers.
In the logs we can see:
42012 45760 2023-12-04 10:50:45 913.621 Io/Io: ERROR! Descriptor FD#16628 out of range in method ‘socket’ context [A].
Error: Descriptor FD#16628 out of range in method ‘socket’ context [A].
42012 45760 2023-12-04 10:50:45 913.621 System/System: Abort called for system at 0x0000000067095f40.
42012 45760 2023-12-04 10:50:45 913.621 System/System: Error is 22, ‘Invalid argument’.
42012 45760 2023-12-04 10:50:45 913.621 System/System: ERROR! Killing the current program.which seems to suggest a resource leak. Had you not updated the drivers already, I would have answered that disabling hardware decoding on the Windows 11 machine is the first thing to try so that we can know whether the problem is in the drivers 🙂
Hi Stefan,
what you need is NoMachine Network which is planned for the next major, NoMachine 9. Some information about Network and how it will work is available here https://www.nomachine.com/network.
Thanks for your input and we’ve registered your interest. What you wrote are all valid points to consider 🙂
Hi, you’re right about the link, it was pointing to a wrong page. The correct page is this: https://forum.nomachine.com/topic/nomachine-server-for-android-2#post-20065
To answer your question, NoMachine does not provide a server for Android. You can connect from any Android device, including ChromeOS, to reach any computer where you have installed NoMachine or one of the Enterprise server products.
Which distribution of Linux and its version do you use?
You can submit logs to forum[at]nomachine[dot]com using the title of this topic as the subject of your email. Thanks.Desktop environment is also useful to know.
I understand you are connecting to localhost. Can you send us the logs? See here for instructions and send them to forum[at]nomachine[dot]com. Please use the title of your topic in the subject of the email.
We have reproduced it! A Trouble Report will be opened and queued up for fixing. Thanks for reporting.
Not sure what to make of your response, Britgirl, but I emailed the file as an attachment to the specified email address with the number (#46174) of the post it should be attached to.
I was referring to your attachment which didn’t attach 🙂
You previously wrote ” I ran xev on the client machine and included the results in the “keys.txt” attached file.” and it wasn’t attached. So I asked for you to send it. But you’re all set now anyway.About your comment on attachments, we’ll make a point of adding what types of attachment are permitted so that users know. Right now only the size is stated. That said, some attachments don’t pass the spam filter because of unusual characters within. We’ll get this checked out. Thanks again for your feedback.
Happy nomachining!
Quite a lot of information is missing. Please provide:
– NoMachine product and version on local and remote machine (free version, Workstation, etc).
– Whether the problem arises connecting to a physical or a virtual display.
– Remote and local Windows/Mac/Linux version (Windows XP/7/8, OS X 10.x, Ubuntu xyz, Mint x.y, etc.).
– If on Linux, desktop version (GNOME. KDE, whatever) on client and on server.
– Are you using Pulse Audio or Pipewire
– Precise steps to reproduce the issue.
Hi, a quick update. We were unable to reproduce the problem. Can you update to the latest version, 8.10, both sides and let us know if anything has changed?
Submit a report to Wacom or HP by all means. We will investigate from our side what needs to be done.
Hi, your attachment didn’t attach. Can you submit any attachments to forum[at]nomachine[dot]com? Thanks!
Everyone, please follow the workaround posted in another issue, but related:
Thanks!