Forum Replies Created
-
Posts
-
Thanks for your comments and feedback 🙂
The TR you mentioned is something different.
Our app design consists in multiple processes handling the Dock integration and the remote desktop windows presentation, and there are some “minor inconveniences” like determining the previous application activation when NSWorkspace reports a hiding event. We’re investigating for ways to improve this behaviour.
Does this article help you?
How to set up key based authentication with NX protocol
https://kb.nomachine.com/AR02L00785Hi, we got your nxd attachment and the recordings, thank you.
We would also need server- and client-side logs. Please follow the instructions you can find here and send them in the same way as you did your nxd log 🙂 https://kb.nomachine.com/DT07S00243
Could you also tell us if the mouse offset is getting bigger when you move it to the bottom right corner of the screen (with show remote cursor enabled).
Thanks.
“I was using the VM for over a year with out an issue”.
Is there anything you perhaps installed/updated before the problem occurred? Ubuntu updates, new drivers, etc ?
The ~/.xsession-errors log would also be useful.
You didn’t submit the logs that you mentioned.
I would uninstall, remove all traces of NoMachine, and then reinstall the latest packages (now 8.5). If the problem is still there, please provide:
– Linux distribution server side
– desktop environment server side
– client OS and version
and logs from both sides. The instructions for gathering logs are available here: https://kb.nomachine.com/DT07S00243.
Attached find the .nx folders _old is the one I had fore some time, the other one is from today after restarting nxplayer.
There are no logs there. This is because the logs are automatically deleted when you close the session. Since it is not possible to tick the box “Don’t delete the log files on exit” in the Player settings (given that you can’t see the check box 🙂 ), what you should is launch the session and get the logs whilst the session is still running. Thanks!
Hi, this topic is going to be closed.
NoMachine Free Edition does indeed work as both client and server. You can shut down the server on the computer you are connecting from if you wish. Alternatively, we also offer Enterprise Client which does not include the server component at all.
If you’re having problems with file transfer, can you please open a new topic? Thanks 🙂
The key you mention is intended to be used to call an already existing physical display, not a virtual one. That said, with Manjaro try
DefaultDesktopCommand "dbus-run-session /usr/bin/startplasma-x11". The alternative is to turn your physical display off withsudo init 3.Our own xserver has those logs disabled. NoMachine does not load any display module because it works as a virtual frame buffer.
We’re not able to reproduce. Is the misalignment bigger if you click in the bottom right corner of the screen. What about if you click in the top left corner, is the misalignment the same as clicking in the bottom right or is it almost unnoticeable?
Could you send us a recording showing the problem with one of the more common applications you use (e.g Chrome) and also the server side logs?
Please see the instructions here: https://kb.nomachine.com/DT07S00243.
You can submit everything via email to forum[at]nomachine[dot]com, include the title of this topic as the subject of your email. Thanks!
In the current version of NoMachine Terminal Server products, treating multi-monitors on the client as separate monitors in NoMachine sessions is possible with any of the products from the Terminal Server for Linux range. (It is a feature which is not supported in the free version of NoMachine). Doing so lets you maximize the session window, for example, in one monitor only instead of going full-screen across all the client-side monitors available.
To enable it:
– Open the NoMachine menu panel inside the session (ctrl+alt+0 or click on the page peel in the upper right corner of the window)
– Click on ‘Display’
– Click on ‘Resize remote display’ then on ‘Fullscreen on all monitors’For a later version, we are going to implement the possibility to have multi-monitors on the server side which can be managed as separate windows on multi-monitors client side. In each of these separate windows users will be able to apply all the usual settings, like applying a different scaling factor, resizing the window to any size, sending the window to fullscreen and placing the window in any desired location. This will apply to connections to physical desktop and virtual desktops/custom sessions.
What could be happening is that the session is disconnecting and reconnecting (automatic reconnection enabled) without you noticing, and when NoMachine disconnects, the original resolution is restored (this is the correct behaviour). NoMachine does not automatically change the resolution upon reconnection. So, if you’ve enabled “Resize remote” once the session starts, later on the session for whatever reason disconnects, then the original resolution is restored, after which NoMachine reconnects automatically, you’ll find that you have to manually change it again.
Please try:
1. Quit the Player (systray icon, right click, ‘Quit NoMachine player’)
2. Then disable hardware decoding on in the player.cfg -> option key=”Enable hardware accelerated decoding” value=”disabled”.
3. Restart the Player.
4. Try connecting again.“online order version” – do you mean you are using one of the products from the Terminal Server family? Or something else?
The “don’t ask for the acceptance if the user is connected as a system user” option can be activated/disactivated in two ways. Via the NoMachine server settings panel on the server side using the NoMachine UI (Security) or via the server.cfg file.
In the server.cfg look for the ‘PhysicalDesktopAccessNoAcceptance’ key. Uncomment it and add ‘system’ to the options. It should look like this:
#
# Enable, disable or restrict NX Server requesting authorization to
# the owner of the physical desktop to allow a different user to
# connect.
# [snip]
#
PhysicalDesktopAccessNoAcceptance administrator,trusted,owner,system