Britgirl

[Britgirl]

You say that you think the problem is on the client side, so with the Mac computer. Have you tried connecting from a different computer and/or with a different OS? This is the easiest way to know if the problem is being triggered on the client side.

You can also look in the crashes list on your Mac. In a terminal run:
ls -ltr ~/Library/Logs/DiagnosticReports/

If something is happening in nxplayer, it will be reported there.

Another thing to consider is that you need xquartz installed on the Mac in order to be able to run custom sessions/rootless sessions. Are you trying to run a “custom virtual desktop session”? See here for a quick reference:

How to run a single Linux application with NoMachine client on macOS
https://knowledgebase.nomachine.com/AR07K00675

but you can search “xquartz” in these forums as well. What happens if you try to start a new virtual desktop (full desktop, not custom)?

Failing those suggestions,  then we need to look also on the server side.

What’s the Linux distribution and its version where you have installed the NoMachine server?

What NoMachine product is installed on the Linux host?

You say “open the virtual desktop”, is this a virtual desktop which you are reconnecting to? What desktop environment (DE) is it? Gnome, KDE, something else? If it is a virtual desktop already running (i.e it’s not new), what applications do you have open there? Have you noticed if this happens when you have specific program open/running in the desktop?

What happens if you open a new virtual desktop with same DE and with a different DE?

[Britgirl]

Thanks for letting us know.

It’s quite possible that it was something to do with the Mint installation as it seemed to be affecting just that machine; your other 2 Mint machines were ok. We use Mint a lot in our labs, as many version combinations as possible, and have not seen this.

Anyway, I’m glad you’ve fixed it, albeit in a drastic way! 😀 Keep nomachining!

[Britgirl]

Hi, just so I understand correctly. On your fourth machine running Mint 20.03 you can connect to it from another Player, so as a “server” it is working correctly?

But, when you want to connect from it to another computer (including localhost), you can’t?

 

I get logged out of my current session and presented with the Mint logon screen.

It’s this sentence which is confusing me 🙂 Is this referring to the Mint host as a Player or a Server?

[Britgirl]

To ebrandsberg2, we will check this out, thanks for the info. It’s very likely a different cause behind the black screen because one is a combination of RH7 with NM5 installed. Yours is Ubuntu (pre-release) with NM7.9 installed.

Anyway, here’s a reminder of our policies about installing pre-releases 😉 :

NoMachine policies to support pre-release/new versions of operating systems
https://knowledgebase.nomachine.com/AR03E00450

[Britgirl]

Hi, can you tell us what macOS version it is?

[Britgirl]

Server in NoMachine jargon is always the computer you are connecting to 🙂 We’re checking now that we have the additional information, and I will update the topic when I get feedback from the test team.

[Britgirl]

Hi, submit those attachments to forum[at]nomachine[dot]com.  Did you follow the instructions that I wrote in my earlier reply from last week?

[Britgirl]

Audio has to be enabled on the system you are connecting to (miniPC) and then from the connection menu you mute the sound on the server which appears to be what you did. Does this not mute audio on the server?

[Britgirl]

You can use --terminate or simply --restart nxserver.

Terminating the Session from Command Line

To terminate a virtual desktop or remote desktop session you can run:
nxserver --terminate SESSIONID or:

nxserver --terminate DISPLAYID

To terminate sessions of a certain user, run instead:
nxserver --terminate USERNAME

Finally, if you want to terminate all sessions, just restart the server:
nxserver --restart

or shutdown if you want to forbid new connections until the server is started again:
nxserver --shutdown

[Britgirl]

Hi, the free edition of NoMachine allows one connection to the remote physical desktop. If you are sitting in front of your computer and working on it locally, another user will be able to connect to it from remote in view or interactive mode (you can decide in the moment they connect). If, on the other hand, you’d like to connect remotely to your computer (one connection), another user cannot access your desktop because it would be considered two connections. In that case, you need Enterprise Desktop for Linux which will connect multiple users to the same physical display or NoMachine Workstation which lets you run up to 4 virtual desktops on the same host (NoMachine virtual desktops) and lets multiple users connect to them.

Differences between NoMachine Enterprise Desktop and the free to download NoMachine package
https://knowledgebase.nomachine.com/AR07L00808

Differences between NoMachine Free Edition for Linux and NoMachine Workstation for Linux
https://knowledgebase.nomachine.com/AR10K00702

In all of NoMachine products, the owner of the desktop decides if another user can connect in view-only or interactive mode is possible. You can also configure this in the NoMachine Server Settings of the computer you want to access. The guide here is useful for that: https://knowledgebase.nomachine.com/DT11R00177

For a user to connect they will need account credentials on that computer i.e username and password.  With the release of version 8, in attended desktop scenarios (i.e you must authorise) it will be possible for users to connect to your desktop without requiring a system account. They will be able to connect temporarily using the Guest Desktop Sharing functionality. This doesn’t change anything in the connection count that I described above.

More information about your question is also available here in the following topics:
‘https://forums.nomachine.com/topic/run-single-client-nomachine-to-reach-many-servers ‘
‘https://forums.nomachine.com/topic/connecting-when-another-user-is-locally-logged-in ‘
‘https://forums.nomachine.com/topic/what-is-physical-desktop-and-virtual-desktop ‘

[Britgirl]

Hello,

Due to changes in Windows API, we had to find an alternative solution based on a custom display driver.

We already opened a Trouble Report for this issue which you probably found linked in this forum assuming you’ve already searched as your post suggests. Maybe you already saw it? We are fully aware of the importance of having this feature and the solution will be released in version 8.

Screen blanking is no longer available on Windows 10, version 2004
https://knowledgebase.nomachine.com/TR10R09864

[Britgirl]

Hi, you are using an old version of NoMachine software on the server side which is no longer supported. If you search in this forum, black screen on Linux will take you to an article about headless machines (no monitor attached). It would seem that the problem is on the server side. Perhaps you updated the OS recently?

Connecting to Linux headless machines with NoMachine
https://knowledgebase.nomachine.com/AR03P00973

You don’t mention whether your server has the free version installed or if there is a Terminal Server product installed (e.g Workstation). Either way, if possible, please evaluate updating it because there have been numerous improvements since then and any investigation we carry out will only be on the latest version available to users.

[Britgirl]

Just to answer your questions from your last reply.

We are not sure if we need to /etc/NX/nxserver --virtualgl no  since we added those DesktopCommands, so we tried it both ways (/etc/NX/nxserver --virtualgl yes   and   no

Use  /etc/NX/nxserver --virtualgl yes only. Setting it to ‘no’ would just disable VirtualGL

 

Added both the following in /usr/NX/etc/node.cfg
DefaultDesktopCommand “/etc/gdm/Xsession ‘env XDG_SESSION_TYPE=x11 /usr/NX/scripts/vgl/vglrun gnome-session –session=gnome'”
CommandStartGnome “/etc/gdm/Xsession ‘env XDG_SESSION_TYPE=x11 /usr/NX/scripts/vgl/vglrun gnome-session –session=gnome”

It’s not necessary to insert vglrun. You could try with

DefaultDesktopCommand "/bin/dbus-launch --exit-with-session gnome-session --session=gnome --disable-acceleration-check"

[Britgirl]

Hi, this feature is planned for the first release of version 8, which is in its final stages of development.

[Britgirl]

A shared drive will show up like in the last image of the tutorial here: https://www.nomachine.com/accessing-files-on-local-or-remote-disk-drives. It appears as a folder, in our case “My office documents”.  We checked on our Windows machines in our lab and were able to share. Can you show us a screenshot, if possible, of what you see when you open the explorer?

[Author]

Posts