Forum Replies Created
-
AuthorPosts
-
Britgirl
ParticipantWhich 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!
Britgirl
ParticipantHi, 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 🙂
Britgirl
ParticipantWe 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/NX
If 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!
Britgirl
ParticipantNoMachine 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 🙂
Britgirl
ParticipantSend the image to forum[at]nomachine[dot]com please.
Britgirl
ParticipantConnections via SSH are only available in the Enterprise products. As I suggested, take a look at Enterprise Desktop Evaluation.
Britgirl
ParticipantCan 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.
Britgirl
ParticipantWe 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).Britgirl
ParticipantCan you tell us the exact message that appears when you try to start a NoMachine session to the server? A screenshot of the dialog maybe. Also, the logs that you gathered from the server would be useful.
March 28, 2023 at 17:44 in reply to: Can’t get HW encoding working [Fedora 37, intel UHD P630] #43633Britgirl
ParticipantWe received them, thank you, and will be analyzing them as soon as possible.
Britgirl
ParticipantHi, SSH connections are available in the Enterprise products. If you have installed Free Edition on the server side, consider installing, instead NoMachine Enterprise Desktop Evaluation.
You can compare the two products here: https://www.nomachine.com/remote-access-for-everybody.
Britgirl
ParticipantThe dump shows a crash of the hardware decoder, possibly related to the drivers. You could try disabling HW decoding. You can try first via the NoMachine Connection Menu (Ctrl-Alt-0 -> Display -> Advanced -> Disable client side hardware decoding) if you’re able to start the session and open the menu. Otherwise,locate the player.cfg on the Linux client and change the follow key <option key=”Enable hardware accelerated decoding” value=”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’).
Britgirl
ParticipantThanks for posting. We also found our own workaround that works with a headless set-up.
1. disable xserver
sudo init 3
2. edit /usr/NX/etc/node.cfg and set:
DefaultDesktopCommand "/usr/bin/startfluxbox"
3. restart nxserver
sudo /etc/NX/nxserver --restart
March 27, 2023 at 09:54 in reply to: Erratic mouse cursor behavior after clicking onto another monitor #43607Britgirl
ParticipantWhat macOS is it on the MacBook and what desktop enviroment is on Ubuntu? Do you have two monitors on the macOS side? Is it possible for you to submit a short recording showing the problem?
March 27, 2023 at 09:48 in reply to: Two factor authentication with SecurID using the NX protocol #43606Britgirl
ParticipantThanks for reporting. This needs further investigation and to do so we are trying to get access to the latest PAM authentication agent for Centos 9f from RSA. In the meantime, could you tell us if with SSH everything is working?
This topic might be better investigated via a support ticket if you have a subscription.
-
AuthorPosts