Forum Replies Created
-
Posts
-
Responding Huashan, your question is now in https://forum.nomachine.com/topic/remote-vps-ubuntu-22-04-with-xcfe4-nomachine-no-sound. This topic will now be closed.
Khaotiq, for an upcoming version we have added a “blank screen on demand” shortcut. Take a look at my answer here: https://forum.nomachine.com/topic/feature-request-add-ability-to-blank-the-server-screen-remotely-on-demand#post-46389
You could enable the keyboard grabbing and use the same shortcut to cycle windows on your local and remote desktop. However if you still want to change the default shortcut, you should do it in the remote system configuration, not in NoMachine.
First you should update to the latest version, both client and server sides. Some issues regarding audio quality in general were fixed in recent maintenance software updates. If you continue to have issues, please open a new topic and provide details of OS on the Player, OS and version on the server, desktop environment if Linux, steps to reproduce and a sample of audio.
Please try the workaround here: https://forum.nomachine.com/topic/how-to-speed-up-nm-server-startup-at-boot#post-46160
Hi, check the IP addresses for that connection by going to ‘Edit connection’. Then select an alternative one if there are multiple ones available. A screenshot showing what I mean is and my explanation https://forum.nomachine.com/topic/how-to-make-nomachine-update-target-computer-ips#post-39467
Hi, glad to know a reinstall fixed the problem and you found the article in our knowledge base about using Pipewire 🙂
A tip about Gnome sessions and not being able to connect, if you come across it again, send the output of
sudo grep DefaultDesktopCommand /usr/NX/etc/node.cfgWe checked on stock Rocky Linux 9 and didn’t have any issues. That command shows:
DefaultDesktopCommand "/bin/dbus-run-session gnome-session --session=gnome"and works fine.This topic was spun off from another post about audio (on Alma Linux) by the admins. Are you still having problems with getting audio to work?
For some tips on how to set up NoMachine with Pipewire, take a look at the following articles:
How to enable audio on systems relying on PipeWire for sound
https://kb.nomachine.com/AR07T01168How to support audio in NoMachine virtual desktops on Linux host using PipeWire
https://kb.nomachine.com/AR12U01215The logs didn’t include var/log/node logs which is what we would need to be able to see any errors, warnings and reasons for not being able to connect.
Maybe the issue is with it being headless? If you attach a monitor, does anything change? If that is not an option, you could disable the xserver and then
sudo /etc/NX/nxserver --restartand connect again (tips are available here for that: https://kb.nomachine.com/AR03P00973).If that does not help, we need full logs from the server machine you are connecting to. You can gather up by following the instructions here: https://kb.nomachine.com/DT07S00243. Thanks.
Hi, streaming mic from the server side to the client side is not supported. Can I ask what your use-case is?
That post is 3 years old and we released a new mobile version since then that correctly supports window resizing 🙂
Is your actual problem that the window bar is visible on top? This is a common problem on DeX, for example
https://us.community.samsung.com/t5/Suggestions/Dex-mode-full-screen/td-p/2343762One user of that thread said “I did Force Stop Dex for PC and cleared the apps cache. It now works”. Could you try the same?
If, instead, the problem is not the bar showing, what is it? Is the remote desktop not supporting the resolution of the DeX screen geometry? What OS/version is on the remote desktop by the way?
You can use the same checkbox that you use in the server settings to blank the screen when you are connected to that computer. During the NoMachine session just go to the !M icon of the desktop you are connected to and open the Server settings. Enable screen blanking on the fly. Once you’ve finished, you can disable it and then disconnect.
Edit: We thought deeply about what you requested, and it can indeed be a very useful feature, something the user can do “on the fly”, when needed. And so this is the result (see attached).
We’ll be adding it to NoMachine 9. 🙂
Attachments:
We were unable to reproduce this problem of not being advertized on the LAN. Can you send us the logs of the server side? Please follow the instructions here and submit them to forum[at]nomachine[dot]com using the title of this topic as the subject of your email.
https://kb.nomachine.com/DT07S00243
