og00r

Forum Replies Created

Viewing 15 posts - 1 through 15 (of 43 total)
  • Author
    Posts
  • in reply to: Authentication failed (but only at one device) #25600
    Avatarog00r
    Contributor

    In received logs there are only logs from client side, which is not enough to proceed with problem.

    Please enable logs on server side reproduce the problem and send them if possible.
    Here is article how to do this:
    https://www.nomachine.com/DT10O00163

    At this moment all can I say, is that connection is closed after entering username to login procedure.

    Please ensure that account name is correct and user is active in system.

    in reply to: 6.9.2_1 does not seem to fix kde problem #24898
    Avatarog00r
    Contributor

    Can you try start session without dbus? Just change DefaultDesktopCommand in node.cfg to:

    DefaultDesktopCommand "/usr/bin/dbus-launch --sh-syntax /usr/bin/startplasma-x11"

    and try again

    also could you give us version of yours dbus-launch? and Manjaro version?
    Any logs in /var/log or journactl (if available)?

    in reply to: MacOS start NX server at boot time? #24347
    Avatarog00r
    Contributor

    Looks like it is a problem with the detection of the correct desktop owner on your machine, as there is no current workaround for such issue, we could prepare and send you patched package. Are you interested in receiving and testing it?

    in reply to: Login loop Ubuntu 18.04 #24305
    Avatarog00r
    Contributor

    To disable Wayland, restart of the machine is suggested.

    But can you paste output of
    /etc/NX/nxserver –version
    to ensure which version are you using?

    Also is it virtual session for that affected user? If yes can he try disabling automatic screen lock in operating system config?
    After this, creation of new virtual session will be requested.

    in reply to: MacOS start NX server at boot time? #24302
    Avatarog00r
    Contributor

    Logs don’t include the full problem (looks like could be enabled little to late), could you check next time on login window if:
    – nxserver –daemon is running (for example with ps -ef | grep nx)
    – then gather his pid and check if it is listening on localhost (command sudo lsof -p <pid of nxserver --daemon> | grep -a LISTEN)

    Also new set of logs with these informations would be needed, at the moment it looks like daemon is not running or is not accepting any connections.

    in reply to: Login loop Ubuntu 18.04 #24292
    Avatarog00r
    Contributor

    Few questions:

    – Is that login loop on ubuntu login window or do you mean login loop in nxplayer?
    – What version of NoMachine are you using?
    – Maybe session (or login window) is running on Wayland? (currently Wayland is not supported on VM)
    – Is there any information that login failed?
    – Is he trying to connect his own session or someone else’s session?

    in reply to: NoMachine Ubuntu 18.04 VM #24263
    Avatarog00r
    Contributor

    Just looking on the forum seems I have to disable Wayland on the Ubuntu VM as Display Server. Is it correct?

    Yes, NoMachine does not support Wayland on virtual machines. You can disable it:
    E.g. in case of GNOME desktop, add the following key to /etc/gdm/custom.conf:
    WaylandEnable=false

    and restart gdm:
    systemctl restart gdm

    Related to the Display Settings the maximum resolution available is the resolution of the VM I have to connect to, or there are some limit?

    Yes, it is maximum.

    in reply to: MacOS start NX server at boot time? #24264
    Avatarog00r
    Contributor

    What version of macOS are you using?

    Was it installed through command line? If not and if mac os is not “Catalina” then we will need some logs.
    Article on how to collect logs:

    https://www.nomachine.com/DT10O00163 (“How to gather debug logs for support requests”)

    Please enable them and reproduce issue (restart whole os that it will be on login window, try to connect, then log in and connect correctly again.

    Gather logs after that.

    After gathering logs, please send them to forum[at]nomachine[dot]com using the title of that forum’s thread as the mail’s subject.

     

    Could you also show ouput of # /etc/NX/nxserver –status when it is on login window?

     

    in reply to: Black screen or session negotiation failed #24232
    Avatarog00r
    Contributor

    Could you please gather some logs for us to check this issue?
    Article on how to collect logs:

    https://www.nomachine.com/DT10O00163 (“How to gather debug logs for support requests”)

    Please enable them, restart the nxservice:
    ‘/etc/NX/nxserver –restart’
    And try reproduce problem.
    Gather logs then.
    After gathering logs, please send them to forum[at]nomachine[dot]com using the title of that forum’s thread as the mail’s subject.

    But I must ask why did you stop gdm? Is it on purpose? Because now it will try to create virtual session.

    in reply to: Win-Win NoMachine unable to connect anymore #24149
    Avatarog00r
    Contributor

    Is it happening before or after login?

    To understand better what is happening, we need to see the server-side logs from the destination Windows host.
    Please follow the instructions here: https://www.nomachine.com/AR10K00697 and then send them to forum[at]nomachine[dot]com.
    Enable logs, restart NoMachine, reproduce problem, gather logs and send them.
    Also output from nxserver –status could be useful.

     

    in reply to: NX won’t work with recent KDE 5.17 #24108
    Avatarog00r
    Contributor

    About that warnings:

    ‘NX> 162 WARNING: Cannot find X servers running on this machine.

    NX> 162 WARNING: A new virtual display will be created on demand.’

    It happens because NoMachine cannot find correct session with new plasma in version 5.17.
    There is Trouble Report for it (separate from TR10Q09440):

    https://www.nomachine.com/TR10Q09441

    As there is no workaround at this moment we could prepare packages with fix for you, but you should confirm what packages you are using (nxserver –version) on what architecture (x86 or x64).

    in reply to: KDE/Plasma 5.17 session doesn’t start #24107
    Avatarog00r
    Contributor

    So I assume virtual sessions are working correctly right now?

    About warning during restart and physical session.

    ‘NX> 162 WARNING: Cannot find X servers running on this machine.

    NX> 162 WARNING: A new virtual display will be created on demand.’

    It happens, because NoMachine can not find correct session with new plasma in version 5.17.
    There is a Trouble Report for it:

    https://www.nomachine.com/TR10Q09441

    As there is not workaround at this moment we could prepare package with fix for you, but we need to know what packages you are using (nxserver –version) on what architecture (x86 or x64) for Arch Linux?

    in reply to: KDE/Plasma 5.17 session doesn’t start #24089
    Avatarog00r
    Contributor

    Could you try:
    add “env -u WAYLAND_DISPLAY” to DefaultDesktopCommand

    DefaultDesktopCommand “env -u WAYLAND_DISPLAY /usr/bin/dbus-launch –sh-syntax –exit-with-session /usr/bin/startplasma-x11” ?

     

    This should work for any installations running NoMachine virtual desktop sessions (e.g you have Workstation installed) and also the free version when NoMachine uses its own embedded X server. To be able to run a physical desktop session, a patch from us is required. We are preparing a package that will fix the issues reported here and will let you know when it’s ready.

    in reply to: Cannot open a virtual desktop #23488
    Avatarog00r
    Contributor

    Creating M-servername-xxxx directory won’t help in this case, this directory is dynamically by nxnode for each session. You should check if user Adm_XXX (I assume that you are trying create session for him) has correct access (permissions) to /usr1/, /usr1/people/ and /usr1/people/Adm_XXX

    If you think that there everything is ok, but it still won’t work you can redirect place where that directory is created by editing node.cfg. Default path should be /usr/NX/etc/node.cfg on remote machine. There is key #UserNXDirectoryPath which points where directory should be created. You must uncomment it and provide path which exist and users have access. There is good example in key description in config file.

    in reply to: Cannot open a virtual desktop #23454
    Avatarog00r
    Contributor

    Did you check that full path to directory which returns error exists, got correct permissions and correct owner is set for directory and parents directory? Could you paste which directory cannot be created?

Viewing 15 posts - 1 through 15 (of 43 total)