Andras Lasso
You probably want to separate users (not just screens but files, processes, etc) and you can achieve that by running the kernel in a docker container, as it is done...
We don't use a window manager in the slicer-notebook docker image, to keep the GUI simple (don't show window controls inside notebooks). I guess this is just an unlucky situation...
Can you check if you can launch Slicer successfully on that system (without Jupyter) and maybe get a stack trace?
Most common issue in a server environment is wrong X or OpenGL configuration. See all the questions on the Slicer forum about running Slicer on a headless system.
@pieper I guess your experience is needed here.
Jupyter replaces `{connection_file}` in `kernel.json` with the actual connection file. You need to do the same if you want to test it by running the command yourself.
Slicer logs everything into the Slicer log files.
Can you post a screenshot? Is the problem that the text is displayed or that something does not work correctly?
The ascii word art is displayed the Jupyter client calls kernel_info_request. I don't remember any of the Jupyter clients calling this or at least it did not display the result....
I don't remember ever seeing this XEUS graphics, but Slicer starting up minimized is the expected behavior. You don't need GUI access to the server, you should be able to...