Stuck on “Desktop not shared” after updating to 8.13.1

Forum / NoMachine for Linux / Stuck on “Desktop not shared” after updating to 8.13.1

Viewing 4 posts - 1 through 4 (of 4 total)
  • Author
    Posts
  • #48937
    maRT_sk
    Participant

    Hello,

    I am experiencing an issue with NoMachine on Ubuntu after updating from version 8.11.3 to 8.13.1. I am trying to connect from my Windows 11 PC to my physical Ubuntu 22.04 laptop.

    There should be an option available to enable desktop sharing, as shown in the documentation below:

    I cannot change this option, so I cannot enable it and it is stuck on “Desktop is not shared.”. I have never faced any connection issues before this update.

    Troubleshooting Steps Taken:

    Reinstalled NoMachine: I have uninstalled and reinstalled NoMachine several times, but the issue persists.

    Modified Configuration Files: I have modified some values in /usr/NX/etc/node.cfg in an attempt to resolve the issue, but without success.

    Tried to Enable nxnode: Attempted to manually start the nxnode service without success. The service remains disabled. Checked Service Status: When I run /etc/NX/nxserver –status, I receive the following output:

    NX> 111 New connections to NoMachine server are enabled.
    
    NX> 161 Enabled service: nxserver.
    
    NX> 162 Disabled service: nxnode.

    NX> 161 Enabled service: nxd.

     

    Checked Logs: Here are some log entries:

    118951 118951 2024-07-29 15:20:43 252.982 NXSERVER Shutting down NoMachine server and services.
    
    108570:signal-handler (1722259243) Received SIGTERM scheduling shutdown...
    
    108570 108570 15:20:43 344.159 Redis: User requested shutdown....
    
    108570 108570 15:20:43 344.260 Redis: Saving the final RDB snapshot before exiting..
    
    108570 108570 15:20:43 348.236 Redis: Redis is now ready to exit, bye bye....
    
    118951 118951 2024-07-29 15:20:43 474.362 NXSERVER WARNING! NXRedis: Cannot get output for command 'get'. Resending commands failed.
    
    118951 118951 2024-07-29 15:20:43 474.418 NXSERVER WARNING! NXRedisScript: wrong sha: '' for script 'getAllCMWithTheirPids'. Trying get one more time.
    
    118951 118951 15:20:43 476.639 Redis: Server started, Redis version 3.0.7.
    
    118951 118951 15:20:43 476.774 Redis: DB loaded from disk: 0.000 seconds.
    
    118951 118951 2024-07-29 15:20:43 510.834 ServerRedisServer: Finishing handler.
    
    118951:signal-handler (1722259243) Received SIGTERM scheduling shutdown...
    
    118951 118951 2024-07-29 15:20:43 510.868 ServerRedisServer: Waiting handler to terminate.
    
    118951 118951 15:20:43 578.163 Redis: User requested shutdown....
    
    118951 118951 15:20:43 578.240 Redis: Saving the final RDB snapshot before exiting..
    
    118951 118951 15:20:43 582.147 Redis: Redis is now ready to exit, bye bye....
    
    118951 118951 2024-07-29 15:20:43 582.569 ServerRedisServer: Cleaning up handler information.
    
    118992 118992 15:20:43 968.173 Redis: Server started, Redis version 3.0.7.
    
    118992 118992 15:20:43 968.309 Redis: DB loaded from disk: 0.000 seconds.
    
    118992 118992 2024-07-29 15:20:44 051.473 NXSERVER Starting LS 8.13.1 and services.
    
    118992 118992 2024-07-29 15:20:44 051.547 NXSERVER System information: Ubuntu 22.04.4 LTS, standalone.
    
    118992 119097 2024-07-29 15:20:44 056.880 LocateClient/DaemonSession: ERROR! No value found for local option 'uuid'.
    
    Error: No value found for local option 'uuid'.
    
    118992 119097 2024-07-29 15:20:44 056.915 LocateClient/Threadable: WARNING! Aborting threadable 0x7caa08002580.
    
    118992 119097 2024-07-29 15:20:44 056.921 LocateClient/Threadable: WARNING! Error is 22, 'Invalid argument'.
    
    118992 119097 2024-07-29 15:20:44 056.926 LocateClient/Threadable: WARNING! Threadable 0x7caa08002580 aborted.
    
    118992 119097 2024-07-29 15:20:44 056.928 LocateClient/Threadable: WARNING! Setting error in threadable 0x7caa08002580.
    
    118992 119097 2024-07-29 15:20:44 056.932 LocateClient/Threadable: WARNING! Restoring context from threadable 0x7caa08002580.
    
    118992 118992 2024-07-29 15:20:44 056.997 NXSERVER WARNING! NXRedis: empty field in command line 'command=evalsha,service=db,key=<del>***removed***</del>,field=0,field=\n'.
    
    118992 118992 2024-07-29 15:20:44 057.049 NXSERVER WARNING! NXRedis: Sending command 'command=evalsha,service=db,key=<span style="text-decoration-line: line-through;">***removed***</span>,field=0,field=\n' aborted.
    
    118992 119096 2024-07-29 15:20:44 057.105 LocateClientApplication/DaemonClientApplication: WARNING! Session terminated abnormally.
    
    118992 119096 2024-07-29 15:20:44 057.115 LocateClientApplication/DaemonClientApplication: WARNING! Error is 22, 'Invalid argument'.

    I would appreciate any guidance on how to resolve this issue and re-enable desktop sharing.

    Thank you in advance for your help!

    #48942
    Britgirl
    Keymaster

    Hi, just to confirm that we understand the issue, do you mean that on your NoMachine Ubuntu host, you cannot see the small “Shared/Not shared” window at all or you see it but cannot change it?

    #48954
    maRT_sk
    Participant

    On the host, the option to change from “Desktop not shared” to “Desktop shared”  is not displayed, and I am stuck with “Desktop not shared” – I cannot change it because I do not see the other option.

    On the client, I receive the following message when attempting to connect to the host:

    Cannot detect any display running. Do you want NoMachine to create a new display and proceed to connect to the desktop?

    Previously, NoMachine would automatically connect me to my Ubuntu desktop, allowing me to control my physical machine.

    #48959
    Britgirl
    Keymaster

    We need to see logs from the affected Ubuntu host.

    Please enable debug, restart nxserver, connect and then collect logs (using the command sudo /etc/NX/nxserver --debug --collect). Full instructions are available here: https://kb.nomachine.com/DT07S00243.

    Send them to forum[at]nomachine[dot]com. Please use the title of this topic as the subject of your email. Thanks!

    Edit 10/10/24: We have received no logs so cannot investigate. We suggest to uninstall completely and re-install NoMachine (the latest version is 8.14) and open a new topic if you have any issues.

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

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