Re: X11 no longer working

On May 9, 2020, at 07:07, Christoph Kukulies wrote: > :info:build clang: warning: no such sysroot directory: > '/Library/Developer/CommandLineTools/SDKs/MacOSX10.15.sdk' [-Wmissing-sysroot] MacPorts expects that you have a versioned macOS SDK in the command line tools (or in Xcode, if the po

Re: X11 no longer working

>> Applications are now restricted where they can write to. I've found >> /usr/local and /opt are OK. I have not tried /var. > > According to https://en.wikipedia.org/wiki/System_Integrity_Protection, > /var is protected. > > You might try moving /var/root/.serverauth.6258 to /opt. /var itself

Re: X11 no longer working

On Sat, May 9, 2020 at 2:28 PM Jeffrey Walton wrote: > > On Sat, May 9, 2020 at 5:50 AM Christoph Kukulies wrote: > > > > Launching X11 manually ./X11 is a good point. Did that and XQuartz appears > > in the dock. Firing then xclock on the Target doesn’t do a connection. > > Silence. The xclock

Re: X11 no longer working

On Sat, May 9, 2020 at 5:50 AM Christoph Kukulies wrote: > > Launching X11 manually ./X11 is a good point. Did that and XQuartz appears in > the dock. Firing then xclock on the Target doesn’t do a connection. Silence. > The xclock just hangs there. > > I don’t see any listening socket: > > kuku@

Re: X11 no longer working

> Am 09.05.2020 um 16:29 schrieb Christopher Jones : > > > >> On 9 May 2020, at 1:21 pm, Christoph Kukulies > > wrote: >> >> The port install xorg-server went through and as a result I have XQuartz >> working again. >> >> Now you say I should revert this (japanes s

Re: X11 no longer working

> On 9 May 2020, at 1:21 pm, Christoph Kukulies wrote: > > The port install xorg-server went through and as a result I have XQuartz > working again. > > Now you say I should revert this (japanes sites’) hack. I removed the > symbolic link that this hack suggested, ran > sudo uninstall xorg-s

Re: X11 no longer working

> > 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/QuickLoo= > kUI.framework/Versions/A/XPCServices/QuickLookUIService.xpc/Contents/MacOS= > /Qui

Re: X11 no longer working

The port install xorg-server went through and as a result I have XQuartz working again. Now you say I should revert this (japanes sites’) hack. I removed the symbolic link that this hack suggested, ran sudo uninstall xorg-server and then sudo install xorg-server. It ran much faster now as if it

Re: X11 no longer working

Thats not what I am referring to. There was likely a warning earlier on directing you to the macports problem hot list. > On 9 May 2020, at 1:07 pm, Christoph Kukulies wrote: > > > >> Am 09.05.2020 um 13:51 schrieb Christopher Jones > >: >> >> >> then you n

Re: X11 no longer working

> Am 09.05.2020 um 13:51 schrieb Christopher Jones : > > > then you need to figure out what is failing for you with ossp-uuid ... > The error was this one: :info:build ../uuid.h:39:10: fatal error: 'sys/types.h' file not found see below in context: :info:build /usr/bin/clang -c -I. -I

Re: X11 no longer working

then you need to figure out what is failing for you with ossp-uuid ... > On 9 May 2020, at 12:48 pm, Christoph Kukulies wrote: > > > > > >> Am 09.05.2020 um 13:41 schrieb Christopher Jones > >: >> >> looks like your xorg-server installation is not working.

Re: X11 no longer working

> Am 09.05.2020 um 13:41 schrieb Christopher Jones : > > looks like your xorg-server installation is not working. Try removing it, > reinstall, then log out and back in again. That’s what I tried already and failed on that (see other post subject „Building xorg fails“): kuku@Christophs

Re: X11 no longer working

looks like your xorg-server installation is not working. Try removing it, reinstall, then log out and back in again. > On 9 May 2020, at 12:39 pm, Christoph Kukulies wrote: > > > >> Am 09.05.2020 um 13:22 schrieb Richard Tobin > >: >> >> > Does running xcloc

Re: X11 no longer working

> Am 09.05.2020 um 13:22 schrieb Richard Tobin : > > 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 al

Re: X11 no longer working

> >> 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 m

Re: X11 no longer working

The other strange thing is (on the target side, doing an nmap to the server): Nmap done: 1 IP address (1 host up) scanned in 334.13 seconds # nmap 192.168.178.51 Starting Nmap 7.70 ( https://nmap.org ) at 2020-05-09 12:55 CEST Nmap scan report for Christophs-MBP.fritz.box (192.168.178.51) Host is

Re: X11 no longer working

> Am 09.05.2020 um 12:39 schrieb Richard Tobin : > >>> Launching X11 manually ./X11 is a good point. Did that and XQuartz >>> appears in the dock. Firing then xclock on the Target doesn't do >>> a connection. Silence. The xclock just hangs there. >> >> Does running xclock or other X clients loc

Re: X11 no longer working

> > Launching X11 manually ./X11 is a good point. Did that and XQuartz > > appears in the dock. Firing then xclock on the Target doesn't do > > a connection. Silence. The xclock just hangs there. > > Does running xclock or other X clients locally work? > > If it does, X is listening on the unix s

Re: X11 no longer working

> Launching X11 manually ./X11 is a good point. Did that and XQuartz > appears in the dock. Firing then xclock on the Target doesn't do > a connection. Silence. The xclock just hangs there. Does running xclock or other X clients locally work? If it does, X is listening on the unix socket as expec

Re: X11 no longer working

Launching X11 manually ./X11 is a good point. Did that and XQuartz appears in the dock. Firing then xclock on the Target doesn’t do a connection. Silence. The xclock just hangs there. I don’t see any listening socket: kuku@Christophs-MBP ~ % ps ax | grep -i x11 88342 ?? Ss 0:00.81 /opt

Re: X11 no longer working

Ok, everything seems to be Ok in the target side! > Le 9 mai 2020 à 09:04, Christoph Kukulies a écrit : > > Here is the output. Nothing happens on the macOS side. I remembered that X11 > (Quartz) popped up automatically iin the dock and the xclock appeared on the > Mac desktop, last time it wo

Re: X11 no longer working

Here is the output. Nothing happens on the macOS side. I remembered that X11 (Quartz) popped up automatically iin the dock and the xclock appeared on the Mac desktop, last time it worked. kuku@Christophs-MBP ~ % ssh -Y -vv pc235 OpenSSH_8.1p1, LibreSSL 2.7.3 debug1: Reading configuration data /

Re: X11 no longer working

Hi, Some possibilities: 1) Try your « ssh -Y » in verbose mode like « ssh -v -Y » or « ssh -vv -Y » for more verbose and take a look at the displayed messages. 2) Is « xauth » package is on your target? 3) What about the « X11DisplayOffset » on your target? 4) What about these lines: