Forum Replies Created
-
Posts
-
Thank you @mkirkove.
Can you also check if pressing those keys inside the session releases them? And if after that the clipboard starts working?
Hi mato,
Can you let us know the following:
– what is the Mac version on the server-side?
– does sending keyboard events with on-screen keyboard makes any difference (clicking mouse on that keyboard to produce~)?
– is the same keyboard layout used on client and server, US/US or UK/UK?
Thanks!wget command:
wget https://www.nomachine.com/free/linux/64/deb -O nomachine_7.7.4_1_amd64.deb 😉Hi rsperson,
It looks like you’re using NoMachine version 5.3.2. Can you please upgrade to the latest version and let us know if the issue still occurs? Thanks 🙂
Hi 🙂
It looks like you had previously installed a Workstation and now you’re trying to install NoMachine free version.
If this is the case, nomachine-workstation_7.7.4_1_amd64.deb is the package you need to install (https://www.nomachine.com/download/download&id=26).Hi javve,
This problem does not seem to be caused by NoMachine. Maybe some application running in the background steals the focus from the terminal window.
Did you have the chance to try gnome directly on raspberry pi? If so, did it shows the same problem?
We received your logs @jurgen. Thank you! They will be queued for investigation and we will provide some feedback soon.
Hi icecream102,
Can you tell us the following:
1. Is the flickering visible in the NoMachine session, in the Hyper-V manager, or both?2. What desktop environment is it running in the virtual machine (Gnome Shell?) ?
3. What is the output when you run the command
xrandrin the virtual machine?Thanks!
Hi nessus42,
Rootless sessions are only available with NoMachine Terminal Server family products (https://www.nomachine.com/terminal-server).
To use the NoMachine free version, a desktop environment must be installed.
Hi nxmac,
You can take a look at the article below:
How to solve blank/upside down screen on macOS after the update to Big Sur
https://knowledgebase.nomachine.com/AR09S01139I am afraid we can’t help because it doesn’t look like this is related to NoMachine. Nothing was changed that could affect this.
Hi rsperson,
So that we can queue up for investigation, can you please send us server-side logs?
Please enable debug by executing
sudo /etc/NX/nxserver --debug --enable all.
Then reproduce the problem and collect logssudo /etc/NX/nxserver --debug --collectAfter collecting the logs you can disable by running
sudo /etc/NX/nxserver --debug --disable allPlease send the logs directly to forum[at]nomachine[dot]com adding the title of the topic to the email subject. Thanks!
Hi Mark,
So that we can queue up for investigation, can you please send us server-side logs?
Please enable debug by executing
sudo /etc/NX/nxserver --debug --enable all.
Then reproduce the problem and collect logssudo /etc/NX/nxserver --debug --collectAfter collecting the logs you can disable by running
sudo /etc/NX/nxserver --debug --disable allPlease send the logs directly to forum[at]nomachine[dot]com adding the title of the topic to the email subject. Thanks!
Hi @jurgen,
Normally it should work, even if PAM is missing.
So that we can queue up for investigation, can you send us server-side logs? You can follow the instructions in this article: https://knowledgebase.nomachine.com/DT11R00181Please send the logs directly to forum[at]nomachine[dot]com adding the title of the topic to the email subject. Thanks!