Forum Replies Created
-
Posts
-
Can you submit your image as an attachment please (it’s not possible to paste images in to the field for text). Thank you.
First you need to enable VirtualGL which is required so that you can view OpenGL accelerated applications. There is an article in our knowledge base with instructions and tips on how to set up your NoMachine server to use VirtualGL.
https://kb.nomachine.com/AR05P00982
It’s a good idea to update to the latest version if possible as well.
Hi, version 9 has the priority right now which includes the new Network feature so resources are taken up with that. It’s likely that it can be added for inclusion in a minor of version 9. We’ve already got a number of features requests lined up for releases after the initial 9 and yours is one of them 😉
You have us head scratching 😀
Are you using Control+Command+Q to activate lock screen (we see in the first recording, with NoMachine, that the Q button is being held down)?
If you press the Q button, as if you were trying to release it, does that change anything?
Hi, bear in mind that Arch is not among our officially supported distros, so NoMachine is not finding the display running there, and it won’t know how to interpret that key. This is the new Trouble Report and it has been queued for deeper investigation. Please use the link to track it, https://www.nomachine.com/TR03V11110.
A recording would be useful. You can even do it using NoMachine’s built-in screen recorder. You can open it from the !M system try icon on the Mac. It stays on top whilst you record. On the server activate the Accessibility Keyboard by pressing the Cmd + Option + F5 keys to open Accessibility Shortcuts. Enable Accessibility Keyboard from the list, and the keyboard will open. This will help us to see what keys are being pressed when you log in. Go to your Windows computer or whichever client-side OS you want to reproduce the problem and log in. Stop the recording on the macOS. Send us the nxr file which you generated.
Hello,
so you are connecting from Windows local side to a macOS?
I suggest you update to NoMachine 8 to start with. What macOS version is on the NoMachine server, the OS you are connecting to? This would be useful to know. It could be a permissions issue in macOS. See the following article for the steps to take: https://kb.nomachine.com/AR11Q01061. If NoMachine has already been added, please remove it and add again.
Hi, the server-side logs were clean. And the logs from the client-side were actually logs from the server component of the Windows machine you are connecting from.
Are you able to try connecting from a different device? Does the same behaviour occur?
To get logs from the client side of the session, see “Fourth Step: Collect Client Side Logs” of the document I posted last time.
The following instructions have to be done to the user’s device.
Inside the NoMachine session, open the menu panel by ctrl+alt+0 or click on the page peel at the top right corner of the window. Open ‘Connection’ and click on ‘Take the logs’ button on the left and choose where to save logs. A copy of the session directory is created to store logs and named as session name plus date. Compress it to create the log archive to be sent to Support Team.
On Windows the .nx folder is hidden. To find it, write the following in the address bar or the file browser:
%USERPROFILE%\.nx
Or you ca navigate through the computer folder till the user’s home and digit .nx in the navigation toolbar to reach it. Its path can be similar to: C:/Users/nomachine/.nx
The bug report can be tracked here: https://kb.nomachine.com/TR02V11091
Absolutely. It is something that we’ve been wanting to do for a long time and is the current development roadmap.
Hi xoepe,
confirm what distro and desktop environment you are using. Does using X.Org solve the problem?
Send us the logs from the affected OS. We can then check against known issues with Wayland. You can extract them using the instructions here: https://kb.nomachine.com/DT07S00243
Send them to forum[at]nomachine[dot]com. Please use the title of this topic as the subject of your email. Thanks!
Did you already try rebooting the Win10 again?
After checking that, send us the logs of the Win 10 host. You can extract them using the instructions here: https://kb.nomachine.com/DT07S00243
Send them to forum[at]nomachine[dot]com. Please use the title of this topic as the subject of your email. Thanks!