Forum Replies Created
-
Posts
-
Server logs look clean. We would need the Player side logs, from the client machine you are connecting from.
These are uptodate instructions for extracting the logs we need: https://kb.nomachine.com/DT07S00244
Also, you say you disabled HW decoding. How did you do that? It needs to be disabled completely on the Player side in the player.cfg file.
Edit the file $HOME/.nx/config/player.cfg and set the configuration key “Enable hardware accelerated decoding” to “disabled”. Before changing the configuration key, you should first quit the NoMachine Player (you can do this by right clicking on the !M icon in the system tray and selecting ‘Quit NoMachine Player’.) Then, try to connect again.
If you’ve done this and still encounter the issue, then send Player logs as I just mentioned.
Hi Timewalker, sorry for the delay. The logs you sent actually show that you have hardware encoding enabled on the server side. Please try disabling it, this worked for the other users. On the server, go to Server -> Settings -> Performance and untick the “Use hardware encoding” box. Restart the server and try and connect again. Another thing I should point out is that NoMachine uses the native AMD encoder, not the VA-API, so there could be some misconfiguration in the system perhaps?
If you don’t wish to attach your screenshot of the Player settings (the Player on the device you are connecting from) you can send to forum[at]nomachine[dot]com. Thanks.
Logs are from the Player side only which don’t show the cause of the black screen which is server side 🙂
Can you tell us the desktop environment you are connecting to on the Ubuntu machine? Can you try to execute point 3 again of the article that you consulted (stop gdm and restarting the nxserver).
Failing that, we will need the logs from the server side as katpan requested. Logs for version 8 can be extracted using the instructions here:
Hi
I tried full screen on all monitors but that just stretched the current display across the 2 monitors in a very non-useful way. Is this possible with the free version?
The feature you need is planned. It will allow multi-monitors on the server side to be treated as separate windows on multiple monitors on the client side. In each of these separate windows it will be possible to apply all the usual settings, like applying a different scaling factor, resizing the window to any size, sending the window to fullscreen and placing the window in any desired location. This will apply to connections to the physical desktop and to virtual desktops/custom sessions. The latter are available only in the Enterprise products.
In the current version it’s possible for virtual desktop sessions (Enterprise products only) to be spanned on all monitors or to a specific monitor.
This is actually an issue which we are aware of so no further logs are necessary. You can see the Trouble Report here:
Audio doesn’t work on Ubuntu 22.04 with PipeWire installed
https://kb.nomachine.com/TR11T10696We have reproduced a similar issue when using a 4k monitor with 150% scaling or similar to connect to the desktop. Does this sound similar to your set-up?
Password authentication is the default authentication method suitable for the majority of environments. In some cases -even according to Company’s policies- it may be preferable to adopt a different authentication method such as key-based authentication. We recommend to refer to manuals of your Operating System for more details. Please also check our online article here:
How to set up key based authentication with NX protocol
https://kb.nomachine.com/AR02L00785any way to automate the account login
It is possible to save the password and username for the NoMachine connection by checking the box “Save this password in the connection file”.
Having a NoMachine server for Android could be a possibility to allow customers to receive remote assistance on their device, for example, but that use case represents a very small percentage of our customers. It’s something we have evaluated but not officially added to our roadmap yet, given that we have always focused on bringing the full computing capacity of a “remote desktop” to the user. So, it’s something we’d like to do, but for the moment remote mobile device support is not currently a priority.
So we will more info because we have been unable to reproduce this behaviour. Send us:
output of setxkbmap -print
output of ‘xev’ when you press those keys
file layout.txt generated with that command
xmodmap -pke > layout.txt
There is a bug we are aware of in Gnome that is documented here: https://forums.nomachine.com/topic/hang-after-password-entered#post-39200
Can you try the workaround there?
In the logs we see the following server.cfg key is empty, when it should not be:
AvailableSessionTypes.What should be written there is ‘physical desktop’. Without this, no display can be started. Why it’s empty for your v8 installation, but not for v7 is not clear since we cannot reproduce this behaviour. Please check your server.cfg file has
AvailableSessionTypes physical-desktopindicated. Then restart the NoMachine server.Further reference:
The server.cfg and node.cfg files explained
https://kb.nomachine.com/AR02N00877point (2) about the ‘AvailableSessionTypes’ key
The AvailableSessionTypes key is present in both server.cfg and node.cfg and permits to define which types of session will be made available to end-users. When server.cfg and node.cfg are on the same host, the list of session types must be the same in both keys. These keys are automatically populated at installation time. If a new session type is added later, they have to be edited manually. Restart the server to make this change effective.