Tor

[Tor]

Hi reesd.
Your remark is correct, even if the OS grabs the keystroke for its purposes we should be able to forward the Period key to remote desktop. There are some system shortcuts impossible to intercept, but Command-Period should not be among those because it generates a specific event delivered to the application. In order to track the issue we’ve opened this Trouble Report, you may sign up to be informed when we’ll release a fix:

The Command-Period shortcut is not correctly sent to the remote desktop
https://www.nomachine.com/TR01O07531

[Tor]

Hi efkan.
Thanks for your report. We correctly support the Indicator API (used on Freya with Ayatana, and on Loki through a plugin for Wingpanel), but we’ve verified the issue on Elementary and already implemented a fix. We’ll include it in the next release.
If you want to be informed when we’ll release it, you can subscribe to the following trouble report:

https://www.nomachine.com/TR01O07501

[Tor]

The list of resolutions looks to be correct. Did I understand correctly that your remote desktop now resizes to the correct resolution, so the xrandr configuration somehow got fixed? 🙂

[Tor]

Hi rdauria, thanks for your report.
The problem is documented here (slightly different condition, but same issue):

https://www.nomachine.com/TR08N07113

A fix will be released in the next software update, you may subscribe to the trouble report to be automatically notified.

[Tor]

Hi Brian.
Did you see that message in our Play Store page? If it is so, you’re not being allowed to download the app because it currently needs at least a 7″ display. We’re working on a version optimized for smaller displays, it was delayed but it is still one of our top priorities. You may subscribe this Feature Request to be contacted when we’ll release it:

Offering a NoMachine client for Android smartphones
https://www.nomachine.com/FR09L02828

In the meanwhile you may wish to install the APK of our tablet version, you can get it from the download area of our website. On a display bigger than 5″ (like the one of the Nexus 6P) it is not perfect but still usable.

[Tor]

Hi Vanderemit. We’re very close to the release of the phone optimized application. The usability on small screens is very critical, so we’re evaluating all details thoroughly to be sure to give the best experience. Be patient just a bit more and I’m sure you won’t regret it. 🙂

[Tor]

Hi Florian.
Can you help us to identify the issue by answering to these questions?

• What is the NoMachine version installed on client and server?
• What is the OS of the server?
• Where do you reproduce the issue, on the client or on the server?
• All monitors turn on and off, also the one of the notebook?
• When the problem occurs exactly, always or only when you connect with NoMachine?

It would be great if you could retrieve logs on the computer where the issue occurs. You should follow this article, point 3 of section 3:
https://www.nomachine.com/DT07M00098#3
Send the archive to forums[at]nomachine[dot]com.

[Tor]

Hi.
Resolutions supported on your server are not related to those available on your client: even if your monitor has a resolution of 1600×900, the remote desktop may not support it. Can you send the list of available resolutions on the server by running the command ‘xrandr -q’ in a terminal, on Linux?

[Tor]

Hi. The list of available resolutions on the new server appears to have mixed or invalid refresh rates. Is the guest OS correctly configured (guest additions, VMWare tools, etc)?

[Tor]

Hi.
The behaviour you’re describing looks correct if the client is not configured to resize the remote desktop, it keeps the original geometry and snaps the window to that size. If instead you’ve enabled the “Resize remote screen” option in the Display menu, then the remote desktop may not support the resolution you’re trying to set or the desktop environment is forcing its own resolution.

This behavioural change may be due not only to different NoMachine versions, but also to different desktop environments used on those servers.

Are those servers running in virtual machines? Can you please send the output of the command ‘xrandr -q’ executed in a terminal on both servers?

[Tor]

Hi again. We’ve slightly changed the keyboard grabbing option, so that now it can work around your issue also when the NoMachine client is windowed. Would that be a good solution for you? If you would like to test it, please contact us at forum[at]nomachine[dot]com.

[Tor]

This is an accessibility feature and as such, we would like to support it. The problem is that it is implemented in a way that makes difficult for an application to continue to handle correctly keyboard events. There are many other apps with the same problem, and we guess this may be one of the reasons why the feature is not available on some recent desktop managers.
The keyboard grabbing option, configurable in the Input menu, can work around this problem when the NoMachine client runs fullscreen even if it doesn’t allow the cursor to highlight. Unluckily it doesn’t help in window mode.

[Tor]

Hi. The option ‘Show remote cursor pointer’ is not currently compatible with the BT mouse, this is the reason why it is disabled. The next NoMachine version (we’re currently using it internally) will change in this way: the cursor will be always visible and will have an option to hide it; the ‘pointer mode’ will need the remote cursor pointer to be visible, and can be enabled even if there is an hardware mouse attached, by handling differently mouse and touch events. I’m sure this will solve your problem.
With the current version you can see the remote cursor when pressing the mouse button. Even if this is far from being ideal, it can be helpful to confirm the operation you’re doing.

[Tor]

Hi. We’ve checked your logs and used them to emulate the same environment without reproducing an issue like that. Even if the problem is on the server we’ll need more information, but since they may be sensitive we’ll contact you by e-mail.

By the way, in your logs it shows you’re connecting to a fully licensed server. Remember that you’re entitled to support via your customer area. Perhaps you should get your administrator to open a support ticket. This would also avoid sensitive information being published on the forum.

[Tor]

Hi.

In our next release we’ll include the official support for Chromebook. Problems we’ve found so far are these:

https://www.nomachine.com/TR09N07231
https://www.nomachine.com/TR07N07085

We’re also evaluating some small changes to improve the experience on these devices.

– Buttons get cut off from the bottom of the window. Luckily, toggling the window to full-screen reveals them.

This is one of the problems reported above. As you said, you can work around it by toggling on and off the fullscreen mode.

– Some gestures are already used by the OS, so four-finger swipe doesn’t quite work.

We’ll change the four fingers swipe to four fingers tap, like we did on iOS some versions ago.

– The window isn’t resizable.

– Relatedly, an aspect-ratio preserving display mode would be helpful.

Currently Android doesn’t allow to freely resize the window. This will change with Android N but as of now, we can’t do much. We’ll see how the Chromebook support to Android apps will evolve.

– It would be great if there were a mode that understood the presence of a hardware keyboard and also a hardware pointing device, allowing for actual right-mouse-button use.

You can expect to easily work with mouse and keyboard on Chromebook in our next release, it’s one of the main improvements we’re introducing.
Thank you for sharing your experience and for your proposals!

[Author]

Posts