Nyxt closes immediately upon opening

[jonathanabennett]

Platform: M1 Silicon MBP running Big Sur (11.6)

After following the steps in the README, I run the command docker run -it --rm bigdeddu/nyxt:2.2.2

After a few moments, an empty Nyxt window appears on the screen. Then, it closes almost immediately. Examining the logs of the Docker image produces the following:

(sbcl:12): dbind-WARNING **: 06:32:00.354: Couldn't connect to accessibility bus: Failed to connect to socket /tmp/dbus-nmErx2tSXk: Connection refused

<INFO> [06:32:01] Listening to socket "nyxt/nyxt.socket".

Nyxt version 2.2.2

(WebKitWebProcess:75): dbind-WARNING **: 06:32:08.997: Couldn't connect to accessibility bus: Failed to connect to socket /tmp/dbus-nmErx2tSXk: Connection refused

(WebKitWebProcess:71): dbind-WARNING **: 06:32:08.997: Couldn't connect to accessibility bus: Failed to connect to socket /tmp/dbus-nmErx2tSXk: Connection refused

/entrypoint.sh: line 4: 12 Killed nyxt

[deddu]

I don't have a M1 nearby to try out, so it's a bit hard for me to test. Are you running those commands in the Xquartz termina window? the dbus messages can be cleared by setting a NO_AT_BRIDGE=1 env variable.

here's a command line incantation, that will fire the app and set xquartz correctly. (you can paste/alias this in any terminal you like)

xterm -e 'xhost +127.0.0.1; docker run -it -e WEBKIT_DISABLE_COMPOSITING_MODE=1  -e NO_AT_BRIDGE=1 --rm --name nyxt bigdeddu/nyxt:2.2.2 nyxt '

see how this goes

[MaxSobolMark]

I'm having this same problem, even with version 2.2.4 and running the above command, also on M1 Mac. Any possible fixes?

[deddu]

I’m waiting for the delivery of an M1, ideally I’ll have a new MBP and an update before the end of the month.

[jonathanabennett]

Any update on this?

[dre-sctg]

I have finally received a mac m1 but I could not reproduce this problem. I do have websites crashing, exactly as before, but nyxt seems to be running. (perhaps a tad slow?)

# within the XQuartz terminal
export DISPLAY=:0 
xhost +127.0.0.1     
docker run --it --rm bigdeddu/nyxt:2:2:4

I saw the platform warning, but it worked without doing anything.

[jonathanabennett]

Update: I am able to get it to work by putting the above in a bash script and executing it from inside the xQuartz terminal. It ran for a while and then closed unexpectedly as I began really interacting with it. We can probably close this issue and I'll open a new issue for that later behavior once I can isolate it.