Hi, Joy-
Perhaps during your previous @SSwarper run where you got those Xvfb error messages, there was still an Xvfb command running from a previous call? Sometimes that can cause the error message you see.
Xvfb is a dependency you install when setting up AFNI. What Xvfb is (from that program's help):
Xvfb - virtual framebuffer X server for X Version 11
Xvfb is an X server that can run on machines with no display hardware and no physical
input devices. It emulates a dumb framebuffer using virtual memory.
It is used by several of the "automatic image generating" programs, such as @snapshot_volreg (possibly the first in AFNI to do so) and @chauffeur_afni. We use it to be able to open the AFNI GUi in a virtual environment, so you don't see the GUI and image windows open on your computer; that way, the GUi can be "driven" to make images even on remote machines, where a GUI can't open.
How to check for "stale" Xvfb sessions in a terminal: type "ps" in the terminal, and you will see a table listing all processes running. The first column is the "process ID", and the last column is the "command". You can end any of those with Xvfb or xvfb if you think they are stale (e.g., a previous command using it got interrupted while Xvfb had started by not closed, so now it keeps running in the background), by "killing" it based on its process ID. For example, run ps:
$ ps
PID TTY TIME CMD
13022 pts/9 00:00:00 Xvfb
13040 pts/9 00:00:00 ps
17746 pts/9 00:00:00 bash
... and then kill the Xvfb:
kill 13022
It is a little bit hard to know if this *was* the problem you had when you first ran @SSwarper, but that might have been... Having an existing Xvfb session running in the background can clash with starting a new Xvfb session, but it might not always do so. But if you do have to interrupt an @chauffeur_afni command in the terminal, then you might want to check if the Xvfb session didn't get a chance to close, and then "kill" it based on its PID, as shown above.
--pt
Edited 1 time(s). Last edit at 04/05/2020 09:43PM by ptaylor.
