> Am 09.05.2020 um 13:22 schrieb Richard Tobin <rich...@inf.ed.ac.uk>: > > >>>> 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")
kuku@Christophs-MBP ~ % xclock -display :0 Error: Can't open display: :0 kuku@Christophs-MBP ~ % xclock -display \:0 Error: Can't open display: :0 kuku@Christophs-MBP ~ % echo $DISPLAY /private/tmp/com.apple.launchd.vabAbiJezH/org.macports:0 kuku@Christophs-MBP ~ % > > Is there a quartz-wm process running? > Not directy. WHat I see is: % ps ax | grep -i quartz 419 ?? Ss 0:00.09 /System/Library/Frameworks/Quartz.framework/Versions/A/Frameworks/QuickLookUI.framework/Versions/A/XPCServices/QuickLookUIService.xpc/Contents/MacOS/QuickLookUIService 13030 s008 R+ 0:00.00 grep -i quartz > -- Richard > > -- > The University of Edinburgh is a charitable body, registered in > Scotland, with registration number SC005336. >
