Forum Replies Created
-
Posts
-
Logs were received from the client side, the computer you are connecting from. We need to see the logs of Windows server, “the Windows host that you are connecting to“. See the section “First Step” in the guide I linked to in my previous reply. Thanks.
Have you tried running
sudo nxserver --restartafter switching to desktop mode on the problematic Steam host?Are the devices able to ping each other?
Logs don’t pinpoint to a specific issue as such but updating to the next maintenance which is to be released shortly is a good idea. Then you can come back to us if re-encounter the problem.
This kind-of-worked – but things were VERY slow. I then installed the plasma-session-x11 package, and changed the line to:
DefaultDesktopCommand "dbus-launch --exit-with-session /usr/bin/startplasma-x11"You could also try
DefaultDesktopCommand "dbus-launch --exit-with-session startkde"There even seems to be some interaction with local applications if the NoMachine connection is up.
Do you mean that even if the application seems to hang, the user can still move the mouse and/or key press events show on the remote desktop?
Is the display server Wayland or Xorg?
What desktop environment is the user connecting to on the EL host?
Is the user connecting to a free NoMachine host? Is it headless?Hi, connecting from macOS and Windows to the Ubuntu server are ok, but connecting from Ubuntu is not. Please send us the client side logs on after having reproduced the problem to forum[at]nomachine[dot]com.
To gather logs, please follow the instructions here https://kb.nomachine.com/DT07S00244#2.
After which try disabling hardware decoding on Ubuntu following the instructions here: https://kb.nomachine.com/AR07U01202. You should set the key to <option key=”Enable hardware accelerated decoding” value=”disabled” /> in the player.cfg file.
Are you able to send us the logs from the Windows host that you are connecting to? Reproduce the white screen issue after having followed the instructions here: https://kb.nomachine.com/DT07S00243
Send them to forum[at]nomachine[dot]com making sure to use the title of this topic as the subject of your email.
As a solution you can consider using an HDMI dongle, please check the following article about using NoMachine to connect to headless Windows hosts, https://kb.nomachine.com/AR05S01124.
Not closing the window of the NoMachine Player is something that can be handled by the operating system, not by NoMachine. About “disabling alt-tab” you could try configuring the session file with grab the keyboard enabled. That way when the user uses any combination of keys, the key presses would be registered in the session and not on the local desktop.
ahhh shame you removed the .nx folder, this could have been useful to understand why this particular Win11 is affected. If it happens again, grab the .nx folder first before doing a reinstall, then come to the forums 🙂
Hi, and welcome to the forums 🙂
you can try to disable NoMachine HW decoding on the “problematic” laptop. To do that, follow the instructions here: https://kb.nomachine.com/AR07U01202, choosing to completely disable (point 3). I’ll write them here to keep the info in this thread.
– Exit the Player (right click the !M icon in the system tray and click “Exit the player”)
– Locate the player.cfg, on Windows the path is typically %USERPROFILE%\.nx\config\player.cfg.
– Open in notepad (rename the original cfg to not lose it) and find the “Enable hardware accelerated decoding” key and set it to ‘Disabled’ like this<option key="Enable hardware accelerated decoding" value="disabled" />
– Save and close.
– Re-open NoMachine.
– Try and connect again.
– What happens? If you get the same problem, then we would need to see the logs from both client and server sides.For the server side, so the MiniPC side, please follow the instructions here for Windows, https://kb.nomachine.com/DT07S00243?s#2. Instead, for logs from the affected laptop, tick the box “Don’t delete log files on exit checkbox” in Player settings: Open the main window from the UI -> Settings -> Player -> Security panel, before starting the session to reproduce the problem. Then find the .nx folder in your user’s home, and zip it up. The .nx folder is hidden. To find it, write the following in the address bar or the file browser: %USERPROFILE%\.nx. As an alternative, you may navigate through the computer folders till the user’s home and insert .nx in the navigation toolbar to reach this hidden folder. The path can be similar to: C:/Users/nomachine/.nx.
Send everything to forum[at]nomachine[dot]com.
Hi,
Glad to know it’s now working, but we can keep this topic open for a while in case you need to report back.
After installing all the latest updates to Fedora 39, this also broke and seemed to fail in the same way.
This could be related to this TR https://kb.nomachine.com/TR04V11131 but it’s hard to say without seeing logs from that server as well.
CRCinAU, please see: https://forum.nomachine.com/topic/fedora-40-nomachine-not-working#post-48737
Hi,
your issue could be related to this Trouble Report: https://kb.nomachine.com/TR05V11141.
If you send us the logs from the server side (follow the instructions here) we can verify them. Follow the instructions here and either submit here as a zip or send directly to forum[at]nomachine[dot]com.
https://kb.nomachine.com/DT07S00243.This sounds like a problem with the macOS installation and/or the AWS instance. If the problem was with NoMachine, it is unlikely that you would be able to access other applications from the dock during the remote desktop session. You should look for apple crash reports for Safari, see this link for instructions: https://support.apple.com/en-il/guide/console/cnsl664be99a/mac