> >> Does running xclock or other X clients locally work?
> No. xclock also hangs locally. So it's not an ssh problem. > > Also, do ssh -v -Y and see what it says about X11 forwarding. > Have gone through the ssh connection already in previous posts. So you did, I missed that. > What make me wonder is, when I'm looking at the process command > line of the Xquartz process that there is a -nolisten tcp (?!) > > 6306 s003 S< 0:00.00 /opt/X11/bin/Xquartz :0 -nolisten tcp -iglx > -auth /var/root/.serverauth.6258 That's ok, you're not trying to connect to X by TCP, but through the unix socket :0. (Just to be sure, try "xclock -display :0") Is there a quartz-wm process running? -- Richard -- The University of Edinburgh is a charitable body, registered in Scotland, with registration number SC005336.
