Forum Replies Created
-
AuthorPosts
-
February 13, 2023 at 09:56 in reply to: Blank the physical screen when somebody connects does not work #42924
BritgirlKeymasterScreen blanking works as far as we are aware across all supported platforms. Please state the distribution and version, plus the desktop environment assuming that you are connecting to Linux.
February 10, 2023 at 17:56 in reply to: Private: How to turn off the “Press the disconnect button to disconnect” prompt #43355
BritgirlKeymasterSorry for the delay in responding.
Can you update to the latest NoMachine version both sides and tell us the steps to reproduce, specifying also the OS on both of the servers you are connecting to? Also, the products you have on each of these servers and what type of session you are using to connect (physical desktop, virtual desktop?).
Thanks.
BritgirlKeymasterHi,
please tell us:
1) macOS version of the iMac
2) macOS version on the Macbook ProWe need the server-side logs (so the iMac) which show the input/output error. From a terminal on the iMac, run
nxserver --debug --enable all, reproduce the problem and thensudo /etc/NX/nxserver --debug --collectand send us the file to forum[at]nomachine[dot]com. Please use the topic’s title as the subject of your email. Thanks.
BritgirlKeymasterPlease answer these questions:
– The laptop, server-side, is Linux right? If so, what distro and version, and what desktop environment?
– Wayland or Xorg?
– Did you install the latest version of NoMachine?
– what settings did you change in NoMachine?
– can you tell us what output devices are listed in your system?
BritgirlKeymasterWhat are the exact steps to reproduce this in Mari? Also, on the NoMachine Player side (where you are connecting from) can you try disabling auto-repeat?
BritgirlKeymasterDid you install package from our website or from the aur repository? We tried the packages from the aur repo on the fly and they indeed behave in the same way as what you are experiencing. Maybe tell the guys who handle the repo at https://aur.archlinux.org/packages/nomachine?
You can check what you have set by running:
sudo /etc/NX/nxserver --startmodeIf the output is similar to this, then it’s the packages which are messed up:
NX> 807 Service NoMachine status is: Automatic NX> 807 Service NXD status is: ManualTo change it run
sudo /etc/NX/nxserver --startmode nxd automatic
BritgirlKeymasterHi, can you tell us what application it is your using (where does that menu come from?).
BritgirlKeymasterYes you can but with some limitations. Please check out the section on webcams in this article:
NoMachine USB forwarding limitations
https://kb.nomachine.com/AR03R01080
BritgirlKeymasterAre you connecting to a virtual desktop session or a physical desktop session?
Can you disable HW decoding in NoMachine on the Mac side? You can disable it completely in the player.cfg. Please 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’).
February 7, 2023 at 12:02 in reply to: Mic-in feature not working/no sound in phone Bluetooth #42873
BritgirlKeymasterOr passing mic from a pc client to a remote server is also not working?
Is the mic enabled in the NoMachine’s app allowed permissions? (Look in Settings -> Applications and scroll down to NoMachine).
The v8 update is in its final stages now.
BritgirlKeymasterHi
Logs show nothing wrong with NoMachine, but with your environment. You have Ubuntu, but Kubuntu-Desktop is installed and we cannot be sure how it was installed. Logs show you are using GDM and even Gnome works fine. Anyway, there is a way to find out how NoMachine sessions are being created. First log on locally to the KDE desktop, then go to your NoMachine client side player and start a physical desktop session to the KDE desktop with NoMachine.
Open a terminal and run
echo $XDG_CONFIG_DIRS
The output must be used inside the CommandStartKDE command:
CommandStartKDE "/usr/bin/env XDG_CONFIG_DIRS=output_of_the_echo_command /usr/bin/dbus-launch --sh-syntax --exit-with-session /usr/bin/startplasma-x11”If that doesn’t help, we don’t know what else to suggest. Environment configuration (beyond the default one) is not really within the scope of these forums.
BritgirlKeymasterI suggest you watch out for version 9 which implements NoMachine Network.
https://www.nomachine.com/network
Thanks for evaluating us nonetheless.
BritgirlKeymasterSubmit screenshots and logs to forum [at]nomachine[dot]com. Thanks!
BritgirlKeymasterBy setting in the Connect Policy key
desktop=1in server.cfg you should set the #CommandStartKDE “” key in node.cfg (not the DefaultDesktopCommand key)CommandStartKDE "env XDG_DATA_DIRS=/usr/local/share:/usr/share:/var/lib/snapd/desktop /usr/bin/dbus-launch --sh-syntax --exit-with-session /usr/bin/startplasma-x11"Does this help?
BritgirlKeymasterSupport for Pipewire in NoMachine was added in v8. So you have two choices:
1) update to version 8. If you update you should also execute the command:
sudo /usr/NX/bin/nxnode –audiosetupOtherwise uninstall v7 completely and install v8.
2) if you don’t want to update, you could also try the workaround which we provided for Ubuntu.
How to enable audio on systems relaying on PipeWire for sound
https://kb.nomachine.com/AR07T01168 -
AuthorPosts
