Forum Replies Created
-
Posts
-
Could you please clarify if the screenshot of the display settings was taken while NoMachine was connected to the desktop? I see you often talk about RDP, but I didn’t understand if you do it as a comparison or to outline that you’re connecting to the desktop while an RDP connection is active. Thank you.
The software update message is misleading. The remote desktop is running on a headless Linux server (where there is not an X server running), and the update process detects it as a virtual desktop. By the way in this specific configuration the software update program can’t complete its task, so you’ll have to download the newest NoMachine package from the website and install it to upgrade your version. We’ll improve it to support also headless servers.
Hi. We’re not currently aware of issues with detecting monitors connected to the remote desktop, you should be able to use both monitors at full resolution.
Can you please open the menu (Ctrl + Alt + 0) and verify if you see the “Change monitor” button in the Display menu? Could you send a screenshot of the Display settings panel, so we’ll know the parameters that are being detected? Thanks.Hi. On mobile app you don’t need to use the menu: open the OnScreen keyboard (or press the toolbar icon if you’ve a physical keyboard) and use the extended bar to press Control, Alt and Delete. It’ll trigger the Secure Attention Sequence on the server to unlock the screen.
Thanks. This looks to be an old problem popped out again after some OS changes. Please try this: enter Settings > General > Keyboard and turn off Smart Punctuation. Let me know if this fixes it.
Thank you for the additional information. Can you please confirm your keyboard language on iPad and your layout on macOS?
The default keys combination is Ctrl + Alt + End so it doesn’t interfere with the Ctrl + Alt + Del shortcut, and as you have noticed the same hotkey can be sent from the ‘special sequences’ menu. If both solutions didn’t help you we need to verify what is happening on the Windows server.
Please verify that your group policy allows services to simulate a Secure Attention Sequence (SAS). To do so, verify the policy in Computer Configuration, Administrative Templates, Windows Components, Windows Logon Options. The entry “Disable or enable software Secure Attention Sequence” must be Enabled, and the software allowed to generate the Secure Attention Sequence must be set to “Services”.
If this is not helping, please follow the instructions at https://www.nomachine.com/DT10O00162 and send gathered logs to forum[at]nomachine[dot]com.NoMachine maps virtual keyboard symbols to symbols available in the remote keyboard layout. Some symbols like the opening or closing quotation marks are typographical and not available in the layout, so the app can’t tell the server what is the correct way to type them.
In the extended symbols you see when tapping and holding the apostrophe key, the second and the fourth symbols (attached image) will be correctly sent to the server.We’re dying for some features for iPad os such as scroll, switch desktop (by three fingers swiping on Mac), etc.
Do you mean scrolling with mouse and trackpad? As for the gestures, we’ll carefully evaluate what we can do without interfering with app gestures.
Attachments:
Hi. You could do something similar by installing
xdotooland by executing a script like this:#!/bin/bash ids=$(xdotool search --class "nxplayer.bin") for id in $ids; do name=$(xdotool getwindowname $id) if [[ $name == "NoMachine -"* ]]; then newname=${name##NoMachine -} xdotool set_window --name "$newname" $id fi doneHi. There seem to be an issue with the GPU acceleration in the Linux container. You can try this to work around it, by hoping next Chrome OS version will include a fix (this was not happening in Chrome OS 76, for example):
1. Open Chrome
2. In the address bar typechrome://flags/#crostini-gpu-support
3. In the opening page change the combo from “Default” to “Disabled”
4. Reboot by clicking “Restart now”As for supporting Chromebox, the reason why you see the app as not compatible should be due to the requirement of a touch interface on the device. This requirement should no longer be needed because the NoMachine app works equally well with touch and mouse input, so we’ll remove it and verify if it is enough.
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.
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.
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!
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.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 isControl + Alt + Double click. We could not use the Control on macOS because it would emit a right click.
