Forum Replies Created
-
Posts
-
Hi. Sorry for the late answer. We’re doing some tests in our lab with that keyboard model, as the problem is strictly related to it. We’ll keep you informed.
Interesting, pointer mode would explain the cursor centered in the screen, but since it’s not enabled I’ve no idea why it is there.
The application is not really doing anything with the trackpad, it’s ChromeOS converting the gestures you do to well known input events like scrolling. We’ll run some tests in our environment, do you mind sharing your ChromeOS version and Chromebook model? How did you install the NoMachine application, store or sideloading?You probably enabled the pointer mode, try to turn it off and check it again. The pointer mode is useful mostly for the touch interface. You can turn it off with the icon in the side toolbar, or in the Input menu.
That TmUmEvt64.dll crashing is related to Trend Micro (AMSP UMH module), but the stack you pasted is about nxserver binary, so from the info you supplied I can’t confirm Trend Micro is also having problems with the NoMachine client.
Do you have a way to add a temporary exception for nxplayer.bin and nxplayer.exe, or a way to check a log of Trend Micro to look for messages related to NoMachine binaries?Can you check if you’ve a file called nxtrace.log in %PROGRAMDATA%\NoMachine\var\log and send it to forum[at]nomachine[dot]com?
If this file doesn’t exist, after you try to start the Player check if there is a NoMachine Player process running in your task manager.The feature is still there and working correctly, so we should just understand why it is not working for you. By the way your preference is perfectly legit! I keep the value set to 10 for a similar reason.
First of all we’ve to verify if the problem is caused by some unexpected values in the CFG and NXS files.
The NXS can be reset to default values by creating a new connection to your server. Don’t worry about your other custom settings, you can set them later.
The CFG can be reset with the “Restore default player settings” link in the settings window. Once you do that, close the player from the tray menu, and edit the CFG like I said in my previous answer.If also this solution doesn’t work, try to set a value slightly bigger than 0, for example a number between 1 and 5, and confirm that the automatic scroll starts when you’re very close to the window edges. This test could be helpful to verify whether the problem is in the setting value reading, or in the logic of the automatic scrolling.
Close all your client instances on Windows and change the following key in
%USERPROFILE%\.nx\config\player.cfgby setting its value to “0”:<option key=”Automatic viewport scrolling sensitive area size” value=”0″ />
The viewport scrolling is configured only on the CFG file and only on the client, any other changes you did can be reverted/ignored.
The ALT + TAB is a system shortcut and can’t be grabbed, but that kind of key combinations are supposed to be sent to the application when it is fullscreen. Can you confirm if you tried the shortcut when the NoMachine app is in fullscreen mode? If it doesn’t work even in that case, can you share your ChromeOS version?
Hi, sorry for the late answer. How many displays are connected to the client and to the server machines? Are you connecting to the physical desktop of a Linux server? What is your display mode, scaling, viewport or resize?
As for your second question, the client doesn’t normally close the window with the list of connections while other client windows are running, so I’m not sure about what you’re seeing on Windows.
The NoMachine Android application that you’re running on ChromeOS doesn’t support starting concurrent connections, therefore you can make use of the Linux VM and install the NoMachine client for Linux.
The Linux VM is disabled by default on Chromebooks, but it is fairly easy to enable it from Settings > Advanced > Developers > Linux development environment. Look for a guide if you get stuck somewhere.
Once the Linux VM is ready, open a Terminal and install a NoMachine Enterprise Client for Linux.We’ve confirmed that some Wacom driver versions just hang waiting for something when the device input gets enabled on window activation. We didn’t find a code workaround for this unexpected behaviour, so the only possible solution so far consisted in stopping the ISD service, but of course this is not advisable if the tablet/pen must be used.
Can you all please check if there is an updated Wacom driver?https://www.wacom.com/en-us/support/product-support/drivers#latest
Hi, thanks for the report. I’ve some questions to help the investigation.
- What is your Mac model? If it’s a Macbook, do you use the built-in trackpad or an external mouse/trackpad?
- Do you’ve multiple screens on client and/or on server?
- What is the server side operating system?
- When you say “one correct mouse click”, do you mean exactly and only one click?
- What is the NoMachine display mode you use: viewport, scaling, or remote resize?
- Can you verify if the mouse works again correctly by just opening and closing the NoMachine player menu?
- Can you verify if the mouse works again correctly by doing a small NoMachine player window resize?
- Can you estimate more or less how big the mouse offset is, and if it is always the same? Does the offset increase as you move to the bottom-right corner of the NoMachine player window?
Thank you for your help.
I’d like to send you a library that adds some checks in the routines handling the system clipboard, but I’d need to know if you use the 32 or 64 bits version of the software (x86 or x64). Please send an e-mail to forum[at]nomachine[dot]com and use the title of this post as subject, we’ll answer by sending a link to download the library.
Hi. We’ve no open issues about copy&paste causing application freezes, so I’m going to ask you some questions to better outline the problem and confirm it.
When you have this application freeze issue:
– Do you have more than one Player running, connected to multiple desktops?
– Is the main Player window, showing the list of machines, freezing as well?
– Open Task Manager and kill one NoMachine Player process at a time. Do the other Player’s start working correctly?
– When you can manage to start a new NoMachine Player, if you shutdown temporarily the NoMachine server do you see other processes running in Task Manager? How are they called? If you kill them, can you start correctly a new NoMachine Player?Also, please send the file %ALLUSERSPROFILE%\NoMachine\var\log\nxtrace.log, if it does exist, to forum[at]nomachine[dot]com.
Thanks.Happy to know it works!
If you want to automatically run the application, you can look for an automation app in the store and configure a macro to open an NXS file with NoMachine. You can select the trigger (device boot, screen unlock, wifi state change, button presses, etc) and the action to execute (in our case “open file”).
I’ve tried a couple of simple apps but I didn’t manage to start the application correctly after the device boots up. However I tried to run it when the screen unlocks, and it worked beautifully. Nice idea, thanks for sharing it!