NXFrameBuffer failed to start headless in NixOS

Forums / NoMachine for Linux / NXFrameBuffer failed to start headless in NixOS

Viewing 2 posts - 1 through 2 (of 2 total)
  • Author
    Posts
  • #41199
    omnibs
    Participant

    I’m trying to set up NoMachine 7.10.1 on NixOS 22.05.

    I read the arch wiki article, adapted what I could from answers linked from there, and I’ve also ready this thread which also talks about “NXFrameBuffer failed to start”.

    This is my /etc/NX/node.cfg:

    AudioInterface “pulseaudio”
    AvailableSessionTypes “unix-remote,unix-console,unix-default,unix-application,physical-desktop,shadow”
    ConfigFileVersion “4.0”
    DefaultDesktopCommand “dbus-launch –exit-with-session /nix/store/mq9xbqnrxhhy6bznlb8cpf93dvca5b6f-i3-4.20.1/bin/i3”
    DisplayEncoderThreads “auto”
    DisplayServerThreads “auto”
    EnableCUPSSupport 0
    EnableDebug 1
    EnableDirectXSupport 0
    EnableEGLCapture 0
    EnableSmartcardSharing 1
    PhysicalDisplays “:10”
    SessionLogLevel 6

    This is what shows up in nxserver.log:

    Starting LS 7.10.1 and services.
    NXSERVER System information: Linux, standalone.
    NXSERVER User ‘user’ logged in from ‘192.168.15.24’ using authentication method NX-password.
    NXSERVER ERROR! Received error message from node ‘localhost:4000’, ‘Session failed, application terminated prematurely.’.
    NXSERVER ERROR! NXFrameBuffer failed to start.
    NXSERVER ERROR! Received error message from nxserver NX> 501 ERROR: Session failed, application terminated prematurely.\nNX> 501 ERROR: Session failed, application terminated prematurely.
    NXSERVER ERROR! Received error from nxserver –daemon NX> 501 ERROR: Session failed, application terminated prematurely.\nNX> 501 ERROR: Session failed, application terminated prematurely.
    NXSERVER User ‘user’ from ‘192.168.15.24’ logged out.

    I noticed whatever I put in DefaultDesktopCommand won’t change the logged output. I also tried the style shown in the arch wiki with “env DBUS_SESSION_BUS_ADDRESS=unix:path=/run/user/$(id -u)/bus /path/to/i3” and a bogus “oaiwhdaiowdh” command. No change.

    Not sure if relevant: I’m running a Sway on Wayland as my local session, and while this local session runs, I’m trying to start the NoMachine server assigned to a different PhysicalDisplay for the remote session. I tried launching Sway with NoMachine, putting it in the DefaultDesktopCommand, and once it failed, I pivoted to i3, which is the config I shared above.

    Would love help diagnosing further!

    #41266
    Britgirl
    Participant

    Hi,

    can you tell us the complete DefaultDesktopCommand you are using?

    We see that you are probably using custom built binaries. Have you checked that you can login to the GUI locally? I.e not with NoMachine involved.

    If you can, open a terminal and run env > /tmp/env-i3.txt. Send us the file and we’ll take a look.

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

Closed because the user did not provide further feedback. Please notify us if you confirm that it is resolved or open a new topic if you have the same problem.