If you are actually using X Display :1 for something, you can change the config.yml file to reference a different display (e.g. That should free up the X display for you to try again. Try running ps | grep -i xvfb and see if it shows a running Xvfb process. Unfortunately, there are a few cases where the environment dies and doesn't close the Xvfb process, leaving the X display in use. probably not the case), or more likely, if you had attempted to run the environment and had it crash at some point where it didn't clean up properly.
multi-monitor with each monitor having its own X server. This can happen if you are running a (non-standard) setup with multiple X displays (e.g. In other words, the environment is attempting to spawn a new X display on :1īased on the error message you provided, it looks like the display :1 is already in use. Because most people are running a desktop environment on display :0, I defaulted the configuration to use display :1.
The gym environment is attempting to establish a virtual display using XVFB (X Virtual Frame Buffer) to run the N64 emulator. This is what is used by default to display your desktop environment (i.e. X Display :0 is your primary X11 display.
