Forum Replies Created
-
AuthorPosts
-
December 30, 2022 at 13:33 in reply to: Waiting for the desktop user to authorize your connection #42235
Britgirl
KeymasterIs that a screenshot from the computer you are connecting to?
When user John disconnects, what is seen? Can you show a screenshot of what is visible when John disconnects?
Britgirl
KeymasterPlease contact us via the website for this request. In the footer, select Contact Us and then select General Enquiries.
Britgirl
KeymasterYou can send any attachments to forum[at]nomachine[dot]com. Make sure you use the title of this topic as the subject of your email. Thanks!
December 30, 2022 at 09:22 in reply to: Input issues between Win10 Client and Linux Mint server #42214Britgirl
KeymasterThe link we sent in the email to you to download is for a package that contains a patch. We were interested in knowing if it fixes the issue completely. If you get a chance to test it, please do 🙂
Britgirl
KeymasterServer 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.
December 29, 2022 at 18:21 in reply to: Input issues between Win10 Client and Linux Mint server #42205Britgirl
KeymasterDid you get a chance to test the package we sent? 🙂
Britgirl
KeymasterHi 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?
December 29, 2022 at 17:48 in reply to: Ooops! Could not initialize the connection, please verify your proxy settings. #42198Britgirl
KeymasterIf 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.
Britgirl
KeymasterLogs 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:
Britgirl
KeymasterVote registered 😉
December 28, 2022 at 15:22 in reply to: Multiple monitors on server (Ubuntu) and client (Windows) #42177Britgirl
KeymasterHi
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.
Britgirl
KeymasterThis 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/TR11T10696Britgirl
KeymasterWe 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?
Britgirl
KeymasterHi, it would be useful to know what OS version you have on the M1.
Britgirl
KeymasterPassword 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”.
-
AuthorPosts