Blank/black screen when connecting to Mac Studio

Forum / NoMachine for Mac / Blank/black screen when connecting to Mac Studio

Viewing 2 posts - 1 through 2 (of 2 total)
  • Author
    Posts
  • #40119
    khawkins.sfdc
    Participant

    I’m having seemingly the exact same issue as https://forums.nomachine.com/topic/black-screen-when-connecting-to-idle-m1-mac, which I know was supposedly fixed. It’s easily and reliably/constantly reproducible for me.

    Client specs:

    • MacBook Pro (16-inch, 2019) / x86_64, macOS 12.5.1
    • NoMachine Enterprise Client 7.10.1

    Server specs:

    1. Mac Studio (2022) / Apple M1 Max, macOS 12.5.1
    2. NoMachine Enterprise Server 7.10.1

    Steps to reproduce:

    1. Establish a remote session to the Mac Studio machine.
    2. Go to the Apple menu and select “Lock Screen”. (You will see the expected lock screen and password challenge here, once you do.)
    3. Close the NoMachine session window on the client.
    4. Close the NoMachine app on the client (for good measure).
    5. Re-open NoMachine on the client and re-establish a connection to the existing session.

    Expected behavior:

    You’re presented with the lock screen and a password challenge.

    Actual behavior:

    You’re presented with a black/blank screen. You can see that the remote cursor is active/responsive, but you cannot interact with the desktop.

    The only thing I’ve found to solve the issue is to reboot the server machine. I’ve already captured server and client logs using the instructions provided in this link. Let me know if it’s okay to send them along to support.

    #40149
    Bilbotine
    Participant

    Hi khawkins.sfdc,

    Thanks for your post, we tested and reproduced a similar problem with version 7.10.1.

    That said, upgrading to the freshly released version 8 seems to fix the problem.

    The universal package for Mac is suitable for both Intel and M1 processor, please try it.

    Your feedback will be appreciated!

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

This topic was marked as closed, you can't post.