Forum Replies Created
-
Posts
-
Hi,
can you check if that still occurs after disabling hardware decoding on the client? To do so, open the session menu panel (by pressing Ctrl+Alt+0 or by the page peel), enter Display settings, click Modify for the advanced option and check ‘Disable client side hardware decoding’.
Hi,
you can already set the number of cores to be used for encoding in the ‘node.cfg’ file on the server, by editing the ‘DisplayEncoderThreads’ configuration key. That said, it has to be noted that NoMachine, by default, already chooses the best number of cores for encoding, basing on the number of available cores.
The .Xmodmap file is taken into consideration by the XQuartz X server on the Mac, but will be ignored on the Linux side. When you use ‘ssh -Y’, the X server the application is connected to is XQuartz on the Mac. On the contrary, when you connect via a NoMachine virtual session, the virtual X server the application connects to runs on server side. The correct way to achieve the same behaviour with a NoMachine virtual session is to run this command in a terminal inside the session:
xmodmap -e "keycode 79 = KP_F1"(Note that normally the keycode for the NumLock key is 77 on Linux and not 79 as it is for XQuartz.)
There seems to be some issue with the drivers. Please try to edit the $HOME/.nx/config/player.cfg file and change the ‘Enable hardware accelerated decoding’ key to:
<option key=”Enable hardware accelerated decoding” value=”disabled” />
But changing the ‘DefaultDesktopCommand ‘ to the one suggested by you allowed the user to login but the graphics acceleration seems to be missing.
Acceleration by means of VirtualGL can be enabled either explicitly by the vglrun command (even only for specific applications) or implicitly for the whole desktop by the
'nxserver --virtualgl yes'command. That DefaultDesktopCommand was provided to you assuming you were using the second method. You can find further details in https://kb.nomachine.com/AR05P00982.Furthermore, when I used my version of ‘DefaultDesktopCommand ‘only one of my clients with Mac could not create a NoMachine session.
Can you send the logs from this specific case?
Disabling H.264 solved the issue for Liftaren. Is it the same for you?
And can you both try to check ‘Disable client side hardware decoding’ in the Display settings tab of the menu panel (Modify button)? Is this enough to solve the problem even when using H.264?
And as Britgirl mentioned, logs would be useful, especially client side logs:
Hi,
it’s not clear to me if you are talking about the username/password you have to enter to connect to the server, or the credentials you have to enter into the remote desktop’s login window (when you are already connected with NoMachine to the Debian machine) to get to the user’s desktop. Can you please clarify on this point?
That said, would you send us the logs? You can use instructions in https://kb.nomachine.com/DT11R00182 for the server side, and https://kb.nomachine.com/DT11R00181#2.1 for the client side. You can send them to forum[at]nomachine[dot]com by referencing this topic.
When its checked, Player window should automatically lose focus when mouse leaves the window and on mouse enter, it’ll be focus as it is now.
This is a feature some Operating Systems have, generally called ‘focus follows mouse’. I do believe that the Player window should not interfere with the normal rules imposed by the OS about how the focus is moved, even if it would be possible to do so.
However, in case you don’t know already, there is a key combination to release the mouse when it is grabbed by the Player window: Ctrl+Alt+Left mouse button. Would this help you?
Hi,
what you want to achieve is not currently possible and, to be honest, I think it could be unexpected and difficult to understand for most users in the most common setups. Thank you for your interest in NoMachine 🙂
Hi,
it seems like you are in view-only mode. Please check the value of the ‘PhysicalDesktopMode’ key in the ‘/usr/NX/etc/server.cfg’ file, change it to ‘1’ or ‘2’ if necessary, then try again.
Hi Whitecatkeke,
please gather logs while reproducing the problem with pipewire (that is, as you say, the ‘compositor’ option) and send them to forum[at]nomachine[dot]com. You can find instructions in https://kb.nomachine.com/DT11R00182.
As for ‘egl’, is the Wayland Gnome option reported as available in the login window? What are the exact Manjaro and Gnome versions?
Hello,
NoMachine transfers the pressed key and injects it on the server at the system level. If we understand how Karabiner is working, doing the remapping of the pressed key to produce a different event, as it remaps the physical key, it should also remap the key injected by NoMachine. Since that’s not the case, it means that Karabiner works at a different level of the device handling stack and that the key NoMachine sends is interpreted by the OS by-passing the capture Karabiner does. Unfortunately we don’t know at which level Karabiner is working, so you should probably try to contact the Karabiner support.
It would be enough for the client to somehow hint at the local configuration in a way that could be parsed in a desktop start script on the server.
This is what NoMachine normally does. Do the clients have this problem only when reconnecting to an existing virtual desktop? Or even when creating a new virtual desktop?
Can you share the logs from one of the problematic sessions? You can find instructions in https://kb.nomachine.com/DT11R00181. Please also tell what is the expected keyboard layout for that client.