Forum Replies Created
-
Posts
-
Apologies.
https://kb.nomachine.com/SU07U00247
You can access all SU using the link here: https://kb.nomachine.com/software-updates (or from the footer of the website, Software Updates)
Hi, version 8.8.1 was released in July for all platforms. You can check the software release announcement here:
https://kb.nomachine.com/SU07U00246
To stay up-to-date you can also subscribe to our news mailing-list if you wish. Go to the following URL and insert your email address:
Are you connecting to a Gnome desktop? We are aware of an issue on Alma Linux when connecting to Gnome. It is not present in the latest Red Hat or Fedora versions. It’s possible to run only 1 GNOME desktop per-user. This looks to be a limitation of dbus-GNOME on Alma Linux, not present on RHEL.
A possible solution is to adopt a different desktop environment like XFCE.
You should also check the DefaultDesktopCommand in node.cfg on the server. What is written there? Journalctl output would also be useful.
We were able to run one GNOME virtual desktop by NoMachine by using any of these command in /usr/NX/node.cfg (all on a single line):
DefaultDesktopCommand "env DBUS_SESSION_BUS_ADDRESS=unix:path=/run/user/1000/bus /bin/dbus-run-session gnome-session --session=gnome"or for GNOME classic:
DefaultDesktopCommand "env GNOME_SHELL_SESSION_MODE=classic DBUS_SESSION_BUS_ADDRESS=unix:path=/run/user/1000/bus gnome-session"To try XFCE:
sudo dnf install epel-release sudo dnf group install "Xfce"Then set in /usr/NX/etc/node.cfg:
DefaultDesktopCommand “startxfce4Have you already tried the tips in the second option in this article?
How to use Intel H.264 HW encoder with NoMachine on Linux platforms
https://kb.nomachine.com/AR09O00938We are still unable to reproduce the problem with resize connecting from any OS to Ubuntu 22 with Wayland. What I suggest is everyone update to the latest version (8.8) and open a new topic, not forgetting to submit logs from both NoMachine client and server sides.
“With Wayland, no flickering login screen, with X11 flickering login screen.”
Also here, this requires a new topic separate from the resize issue.
Iām running RHEL 8.8 and NoMachine 8.8.1-1. If it matters,
nx-libsandnxagentare version 3.5.99.26-1.That “3.5.99.26-1.” indicates an NX-derivative which is not from NoMachine and it could be interfering with the NoMachine software. So, uninstall the derivative and verify if the issue continues.
If it does, please check or share .xsession-errors file in user’s homedir on server, and the /var/log/messages or journalctl logs.
Both second attachments didn’t attach.
Before you do anything else, and before we investigate, I suggest updating from 8.2 to 8.8 which is the current version. Please do this on both client and server sides. A number of issues have been fixed since 8.2, such as a possible nx daemon crash.
If, after updating, you are still getting the same problem, resubmit server side logs and Player logs from the Windows machine.
There is a small bug in the NoMachine node.cfg on Fedora: there is the wrong value set for key AudioInterface during installation on Linux with Pipewire
The key is set to node.cfg: AudioInterface alsa
The workaround is to set manually “AudioInterface pipewire” and
nxserver --restartPlease try this and let us know if it helps.
This is very strange. Can you submit a screenshot showing the problem?
Logs would also be useful. You can gather both player and server side logs by following the instructions in https://kb.nomachine.com/DT07S00243. You can send the logs to forum[at]nomachine[dot]com.
Hi, NoMachine Network (www.nomachine.com/network) is very much on the roadmap and is nearing completion. It will be released in version 9. This is what you are referring to when you write “a connection can be established via the Internet”, I imagine š
The portable client suitable for starting connections via USB flash/pendrive is planned. However, priority was given to other features and we are unable to provide a target version right now.
Hi, we are unable to reproduce it. Can you enable debug on the affected Windows machine, restart Windows,Ā connect, and if the connection fails, collect logs and share them with us. We would also need the logs from the Player which cannot connect. Please follow the instructions here to enable debug: https://kb.nomachine.com/DT07S00243 (first through to fourth steps). Submit the logs to forum[at]nomachine[dot]com making sure to use the title of this topic as the subject of your email.