Login to a running session

Forums / NoMachine for Linux / Login to a running session

  • This topic has 5 replies, 3 voices, and was last updated 1 week ago by Avatarkroy.
Viewing 6 posts - 1 through 6 (of 6 total)
  • Author
    Posts
  • #26065
    Avatardimhr12
    Participant

    I used NoMachine to connect into a running session. But, in the later days when I connect, it create a new session with the same user, and I can’t see the same desktop with windows opened. Why this is happening?

    There is a new configuration needed, that maybe have been modified in a update?

    I’m using Kubuntu, NoMachine version 6.9.2 as client, trying to connect to another Kubuntu, with same version.

    #26086
    Avatarkroy
    Contributor

    Hi.

    It’s not quite clear to us what the problem is. Windows aren’t reopen after creating a new session or it’s not connecting to the physical session?

    #26117
    Avatardimhr12
    Participant

    It’s happening a double login.

    I have one notebook with browser opened, and when I connect with NoMachine, I don’t see these windows and applications opened. It is doing another login, with empty and new session. I wanna login to same session, as happened before.

    #26188
    Avatarkroy
    Contributor

    Which NoMachine verson you have – is it Workstation Evaluation or the free NoMachine version? Are you sure you are connecting as the same user which is owner of the desktop with the opened applications? Can you tell me the steps you take to connect? Perhaps you can submit the screenshots of the phases?

    #26205
    Avatardimhr12
    Participant

    I have free NoMachine version.

    Yes, I’m using the same user, the only of that machine.

    Step by step: I click right button in NoMachine icon notification area, select the machine I want to connect, fill username and password and it’s done. It happen the same when I select “Browse connections” in menu and select the machine to connect.

    Both machines have Kubuntu 18.04.1 x64.

    #26331
    Avatarkroy
    Contributor

    Did you tryd to reproduce problem after restarting nxserver or system reboot? It looks that somehow your physical desktop wasn’t detected by NoMachine so it creates a new one like it was headless. It could happen in situation where X server on the system was started much later than NoMachine server. Is it headless system and desktop was started manually? If yes, nxserver should be restarted (sudo /usr/NX/bin/nxserver --restart) after desktop startup.

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

You must be logged in to reply to this topic.