Forum Replies Created
-
Posts
-
Hi, your using a 9.1 server and a fix for the crash is already in version 9.2. However, in your case that crash is happening because of the following bug for which we have a Trouble Report already open: https://www.nomachine.com/TR10W11586. A fix for that issue is planned for the next maintenance release.
Now it’s clearer, we previously understood that a connection from your Windows client failed to connect as well. Take a look at the following https://kb.nomachine.com/AR06U01201 which explains how multi-monitors currently works in NoMachine.
Did you already try the following (they are the same steps as the other article you linked)?
– Open the NoMachine menu panel inside the session (ctrl+alt+0 or click on the page peel in the upper right corner of the window)
– Click on ‘Display’
– Click on ‘Resize remote display’ then on ‘Fullscreen on all monitors’It’s important that Resize is enabled, then on Fullscreen on all monitors. Can you show us a screenshot of the Display settings maybe?
There is also a Trouble Report open https://kb.nomachine.com/TR03U10791. When the X11 vector graphics mode is disabled, multiple monitors of the client are not treated as separate monitors. We are not sure if this is your case, but please check this setting in the ‘Server settings’ -> ‘Performance’ on the Linux host.
Hi, if you are unable to connect, can you show the error message you see? A screenshot will suffice. Can you describe the problem with multi-monitors, what is not working exactly?
Logs from both client and server machines would also be useful. You can extract them using the instructions here: https://kb.nomachine.com/DT08U00298#1.1.
Send them to forum[at]nomachine[dot]com. Please use the title of this topic as the subject of your email. Thanks!
This is a duplicate of https://forum.nomachine.com/topic/very-small-application-font-size-on-fedora-43.
Hi, there is a Trouble Report documenting the issue here and it includes a workaround as well which you can use: https://kb.nomachine.com/TR11W11619. The fix is already lined up for the next maintenance release.
Hi, seeing the logs would be useful from the server machine you are connecting to.
Send them to forum[at]nomachine[dot]com. Please use the title of this topic as the subject of your email. Thanks!
The instructions are here: https://kb.nomachine.com/DT08U00298#1.1
Got the logs, thanks Jesse. We’ll be taking a look and will let you know soon. Good to know the workaround temporarily solves the issue!
Tar.gz is the most universal package. Not all Linux distributions have a package manager which supports rpm or deb. So for those die-hard Linux users who want to use NoMachine on distros that we don’t officially support, or that doesn’t offer their own package manager, they can opt for the tar (Tiny Core and earlier versions of Slackware for example, Gentoo and Arch as well, https://kb.nomachine.com/AR03L00789). We don’t like to exclude people from trying the software just because they are not using one of the traditional distributions. Good luck with your search. Maybe in the future you’ll give us another chance.
Hi, it looks very similar to this known issue:
https://kb.nomachine.com/TR11W11619
Can you try the workaround there? We’d also be happy to take a look at the logs to check. Follow the instructions here: https://kb.nomachine.com/DT08U00298#1.1 and send them to forum[at]nomachine[dot]com. Please use the title of this topic as the subject of your email.
If the logs confirm the exact same problem, we’ll send you a fix to try.
Hi, when you try connecting from the Macbook to the Linux server, do you see a black screen or a message? If it’s a message, can you show us a screenshot? Not seeing the local LAN connection of the Linux server on your macbook might be because maybe the macOS is not configured for LAN access in Privacy & Security in the system settings? I know you said it was working before, maybe something changed when you updated NoMachine to version 9.2.18? What version of macOS is it?
(P.s ideally you should update your legacy v7 Linux server to a more recent version. If you prefer to update first to v8, please contact us for a private link to the packages as they are no longer public.)
It’s probably better to split the topic now that you have resolved the problem of not being able to uninstall, and give it the correct title. You asked in an earlier reply about whether we can make the process of installing the application on Linux a lot less convoluted. Well, we can say your install process was convoluted, no? Use the DEB the next time 😉
If you wish to continue the discussion about NoMachine not working correctly on your Pop!_OS COSMIC installation, let us know. Our own tests show that NoMachine sessions connect and work correctly. It would be useful to know what specific “action is not possible”. Do you mean you can see the desktop but can’t input anything?
Hi, this topic is similar to the one posted here https://forum.nomachine.com/topic/nomachine-main-ui-wont-open-on-windows. We have not been able to reproduce this issue with any of the multiple Windows systems with WSL enabled in our labs. It is likely due to a particular combination of tests and drivers that we have no way of verifying. We are continuing to investigate, however, and we will update your topic with our findings.