NoMachine in Ubuntu Focal Docker fails with dbus error

Forums / NoMachine for Linux / NoMachine in Ubuntu Focal Docker fails with dbus error

Viewing 2 posts - 1 through 2 (of 2 total)
  • Author
    Posts
  • #28567
    Avatararcasops
    Participant

    I have a Ubuntu 16 Desktop and am trying to setup NoMachine in a docker container as per this post https://www.nomachine.com/DT10O00161.

    Have changed the Ubuntu version to Focal and the version of NoMachine to 6.12 but rest is same.

    At the time of client login the server log says this:

    020-07-17 16:37:47 783.008   771 NXSERVER User 'nomachine' logged in from '192.168.1.103' using authentication method NX-password.
    
    2020-07-17 16:37:56 960.285   809 NXNODE   WARNING! Process '/bin/bash --norc -c exec -a - /bin/bash -c 'dbus-launch --exit-with-session gnome-session --session=ubuntu'' with pid '854/854' finished with signal 5 after 0,425 seconds.
    
    2020-07-17 16:37:56 960.826   809 NXNODE   ERROR! Application terminated too early.
    
    2020-07-17 16:37:57 581.406   791 NXSERVER ERROR! Received error message from node 'localhost:4000', 'Session failed, application terminated prematurely.'.
    2020-07-17 16:37:57 725.967    15 NXSERVER ERROR! NXFrameBuffer failed to start.
    
    2020-07-17 16:37:57 726.147    15 NXSERVER ERROR! Received error message from nxserver NX> 501 ERROR: Session failed, application terminated prematurely.\nNX> 501 ERROR: Session failed, application terminated prematurely.
    
    2020-07-17 16:37:57 726.916   771 NXSERVER ERROR! Received error from nxserver --daemon NX
    #28611
    Avatarfisherman
    Moderator

    NoMachine docker documentation was focused on installing NoMachine on Debian with mate-core.

    As you did installed latest Ubuntu with Mate desktop you will need to change the following key DefaultDesktopCommand “/usr/bin/mate-session” of the NoMachine config file /usr/NX/etc/node.cfg inside of the container.

    Issue you mentioned is that our application did not detect correctly installed desktop environment and it did fallback to the default desktop environment of the Ubuntu.

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

You must be logged in to reply to this topic.