Tor

[Tor]

Tap the wheel icon in the right side toolbar, tap Display, tap “Fit to window” to uncheck it. Session will run in 1:1 mode and it can’t be adjusted with gestures.

[Tor]

Hi Bryce, we’ll add you to the list of testers. Since we’re working on a version 6.9 we’ve still some things to check, but we’re also evaluating to just update a 6.1 to distribute it for testing in a shorter time. I hope we can contact you all within a couple of weeks.

[Tor]

Hi. We’re working on improving the mouse support on iPadOS, we’ll be sure to check wheel usage too. Thank you for the feedback!

[Tor]

Having the same issue on Pixel Slate, is it possible to be provided the APK to test as well?

@MrWoo no problem, we’ve added you to the list of testers. We’re solving some important store requirements before publishing the beta version, we’ll contact you as soon as it will be ready.

I’ve heard that it is slower and that the Android version is the preferred route (is that correct NoMachine?)

@Brian where did you hear that?! 😀 Unless who said it had some very specific issues (which we would be more than happy to investigate), you can expect the same level of performance on all platforms we support. Of course there are a lot of parameters that can affect the experience and sometimes tuning the configuration could be required.

[Tor]

So at this point, I’m out of ideas for kicking off a shadow session.

We’re sorry, we ran out of coffee… The correct keystroke to force connecting through a shadow session on macOS client is Command + Alt + Double click, while on Linux and Windows it is Control + Alt + Double click. We could not use the Control on macOS because it would emit a right click.

[Tor]

Hi. In version 13 you could enable the AssistiveTouch to use the mouse with NoMachine on iPad. Now that the mouse has received a better integration in 13.4, we’ll soon explore the possibilities we have to know how to improve the app.
If you’ve any feedbacks, please share them with us!

[Tor]

That feature is one of those on top of our priorities, we can’t give an exact date yet, but we’ll do our best to include it in one of our next releases.

[Tor]

Hi. You can select the remote monitor to show in the client window, try the shortcuts Control + Alt + A to show them all, or Control + Alt + <monitor number> (and Control + Alt + I to know their numbers) to select a single monitor. You can then enable the fullscreen (or multi-window fullscreen) to match client and server monitors. However if your monitors layout and geometry on the client are different from those on the server, the result could not be the one you expect. In order to make that easier, this feature request when implemented will be helpful:

https://www.nomachine.com/FR10N03220

[Tor]

Is there any way to prevent a non-full screen window (and/or non-focused window) from scrolling as the mouse travels above it?

You could try to edit the file %USERPROFILE%\.nx\config\player.cfg and reduce the value of the setting “Automatic viewport scrolling sensitive area size”. If you set it to 0, the automatic scrolling will be disabled.
We’ll start an analysis of your report to evaluate whether we need to completely prevent the automatic scrolling for an inactive window, or offer a new configuration key.

But if I was to get a dual display setup at home instead of just using my laptop would the NoMachine client be able to mimic the two displays by having display #1 of work PC on display #1 of home PC and display #2 of work PC on display #2 of home PC?

If your client and server monitors layout and size will be the same, you will just need to toggle the fullscreen mode to have a perfect remote desktop match. If instead you will have different sizes or layout, the following feature request will give more freedom by allowing to place windows where you prefer:

https://www.nomachine.com/FR10N03220

[Tor]

Hi Brian, thank you for the report. The problem is not related to the frontend, but to the OS app sandbox getting stuck while the app is connecting to the remote desktop. We had to work on our build details and shipped architectures to solve it, but this change required many more aspects to be tuned, improved or changed completely, so it is taking more time than expected. I see you’d like to install a testing APK in developer mode, so we’ll contact you soon. 🙂

[Tor]

Hi Tim! We’ve found what is causing your issue and we’re working on a solution. You can track the report here and subscribe it to be alerted when we’ll release the fix (most likely in the next maintainance):

https://www.nomachine.com/TR03R09565

Your workaround is currently the only way to restore the file transfer. Thank you very much for your help.

An additional note. I’ve noticed that the size of your logs is caused by the server running in debug mode. You can execute the following commands to clean them up and save some disk space:

1. sudo /usr/NX/bin/nxserver --debug --disable all
2. sudo /usr/NX/bin/nxserver --logrotate
3. Delete files in the directory reported by the output of the command above

[Tor]

Hey there. We’re working on a version to fix this problem. If you enable the developer mode we could also send you an APK version including the fix, otherwise subscribe to this report to be alerted when we’ll release it:

https://www.nomachine.com/TR10Q09450

[Tor]

If you’ve never enabled server debug logs (for an old troubleshooting request, for example), the big size could depend from multiple factors. Let’s go through this procedure so you’ll both clean up the space and retrieve all logs for the debugging.

1. Enter the directory /usr/NX/var/log/node
2. Remove old debug logs with the command sudo rm -rf F-*
3. Go back to the directory /usr/NX/var/log
4. Store old server logs by running the command sudo /usr/NX/bin/nxserver --logrotate. You can delete the rotated logs reported in the output if you don’t need them for other reasons.
5. Reproduce the issue with file transfer, and while the client is still connected to the desktop, run the command sudo /usr/NX/bin/nxserver --debug --collect. Verify if the resulting archive is smaller than the previous one.
6. Execute the command tar czvf NoMachine-user.tar.gz $HOME/.nx/M-* to store user’s server side logs.
7. Open the file browsing on Windows, enter %USERPROFILE%\.nx in the address bar, in the opening folder right click the latest directory with prefix “R-“, select “Send to” then select item “Compressed (zipped) folder”.
8. Send all created archives to forum[at]nomachine[dot]com

[Tor]

Do you’ve Swype version 1.8? In such a case, by tap&holding the “?123” key you should see a popup where you can select the floating mode. I agree about sticking with a keyboard if you’re comfortable with it, so I hope I won’t be the reason for you to stop using it! 😛

I find tapping the buttons quite unreliable for some reason

Thank you for this feedback. What is your device model? I’ll ask our team to verify the extended keyboard usability on the same or similar model.

[Tor]

a bit more flexibility on how far one can scroll the screen around would be nice

Sure, scrolling will still be possible, the guessing is only needed for the initial position.
You can subscribe to the feature request, so we’ll notify you as soon as we’ll make it available:
https://www.nomachine.com/FR12P03758

Just out of curiosity, what is the keyboard you’re using? I’d be happy to verify if it has a floating mode hidden somewhere! 🙂

[Author]

Posts