Forum Replies Created
-
Posts
-
On Windows the pointer cannot be hidden, because it is drawn by Windows on a lower level which we don’t have access to. On Mac and Linux the pointer is hidden.
Hi, right now we don’t support HW encoding on RPi. At the moment, we’re currently working on HW decoding for the Raspberry Pi based on V4L2, though we’re not able to give you an ETA for the decoding functionality. Once that’s added, we’ll then be able to start on HW encoding.
Note that the default behaviour is the following: when the system account is the same, NoMachine assumes by default that the connecting user is also the same and performs the automatic migration of the session from one device to the other. E.g. user A connects. User B logs in from a different device but with the same username and credentials of user A: session closes on the device of user A and it’s re-opened on the device of user B.
What you can do is this if your two users are logging in with the same username: untick the option “Don’t require acceptance if the user logged in as the owner of the desktop” on the NoMachine server side, the machine you are connecting to (see image). The default setting is to not require acceptance when the owner of the desktop logs in. Unticking it means that when the second user connects (who is still the owner given that the account is only one and it is shared with the first), the first user will be asked what he wants to do. When the first user accepts, they will be disconnected and the second user will then be able to log in.
Attachments:
where different users with personal host machine accounts get locked out of their own account because another user just closed the NX session without first signing out.
I understand you have 2 users, each with their own system account. Getting locked out can happen when the first user does not sign out correctly. I.e they just close the window without logging off from the system.
We have this key in the server.cfg which can help with this. You can force the log out.
#
# Enable or disable the automatic logout of the user from the system
# upon disconnection of the NoMachine session.
#
# 1: Enabled. NoMachine will execute the forcelogout.sh script. The
# automatic logout can be effective only if the command set in
# script is appropriate for the system.
#
# 0: Disabled. When disconnecting the NoMachine session, the user is
# not automatically logged out of the system.
#
#LogoutOnDisconnect 1NoMachine immediately unticks it with no explanation of why. Likewise if I try and untick “Don’t require acceptance if the user logged in as the owner of the desktop” it won’t let me do that either?
We are not able to reproduce any problems with with tick/unticking of those settings in GUI. We will therefore need logs. Please follow the instructions for your platform in the article here: https://kb.nomachine.com/DT07S00243. Attachments can be sent via email to forum[at]nomachine[dot]com, making sure to use the title of this topic as the subject of your email. Thanks!
On your macOS, please go to System settings -> Notifications and check that the option “Allow notifications when mirroring…” is enabled.
Unfortunately, the problem is with the drivers of your HW encoder and not with NoMachine, so in this particular case, tweaking NoMachine will not help.
Which hardware platform are you installing the packages on? Raspberry Pi, something else?
The version of ARM that you have installed, where did you get it from?
Logs would be useful. We’ll need NoMachine logs from the device. Follow the instructions here: https://kb.nomachine.com/DT07S00243 and then submit them to forum[at]nomachine[dot]com using the topic’s title as the subject of your email. Thanks!
Hi, we’re working on not showing that bar except for when there is a double swipe for the next update. Thanks for taking the time to provide feedback about the app 🙂
We aren’t aware of similar issues with RHEL 8.
When you reinstalled did you remove all traces of the installation? I.e did you do:
sudo rpm -e nomachine-small-business-terminal-server sudo rm -rf /usr/NX /etc/NXIf not, please reinstall and remove traces, then reinstall.
After which, we’ll need logs from the NoMachine server side. Follow the instructions here: https://kb.nomachine.com/DT07S00243 and then submit them to forum[at]nomachine[dot]com using the topic’s title as the subject of your email. Thanks!
NoMachine does not install any DE. A desktop environment is a requirement of being able to get a functional NoMachine installation. NoMachine is designed to work out-of-the-box on Linux headless machines provided a desktop environment is installed. NoMachine is able to detect when the X server is not running and run its own virtual display, which is an embedded X server.
Please consult https://kb.nomachine.com/AR03P00973 for more information on how to use NoMachine on a headless Linux 🙂
Connections via SSH are only available in the Enterprise products. As I suggested, take a look at Enterprise Desktop Evaluation.
Can you tell us which specific notifications are not showing in the NoMachine session but are showing on the physical macOS desktop? Some screenshots would be useful.
We aren’t aware of any of the issues that you described on the supported distributions and desktop environments. Can you tell us what distro you are using and what DE is installed there? What is set in the DefaultDesktopCommand key in the node.cfg on the server?
What you can do is run:
grep ^Exec /usr/share/xsessions/* in a terminal and then use the output as the argument in the node.cfg DefaultDesktopCommand key as explained here: https://kb.nomachine.com/AR04K00667#2 (2. How to run a non-default virtual desktop environment).
