Forum Replies Created
-
Posts
-
Would both of you be willing to submit logs after having encountered the white screen issue? To do that, you’d need to enable debug, reproduce the problem and then submit them directly to forum[at]nomachine.com. That way we can investigate. Please follow these instructions. Thanks very much.
There was a mistake in the formatting of the command. Apologies. Try this and let us know if it helps:
DefaultDesktopCommand "/etc/gdm/Xsession 'env DBUS_SESSION_BUS_ADDRESS=unix:path=/run/user/$(id -u)/bus gnome-session'"The only other option is to wait for the fix.
Please provide the following:
– NoMachine product and version on local and remote machine (free version, Workstation, etc).
– Whether the problem arises connecting to a physical or a virtual display.
– Remote and local Windows/Mac/Linux version (Windows XP/7/8, OS X 10.x, Ubuntu xyz, Mint x.y, etc.).
– If on Linux, desktop version (GNOME. KDE, whatever) on client and on server.
and additionally what’s the source of the video (i.e which application)?
This is a known issue and we are currently working on a fix:
Cannot run NoMachine sessions on ARMv7 devices with kernel 5.4.42 or later
https://www.nomachine.com/TR06R09747Please sign up to receive a notification of the fix.
Can you update to the latest version we released earlier this week? NoMachine 6.11.2. The following TR was fixed in that release which is probably what you were encountering.
Audio is not working when NoMachine v. 6.10.12 is installed on macOS Catalina
https://www.nomachine.com/TR05R09720It depends what package you have installed on your Raspberry. Try the appropriate uninstall command from the Installation and Configuration Guide (Linux section).
Mick, we will send it to the email address associated with your forum account. Can you confirm what version you are using? 6.10 or 6.11?
Both https://www.nomachine.com/TR05R09712 and https://www.nomachine.com/TR12Q09486 are being worked on, but I cannot say whether they’ll both be released in production before September.
If you haven’t already done so, I’d update to the latest 6.11. There is a fix for this problem which was affecting Windows clients
Green screen when connecting by NoMachine client for Windows v. 6.10.12 to high resolution monitors
https://www.nomachine.com/TR05R09689Then let us know if you’re still having problems.
If you are using Enterprise Terminal Server with Terminal Server Nodes, you should contact support if you are a customer. They will be able to advise appropriately and take a proper look at your configuration, something which is outside the scope of these forums.
If you haven’t already done so, please also look at the load-balancing configuration suggestions in the ETS guide:
https://www.nomachine.com/DT06O00142#3.3.Maybe send us a screenshot of what you are seeing? You can also define a different shortcut in the NoMachine client User Interface via the Player preferences -> Input -> Change shortcuts interface.
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