NoMachine closes immediately when opening a virtual desktop

Forums / NoMachine for Mac / NoMachine closes immediately when opening a virtual desktop

Viewing 2 posts - 1 through 2 (of 2 total)
  • Author
    Posts
  • #38074
    CM_11
    Participant

    I am having trouble connecting to a Linux server using NoMachine on Mac (MacOS Monterey, version 12.2.1). I am able to connect to the Linux server (as I am prompted for my password), but when I go to open the virtual desktop, the window closes spontaneously without any warnings. This doesn’t appear to be an issue with the server, but with the client software. This issue began prior to the new update (version 7.8.2) and is continuing even after updating NoMachine to version 7.9.2.

    #38087
    Britgirl
    Keymaster

    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?

Viewing 2 posts - 1 through 2 (of 2 total)

Closed because the user did not provide further feedback. Please notify us if you confirm that it is resolved or open a new topic if you have the same problem.