Forum Replies Created
-
Posts
-
Thank you Matt, we’ll keep an eye out for this problem. If you’ll reproduce it again, don’t hesitate to contact us.
2. mouse and keyboard will work initially for a few minutes. Then when you try to use either input device terminals start closing and then the connection closes
The terminals closure could be caused by this issue:
https://www.nomachine.com/TR06R09781
When you notice input starts working badly, try the workaround described in the Trouble Report. I’d be grateful if you can confirm it.
After the last upgrade I started seeing this same issue. Linux terminals just hang and won’t accept any inputs.
If you’ve the same issue reported by Matt (menu opening, etc), could you answer to questions 2, 3 and 4 of my previous post?
Additionally, do you’ve issues only with terminals or with any application running remotely?Hi. You will find that welcome screen on the server where you want to connect. The Android app, which is a client, doesn’t need to show it.
Hi. I’m not sure I understand everything, so I’ve some questions:
1. What is the client side OS and NoMachine version?
2. Mouse and keyboard are correctly sent to the remote desktop and they don’t work only when you want to open the client menu, or they don’t work at all and you can’t interact with the remote desktop?
3. You’re now using Ctrl + Alt + T to raise the disconnect dialog. How did you close the connection with the desktop when you didn’t have problems with input events?
4. Can you see the small upper right corner peel when you move over it? Only the click is not registered?
Hi Martin. We’ve found a way to reproduce the issue, thank you for reporting it. Please wait while we work on a solution and provide you with a version to test.
Hi. We had a similar report recently, we’re investigating it. Can you confirm whether you’re using a hardware keyboard connected to the tablet?
Hi. What is your device model? Did you try to enable the pointer mode, from the toolbar, to have a more accurate method to move the mouse pointer?
I’m happy you solved it. 🙂 I’ll forward your request to devs, so they can evaluate it.
By the way since the video card is responsible for notifying the number of connected monitors, you could check if there is a setting allowing to report the monitor as connected also when it’s turned off. You could also configure energy saving settings, it’s not like turning the monitor completely off but it’s better than leaving it switched on.
Lastly, if you want to hide what you’re doing while you’re connected to the desktop for privacy reasons, you can enable the display blanking option in server settings.Agreed, here it is:
https://www.nomachine.com/FR06R03993
It has been added to the short term release roadmap, so you can subscribe to the FR to be notified when it’ll be available. 🙂
But I can’t tell if NoMachine is actually using portions of the RDP protocol which would limit it to 1 monitor, or not.
The free version of NoMachine doesn’t support RDP sessions, it’s a feature available in the Linux Terminal Server products.
Are you able to see more than 1 monitor, or are you only using 1 monitor in your setup?
If you can correctly connect to the Windows physical desktop (the same you use at work) and both monitors are detected by the Operating System (they’re not switched off/disconnected), you’ll see all your monitors in the remote desktop session of NoMachine and you don’t need to virtualize your desktop like you’re used to do with RDP.
Hi. Yes, it is currently only a command line option. We could improve the option usage by adding a key in the connection file (NXS). Would that be fine for you?
Hey Ranger, thank you for sending the useful information. There are many differences between NoMachine and Windows Terminal Services, and one of those is for sure the way they deal with displays on the server. When you connect with RDP, Windows Terminal Service creates a desktop with virtual displays that don’t necessarily match the actual monitors connected to the server (usually RDP clients allow to use the default display resolution or set a custom resolution). In your recent screenshot I see your machine lists a single monitor NEC 2560×1440, which is the one shown in NoMachine display settings. In order to see correctly two monitors in NoMachine you need to verify why your PC at work doesn’t show both NEC monitors in display settings.
Hi jason. The path you see in libfontconfig.so is just the default one, but you can change it by setting the variable NX_CONFIG in the environment where you’ll start the player. It is a path representing where the client will store its data, by default
~/.nx. If you also want to move user files/folders created by the NoMachine server services you’ll have to change the keyUserNXDirectoryPathin/usr/NX/etc/node.cfg.