Forum Replies Created
-
Posts
-
The symbol lookup error is a kernel-related issue. Reverting to an earlier kernel version is suggested for the time-being. We have opened a Trouble Report https://www.nomachine.com/TR06R09747 (please sign up to receive notification).
Hi,
When the user is logged the screen become blank but we still see the mouse pointer that is moving in a blank monitor. This is the normal or also the mouse pointer should disappear?
On Linux this is normal behaviour. On some Linux distributions, gamma adjustments applied to blank the screen do not affect the cursor which remains visible. The local user, however, cannot control it with the physical mouse.
Another user has problem after disconnecting from NoMachine (it is mainly used for telework). When is back to the office and try to get access to the Physical Machine locally, He is able to enter the password in his ubuntu 18.04 but after that, both monitors(he has 2 screens) become “blank” as he was connected remotely and we need to reboot his computer. There is a way to prevent that?
Is it possible that he didn’t disconnect properly? We weren’t able to reproduce this on-the-fly, but we’ll check again if you tell us the display manager you are using. Does the user physically see the login window or lock screen? How many monitors are there?
It’s not clear what you want to achieve?
Do you want to stop user B from trying to connect?
If user A is already connected and they are the owner, they will see “Waiting for the desktop user to authorize your connection.” They can refuse user B.
See the following article:
How to authorize connections to remote desktop automatically or only upon owner’s authorization with NoMachine https://www.nomachine.com/AR04K00663
Send any attachments as before making sure you put the new topic title as the subject.
Please write here the details of your environment for the developer’s convenience and anyone else reading the thread.
Hi, we’ve sent you a link to a download package and instructions. Check your inbox for emails from us.
Hi, can you check your email inbox because I sent a link yesterday with instructions. I’ll send it again.
Please tell us:
– version of NoMachine on client side
– version of NoMachine on server side
– OS version of Mac
– OS version of Ubuntu
Also, logs didn’t attach possibly because they were too big. So send them directly to forum[at]nomachine[dot]com. Use the title of this topic as your subject.
Hi, can you send us the logs from the server-side computer? Please follow the instructions here: https://www.nomachine.com/DT10O00163#1
You can send them directly to forum[at]nomachine[dot]com making sure you use the title of this topic as the subject of your email. Thanks!
Zenith, it’s not clear whether you mean there are glitches and artifacts when connecting with NoMachine. Since this can be considered a new topic which is unrelated to the authentication issue you previously had, please record here the details of your set up.
We received the logs. We need you to test whether Apple Audio Core is working properly.
You can do this by trying to record audio by using another application, for example QuickTime Player:
1. Connect to this mac via NoMachine.
2. Play some audio (music for example).
3. Run “QuickTime Player” and choose File -> New Audio Recording.
4. In the recorder, click the Options pop-up menu and select “NoMachine Audio Adapter”.
5. Now you should see volume slider moving around (while playing some audio).
6. Try to record audio for a few seconds, save it as a file and then play it on a different machine.
Let us know result of this test. Are you able to here audio of the recorded file?
Please check you are using the following
--debugand not-debug. So$ sudo /etc/NX/nxserver --debug --collect