Forum Replies Created
-
AuthorPosts
-
fisherman
ModeratorHello,
What I see this is security feature of Little Snitch.
If you do need remote access Little Snitch, you have to enable the “Allow GUI Scripting access to Little Snitch” option in Little Snitch Configuration > Preferences > Security.February 18, 2022 at 09:45 in reply to: Mac client cannot use copy and paste text to NoMachine Linux #37617fisherman
ModeratorHello,
NoMachine remote connection behaves as the local keyboard was directly attached to the server. Due to that, since you need to press Ctrl+C to copy on Linux, you have to press Control+C also when connecting remotely from the mac.
There is an open feature request that will cover that problem when it is implemented FR10M02977 – Provide an interface enabling user to configure modifier keys
fisherman
ModeratorI did not check startup scripts for the Linux Mint that loads correct theme on physical desktop. NoMachine starts command you mentioned in your post. I can recommend workaround that possibly you can use.
– Remove existing xfce settings for that user that has loaded standard xfce desktop.
rm -rf ~/.config/xfce4
orrm -rf /home/user/.config.xfce4
– log to the desktop with user physically or using NoMachine physical session
– then logout
– Create virtual desktop sessionJanuary 18, 2022 at 17:10 in reply to: Cannot connect to remote Linux server running NoMachine #37083fisherman
ModeratorIf it is headless machine I would disable lightdm to start on boot, you can do that by executing
systemctl disable lightdm.service
and then reboot machine.January 12, 2022 at 15:17 in reply to: MacOS Monterey v12.1 server – no audio sound on both Windows/Linux clients? #37018fisherman
ModeratorWhat I noticed is that you can use possible workaround to solve audio problem on Mac OS 12
sudo rm -rf /Library/Extensions/nxaudio.kext /Library/Audio/Plug-Ins/HAL/NMAudio.driver /Library/Audio/Plug-Ins/HAL/NMAudioMic.driver sudo mkdir -p /Library/Audio/Plug-Ins/HAL/ sudo cp -a /Applications/NoMachine.app/Contents/Frameworks/bin/drivers/NMAudio.driver /Library/Audio/Plug-Ins/HAL/NMAudio.driver sudo cp -a /Applications/NoMachine.app/Contents/Frameworks/bin/drivers/NMAudioMic.driver /Library/Audio/Plug-Ins/HAL/NMAudioMic.driver sudo chmod -R 755 /Library/Audio/Plug-Ins/HAL/NMAudio* sudo chown -R "root:wheel" /Library/Audio/Plug-Ins/HAL/NMAudio* sudo launchctl stop com.apple.audio.coreaudiod sudo launchctl start com.apple.audio.coreaudiod
January 10, 2022 at 16:44 in reply to: MacOS Monterey v12.1 server – no audio sound on both Windows/Linux clients? #36993fisherman
ModeratorAbout MacOS 12 we have already opened Trouble Report that will be fixed in the following NoMachine versions TR12S10423 – Sound forwarding doesn’t work on macOS 12.
fisherman
ModeratorI am glad that it helped.
fisherman
ModeratorFurthermore, problem is with nvidia drivers and not with NoMachine software.
fisherman
ModeratorBased on the output of the command vainfo executed with using drm and nvidia device that produced the crash, NoMachine will not be able to use that device and that was reflecting that NoMachine failed back to use software decoding.
January 10, 2022 at 13:35 in reply to: Cannot connect to remote Linux server running NoMachine #36977fisherman
ModeratorHello,
I am really happy that my post helped you.
fisherman
ModeratorCan you check following command
ls -l /dev/dri
there should be list of devices, one of them renderD12x will be nvidia (will be renderD129 or some other number)
then run following command
LIBVA_DRIVER_NAME=nvidia vainfo --display drm --device /dev/dri/renderD129
In last command we do following:
– we say to vainfo to use nvidia driver with LIBVA_DRIVER_NAME
– we specify that nvidia device should be used by selecting it manually as renderD12x
– the most important part is that it uses DRM, instead of default X11 for display argument – we need to use it that way in our softwarePlease then show us output of the mentioned command.
January 6, 2022 at 14:43 in reply to: Cannot connect to remote Linux server running NoMachine #36950fisherman
ModeratorHello,
What I see here is the issue with your xorg Display configuration of the headless server, that needs to be adapted to use higher display resolutions.
NoMachine when connecting to the physical screen uses only provided resolution from the system, and as you show on your screenshots that was 1366×768.
If you want that NoMachine set up screen resolution, you could use NoMachine workstation virtual desktops, or ask NoMachine to create physical display for you. More info about mentioned feature can be found here: FR10L02842 – Giving the possibility to connect a physical session in NoMachine free version when the local X server can’t be found.January 6, 2022 at 14:13 in reply to: MacOS Monterey v12.1 server – no audio sound on both Windows/Linux clients? #36948fisherman
ModeratorHello,
Can you tell us if you are using new M1 Mac machine?
Audio does not work on Apple M1 as a server, we have opened new Feature Request to natively support Apple M1, you can see more here: FR12R04054 – Offering NoMachine packages natively built for Apple M1 Chipfisherman
ModeratorHappy New Year too,
Can you tell us if you are using single or multiple display?
As well did you experienced something similar with other applications?fisherman
ModeratorI tried version 6.12.3, and version 7.7.4 and both work as expected and without issues on Windows 11. This looks as the installation problem happened on specific environment.
Please can you try uninstalling NoMachine and reboot host and report if here are any uninstallation errors. After reboot verify if NoMachine folder still exists “C:\Program Files (x86)\NoMachine”.
If exists rename it and then install NoMachine again. Important is to reboot Windows after installing NoMachine to correctly load needed drivers.If you still experience the problem, after new install, collect NoMachine logs ( DT11R00181 – Collect server and client logs manually ) and attach it to this post, or send to forum[at]nomachine[dot]com.
-
AuthorPosts