_Platform (on client): Mac OSX 10.14.3 (Mojave) _Platform (on server): Scientific Linux release 6.9 (Carbon) What is the difference between and XWindow opened for ROOT, and other interactive sessions like xeyes? it looks like the command was executed, and shows command line again for the next command. Just got a new MBP running El Capitan, and for whatever reason, step (3) above causes the Pi to pause for a sec, and do nothing, i.e. I was hoping some of you might have an idea, even just steps of troubleshooting? Start X11 Forwarding with /etc/X11/Xsession Back then I was on Mountain Lion, and downloaded XQuartz, step (3) worked. It looked like a segmentation fault in XQuartz on my local Mac, but I reinstalled, used more XQuartz versions, all producing the same… I could reproduce this error with all the other scientific linux machines I have right now access to. Which is just showing the XQuartz crash after trying to launch a window. In verbose session (ssh -XY -v) the output after launching the ROOT application is:ĭebug1: client_input_channel_open: ctype x11 rchan ĭebug1: client_request_x11: request from 129.129.141.177 53580ĭebug1: x11_connect_display: $DISPLAY is launchdĮrror in RootX11IOErrorHandler: fatal X11 error (connection to server lost?!) **** Save data and exit application **** When trying to launch a root application with a TCanvas (or from cint a TBrowser, or anything with ROOT graphics), a window blops up for a (milli)second and then XQuartz on my side crashing. Most importantly I can tunnel trough ALL X windowsI tried (xclock, xeyes, geany, emacs…), but it fails with ROOT.
Type the following command at the prompt: ssh -p 20110 -Y wvulogin Visit our Shell Server page for the updated list of available shell server addresses.Be sure to use the -X option to allow the X connection to tunnel thorough SSH. I try to do ssh tunneling from a scientific linux server to mac (see details at end) byĪll authentications are correct, config files checked, xauth OK, DISPLAY environment seems ok. Open the Terminal app and login to the shell servers via SSH.
I have a really unusual problem, and I do not have a better guess than this is connected somehow to ROOT.