Forum Replies Created
-
Posts
-
Hi, the development roadmap is no longer in the public domain. Indeed they log the evolution and design of our software and are documents that go into extreme detail. There is a public section for Trouble Reports where we publish bug reports, the workarounds available and eventual closure.
Please send us debug logs from the computer you are connecting to. You should enable debug and then reproduce the problem. You can extract them using the instructions here: https://kb.nomachine.com/DT07S00243
Send them to forum[at]nomachine[dot]com. Please use the title of this topic as the subject of your email. Thanks!
Ziomario, the NoMachine app for Android/iOS functions only as a client. You cannot use it as a server. This means that you won’t be able to connect to the Android device with NoMachine.
The IP address you see is a session file from an earlier session. But you won’t be able to use that session file to connect to Android, for the reason I just mentioned. You should delete the session file, editing the port to try to connect to the Android host which cannot accept connections will have no effect.
Instead, regarding the unusual crash, if it continues, please make sure you are using the latest version (which I assume you are but you didn’t mention it) and submit the logs as I mentioned earlier.
Can you send us the logs from:
– your NoMachine Windows client
– the Ubuntu serverFor logs, please enable debug as per the instructions here on the Ubuntu side and gather logs. The link also contains instructions for extracting logs from the Player.
https://kb.nomachine.com/DT07S00243
Also useful would be the nxtrace from the Windows computer. If it’s the player which is crashing for some reason, there will be a nxtrace log in C:/ProgramData/NoMachine/var/log.
Send everything to forum[at]nomachine[dot]com. Please reference this topic in your email. Thanks!
Hi,
I would like to not enter the local “physical desktop”, but rather start a new session with another window manager (LXDE) when I work remotely…..ssh access does not work with the NM client, although is seems to be activated in the NM server config. SSH login is possible from a terminal using my standard rsa key (I would like to do this with NM as well instead of typing my password for each new session).
These are features of the NoMachine Terminal Server family of products. I suggest you take a look at the Workstation and check whether that satisfies your requirements. You can download it as evaluation software from the website here:
https://www.nomachine.com/product&p=NoMachine%20Workstation
https://downloads.nomachine.com/download-enterprise/#NoMachine-WorkstationMore information about how the two products are different is available here:
Differences between NoMachine Free Edition for Linux and NoMachine Workstation for Linux
https://kb.nomachine.com/AR10K00702Hello, we welcome feedback!
“usability can be greatly enhanced by having more options for customizing the appearance and layout.”
What would you like to be able to customize exactly?
“I have experienced occasional performance hiccups when accessing remote sessions over different network conditions”
Can you tell us more about the remote sessions in terms of what was running on the computer you were connecting to? What desktop environment, what applications were you using?
“advanced optimization settings or enhanced network adaptation features”
Can you be more specific about this?
So not KDE, which is what we thought you might have been using.
The first time you uploaded the logs, they failed to attach. If you have a chance to reproduce the problem again on Wayland, please follow the instructions here and send them to forum[at]nomachine[dot]com.
Please update the server side to the latest version 8. If you are not the administrator of that host, please ask them to reach out to us via the support center.
Hi,
I would like to setup a NoMachine server on Android 14 and connect to it from my Linux /Ubuntu 24.04/ Workstation X64 bit.
The NoMachine app for mobile is not a server. You can use the Android app to start connections to a host where you have installed one of the server products, such as the free edition. It will not be possible to reach your Android device from your Ubuntu machine.
What I did to reach the goal has been to press on “search for nomachine PC connected to my LAN” and it discovered a connection made on 192.168.1.6,that’s the IP assigned to Android where I’ve launched the NoMachine application that I’ve installed from the PlayStore.
You mean that on your Android device you then searched for NoMachine hosts and found 192.168.1.6 which is your Ubuntu computer being broadcast on the LAN? If you connect and the port is unavailable, you should see an error dialog telling you. Do you see any error dialogs when you try to connect?
The problem is that I’m not able to connect to 192.168.1.6,nor on 4000 neither 8100.
Please make a test. Change the port back to the default 4000 port on your Ubuntu host (please leave all settings as default ones, if necessary reinstall) Go to your Android device and connect to it using the local IP address of the NoMachine Ubuntu PC. Can you connect?
In addition,when on Linux I give the command “dnesg”,I see this error between the messages :
[ 525.935592] nxplayer.bin[14168]: segfault at 10 ip 00007ff7d229ffe4 sp 00007ffd3a9125e8 error 4 in libc.so.6[7ff7d2228000+188000] likely on CPU 7 (core 7, socket 0)To investigate a crash we will need both logs and backtrace of the Ubuntu machine.
How to gather debug logs
https://kb.nomachine.com/DT07S00243How to debug a core file on Linux
https://kb.nomachine.com/AR09L00810Send everything to forum[at]nomachine[dot]com making sure to include a reference to the topic. Thanks.
Can you send us the logs from the Windows 11 machine? Zip up the entire .nx folder and submit to forum[at]nomachine[dot]com. Include the link to your topic. Thanks!
This is a known issue and you should disable Wayland and use X.Org instead. See the following topics:
The Trouble Report currently open is: https://kb.nomachine.com/TR05V11141
We don’t know either. We tested MX Linux (having applied all the updates) and left the session running for most of the day and no slowing down was observed. If it comes back, next time, grab the logs.
Hi, can you try disabling hardware decoding on your Windows client computer? Follow the instructions here to do that (in your case you must disable completely, in point 3, by setting the option key as:
<option key="Enable hardware accelerated decoding" value="disabled" />How to disable hardware decoding on the client side
https://kb.nomachine.com/AR07U01202The distro and the DE would be useful for us to help us with our investigation. To find the desktop environments installed on your system 🙂
1) Execute this command in a terminal:
ls /usr/share/xsessions