Forum Replies Created
-
AuthorPosts
-
Britgirl
KeymasterPlease tell us:
– NoMachine product and version on local and remote machine (free version, Workstation, etc).
– 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.
– Can you connect to the physical display of the Linux machine?March 31, 2022 at 10:26 in reply to: NX> 501 ERROR: Session failed, application terminated prematurely. #38114Britgirl
KeymasterHi, can you tell us:
– 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.
Britgirl
KeymasterIf I understand correctly, to get to the same desktop you are using NoMachine to connect, your friend is using another tool.
When you connect with NoMachine and the other tool to the same desktop, NoMachine is able to update the cursor position correctly when it is moved within the other tool’s session. So this is fine up to this point. But, the other tool you are using doesn’t update the cursor position when you are in a NoMachine session.
This would make it a problem of the other software you are using ๐ Why not simply both of you use NoMachine?
Britgirl
KeymasterHi, you should use pulseaudio, yes.
Regarding the question about resolution, you could try changing the resolution by using the slide bar, by selecting one of the resolutions supported by the desktop -> within the session, open the menu with Ctrl-Alt-0, select Display -> Change settings. You will see something like illustrated in the guide here:
Guide to the Functionality in the Menu Panel on Linux
https://knowledgebase.nomachine.com/DT10R00168#5.8Britgirl
KeymasterTo start, this is not our own “new version update” notification, and we actually don’t have any idea of where it’s coming from, since, by the way, NoMachine doesn’t install or update through any “system repository”.
That said, if it was a NoMachine update availability notification, it wouldn’t be a “random update”, but an update availability notification from a software you installed and, reasonably, want to keep updated.
Britgirl
KeymasterWe aren’t aware of “no available desktops” errors when connecting to Monterey.
Can you enable debug, reproduce the problem, (restart nxserver, connect using nxplayer ), then collect logs and send to forum[at]nomachine[dot]com.
To enable debug on the Mac, follow the instructions here: https://knowledgebase.nomachine.com/DT11R00181#1.3.
Britgirl
KeymasterWe’re checking this. We encountered this same error a while back and have never been able to reproduce it again. Our library is being blocked by some Windows process. What you can do is click ignore, or reboot and then update NoMachine.ย Alternatively, close the process that is locking the library.
Britgirl
KeymasterThanks for letting us know. Glad you fixed it because we wouldn’t have been able to investigate further because v5 is no longer supported.
Britgirl
KeymasterHi, you don’t mention what version you are using. We recently fixed a bug in the release affecting 7.8.2 related to mDNS which was causing behaviour like you described.
High CPU usage of NoMachine Client on Ubuntu when listing the available machines and connections
https://knowledgebase.nomachine.com/TR09S10371If you are using 7.8.2 and don’t want to update to 7.9.2, you can use the workaround mentioned in the TR i.e disable networkย browsing. Open the client UI -> Settings -> Player -> Security and select ‘Don’t show other computers on the network’.
If you are already using 7.9.2, please send us the exact output of “top”, “top -H” (to also get the exact thread consuming the CPU), “atop” or whatever command you are using to get the system load.” We aren’t aware of reports of abnormal CPU usage in this version.
March 30, 2022 at 08:54 in reply to: NoMachine closes immediately when opening a virtual desktop #38087Britgirl
KeymasterYou 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/AR07K00675but 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
KeymasterThanks 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
KeymasterHi, 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
KeymasterTo 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/AR03E00450Britgirl
KeymasterHi, can you tell us what macOS version it is?
Britgirl
KeymasterServer 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.
-
AuthorPosts