X11 no longer working

classic Classic list List threaded Threaded
24 messages Options
12
Reply | Threaded
Open this post in threaded view
|

X11 no longer working

Christoph Kukulies
Today is a havoc day. I changed my login shell to bash. Also added this BASH Silencing variable succesfully.
Was playing around for hours with my FreeBSD system in the network and in the morning I ran some X clients.
Alway saw the X11 Quartz icon in the dock.

Is it correct, the X server starts automatically if an X cient wants to connect over the network, right.
Last thing I did was to remove the X11 icon from the dock. Now suddenly when I ssh -Y to the FreeBSD system, start xclock there,
nothing happens. The xclock command line hangs on the client side. But no message at all. DISPLAY is localhost:10.0.

I did a reboot of the FreeBSD system already to no avail. What’s going on? Will reboot my Mac and next thing I’ll do is revert to zsh to see whether it has got to do with that.


Christoph

Reply | Threaded
Open this post in threaded view
|

Re: X11 no longer working

Pierre Malard
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:
        Source% ssh -Y user@cible
        Target% echo $DISPLAY
        Target% xclock

It’s not an SHELL problem.

Good luck

> Le 8 mai 2020 à 16:10, Christoph Kukulies <[hidden email]> a écrit :
>
> Today is a havoc day. I changed my login shell to bash. Also added this BASH Silencing variable succesfully.
> Was playing around for hours with my FreeBSD system in the network and in the morning I ran some X clients.
> Alway saw the X11 Quartz icon in the dock.
>
> Is it correct, the X server starts automatically if an X cient wants to connect over the network, right.
> Last thing I did was to remove the X11 icon from the dock. Now suddenly when I ssh -Y to the FreeBSD system, start xclock there,
> nothing happens. The xclock command line hangs on the client side. But no message at all. DISPLAY is localhost:10.0.
>
> I did a reboot of the FreeBSD system already to no avail. What’s going on? Will reboot my Mac and next thing I’ll do is revert to zsh to see whether it has got to do with that.
>
> —
> Christoph
>
--
Pierre Malard

   « Je n'ai jamais séparé la République des idées de justice sociale,
     sans laquelle elle n'est qu'un mot »
                                                                  Jean Jaures - 1887
   |\      _,,,---,,_
   /,`.-'`'    -.  ;-;;,_
  |,4-  ) )-,_. ,\ (  `'-'
 '---''(_/--'  `-'\_)   πr

perl -e '$_=q#: 3|\ 5_,3-3,2_: 3/,`.'"'"'`'"'"' 5-.  ;-;;,_:  |,A-  ) )-,_. ,\ (  `'"'"'-'"'"': '"'"'-3'"'"'2(_/--'"'"'  `-'"'"'\_): 24πr::#;y#:#\n#;s#(\D)(\d+)#$1x$2#ge;print'
- --> Ce message n’engage que son auteur <--


signature.asc (919 bytes) Download Attachment
Reply | Threaded
Open this post in threaded view
|

Re: X11 no longer working

Christoph Kukulies
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.





The X11DisplayOffset seems to be 10, although the line in sshd_config is commented out. 10 seems to be the default. But it used to work the day before yesterday. Don’t know what happened unless I had done something to the PATH or macports tree.

What I did was remove the X11 icon from the dock, but that after it stopped working. It is so that X11 Quartz normally launches automatically when a client requests an X11 connection, right?

Still clueless. Maybe I’m overlooking something very obvious?

Christoph

> Am 08.05.2020 um 17:41 schrieb Pierre Malard <[hidden email]>:
>
> 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:
> Source% ssh -Y user@cible
> Target% echo $DISPLAY
> Target% xclock
>
> It’s not an SHELL problem.
>
> Good luck
>
>> Le 8 mai 2020 à 16:10, Christoph Kukulies <[hidden email]> a écrit :
>>
>> Today is a havoc day. I changed my login shell to bash. Also added this BASH Silencing variable succesfully.
>> Was playing around for hours with my FreeBSD system in the network and in the morning I ran some X clients.
>> Alway saw the X11 Quartz icon in the dock.
>>
>> Is it correct, the X server starts automatically if an X cient wants to connect over the network, right.
>> Last thing I did was to remove the X11 icon from the dock. Now suddenly when I ssh -Y to the FreeBSD system, start xclock there,
>> nothing happens. The xclock command line hangs on the client side. But no message at all. DISPLAY is localhost:10.0.
>>
>> I did a reboot of the FreeBSD system already to no avail. What’s going on? Will reboot my Mac and next thing I’ll do is revert to zsh to see whether it has got to do with that.
>>
>> —
>> Christoph
>>
>
> --
> Pierre Malard
>
>   « Je n'ai jamais séparé la République des idées de justice sociale,
>     sans laquelle elle n'est qu'un mot »
>                                                                  Jean Jaures - 1887
>   |\      _,,,---,,_
>   /,`.-'`'    -.  ;-;;,_
>  |,4-  ) )-,_. ,\ (  `'-'
> '---''(_/--'  `-'\_)   πr
>
> perl -e '$_=q#: 3|\ 5_,3-3,2_: 3/,`.'"'"'`'"'"' 5-.  ;-;;,_:  |,A-  ) )-,_. ,\ (  `'"'"'-'"'"': '"'"'-3'"'"'2(_/--'"'"'  `-'"'"'\_): 24πr::#;y#:#\n#;s#(\D)(\d+)#$1x$2#ge;print'
> - --> Ce message n’engage que son auteur <--
>


log.txt (9K) Download Attachment
Reply | Threaded
Open this post in threaded view
|

Re: X11 no longer working

Pierre Malard
Ok, everything seems to be Ok in the target side!

> Le 9 mai 2020 à 09:04, Christoph Kukulies <[hidden email]> 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 worked.
>

A last test is to launch X11 « by the hand » on terminal and look if the XQuartz is really launched:
        $ /Applications/Utilities/XQuartz.app/Contents/MacOS/X11

I remember I had some problems with XQuartz since Catalina upgrade.
There has been no XQuartz update since 2016 and they indicate another solution to have X11 on Mac OS X: MacPorts (https://www.xquartz.org/releases/index.html).

So I have switched to MacPorts install and I have no problems with Catalina.

Other thing, take a look on this URL: https://askubuntu.com/questions/1029909/x11-forwarding-for-non-root-user-not-working

>
> <log.txt>
>
> The X11DisplayOffset seems to be 10, although the line in sshd_config is commented out. 10 seems to be the default. But it used to work the day before yesterday. Don’t know what happened unless I had done something to the PATH or macports tree.
>
> What I did was remove the X11 icon from the dock, but that after it stopped working. It is so that X11 Quartz normally launches automatically when a client requests an X11 connection, right?
>
> Still clueless. Maybe I’m overlooking something very obvious?
> —
> Christoph
>
>> Am 08.05.2020 um 17:41 schrieb Pierre Malard <[hidden email]>:
>>
>> 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:
>> Source% ssh -Y user@cible
>> Target% echo $DISPLAY
>> Target% xclock
>>
>> It’s not an SHELL problem.
>>
>> Good luck
>>
>>> Le 8 mai 2020 à 16:10, Christoph Kukulies <[hidden email]> a écrit :
>>>
>>> Today is a havoc day. I changed my login shell to bash. Also added this BASH Silencing variable succesfully.
>>> Was playing around for hours with my FreeBSD system in the network and in the morning I ran some X clients.
>>> Alway saw the X11 Quartz icon in the dock.
>>>
>>> Is it correct, the X server starts automatically if an X cient wants to connect over the network, right.
>>> Last thing I did was to remove the X11 icon from the dock. Now suddenly when I ssh -Y to the FreeBSD system, start xclock there,
>>> nothing happens. The xclock command line hangs on the client side. But no message at all. DISPLAY is localhost:10.0.
>>>
>>> I did a reboot of the FreeBSD system already to no avail. What’s going on? Will reboot my Mac and next thing I’ll do is revert to zsh to see whether it has got to do with that.
>>>
>>> —
>>> Christoph
>>>
>>
>> --
>> Pierre Malard
--
Pierre Malard

   «Mittler zwischen hirn und händen muss das hirz sein !»
   «La médiation entre le cerveau et les mains doit être le cœur !»
                                                 Fritz Lang - "Métropolis" - 1929
   |\      _,,,---,,_
   /,`.-'`'    -.  ;-;;,_
  |,4-  ) )-,_. ,\ (  `'-'
 '---''(_/--'  `-'\_)   πr

perl -e '$_=q#: 3|\ 5_,3-3,2_: 3/,`.'"'"'`'"'"' 5-.  ;-;;,_:  |,A-  ) )-,_. ,\ (  `'"'"'-'"'"': '"'"'-3'"'"'2(_/--'"'"'  `-'"'"'\_): 24πr::#;y#:#\n#;s#(\D)(\d+)#$1x$2#ge;print'
- --> Ce message n’engage que son auteur <--


signature.asc (919 bytes) Download Attachment
Reply | Threaded
Open this post in threaded view
|

Re: X11 no longer working

Christoph Kukulies
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/local/libexec/privileged_startx -d /opt/local/etc/X11/xinit/privileged_startx.d
 6254 s003  S+     0:01.61 ./X11.bin
 6258 s003  S+     0:00.02 /bin/sh /opt/X11/bin/startx -- /opt/X11/bin/Xquartz
 6305 s003  S+     0:00.00 /opt/X11/bin/xinit /opt/X11/lib/X11/xinit/xinitrc -- /opt/X11/bin/Xquartz :0 -nolisten tcp -iglx -auth /var/root/.serverauth.6258
 6306 s003  S<     0:00.00 /opt/X11/bin/Xquartz :0 -nolisten tcp -iglx -auth /var/root/.serverauth.6258
 6405 s003  S      0:00.03 /opt/X11/bin/quartz-wm
10624 s005  R+     0:00.00 grep -i x11
kuku@Christophs-MBP ~ % lsof -U | grep 6254
kuku@Christophs-MBP ~ % lsof -U | grep 6258
kuku@Christophs-MBP ~ % lsof -U | grep 6305
kuku@Christophs-MBP ~ % lsof -U | grep 6306
kuku@Christophs-MBP ~ % lsof -U | grep 6405
kuku@Christophs-MBP ~ % lsof -U | grep 88432
kuku@Christophs-MBP ~ % 



Reply | Threaded
Open this post in threaded view
|

Re: X11 no longer working

Richard Tobin-2
In reply to this post by Christoph Kukulies
> 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 expected and the
problem must be with ssh connecting to it.  What X-related lines
does /etc/ssh/ssh_config have?

-- Richard

--
The University of Edinburgh is a charitable body, registered in
Scotland, with registration number SC005336.

Reply | Threaded
Open this post in threaded view
|

Re: X11 no longer working

Richard Tobin-2
In reply to this post by Christoph Kukulies
> > 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 expected and the
> problem must be with ssh connecting to it.  What X-related lines
> does /etc/ssh/ssh_config have?

Also, do ssh -v -Y and see what it says about X11 forwarding.

-- Richard

--
The University of Edinburgh is a charitable body, registered in
Scotland, with registration number SC005336.

Reply | Threaded
Open this post in threaded view
|

Re: X11 no longer working

Christoph Kukulies


Am 09.05.2020 um 12:39 schrieb Richard Tobin <[hidden email]>:

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?

No. xclock also hangs locally.



If it does, X is listening on the unix socket as expected and the
problem must be with ssh connecting to it.  What X-related lines
does /etc/ssh/ssh_config have?

Also, do ssh -v -Y and see what it says about X11 forwarding.



Have gone through the ssh connection already in previous posts.


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

Who is doing that?

Christoph

-- Richard

--
The University of Edinburgh is a charitable body, registered in
Scotland, with registration number SC005336.


Reply | Threaded
Open this post in threaded view
|

Re: X11 no longer working

Christoph Kukulies
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 up (0.00050s latency).
All 1000 scanned ports on Christophs-MBP.fritz.box (192.168.178.51) are closed
MAC Address: A8:60:B6:2E:DF:6D (Apple)

Nmap done: 1 IP address (1 host up) scanned in 333.33 seconds


No port open to the outside.

Am 09.05.2020 um 13:07 schrieb Christoph Kukulies <[hidden email]>:



Am 09.05.2020 um 12:39 schrieb Richard Tobin <[hidden email]>:

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?

No. xclock also hangs locally.



If it does, X is listening on the unix socket as expected and the
problem must be with ssh connecting to it.  What X-related lines
does /etc/ssh/ssh_config have?

Also, do ssh -v -Y and see what it says about X11 forwarding.



Have gone through the ssh connection already in previous posts.


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

Who is doing that?

Christoph

-- Richard

--
The University of Edinburgh is a charitable body, registered in
Scotland, with registration number SC005336.



Reply | Threaded
Open this post in threaded view
|

Re: X11 no longer working

Richard Tobin-2
In reply to this post by Christoph Kukulies

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

Reply | Threaded
Open this post in threaded view
|

Re: X11 no longer working

Christoph Kukulies


Am 09.05.2020 um 13:22 schrieb Richard Tobin <[hidden email]>:


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.


Reply | Threaded
Open this post in threaded view
|

Re: X11 no longer working

Christopher Jones
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 <[hidden email]> wrote:



Am 09.05.2020 um 13:22 schrieb Richard Tobin <[hidden email]>:


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.


smime.p7s (2K) Download Attachment
Reply | Threaded
Open this post in threaded view
|

Re: X11 no longer working

Christoph Kukulies




Am 09.05.2020 um 13:41 schrieb Christopher Jones <[hidden email]>:

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-MBP ~ % sudo port install xorg-server
--->  Computing dependencies for xorg-server
The following dependencies will be installed: 
 font-adobe-100dpi
 font-adobe-75dpi
 font-adobe-utopia-100dpi
 font-adobe-utopia-75dpi
 font-adobe-utopia-type1
 font-arabic-misc
 font-bh-100dpi
 font-bh-75dpi
 font-bh-lucidatypewriter-100dpi
 font-bh-lucidatypewriter-75dpi
 font-bh-ttf
 font-bh-type1
 font-bitstream-100dpi
 font-bitstream-75dpi
 font-bitstream-speedo
 font-bitstream-type1
 font-cronyx-cyrillic
 font-cursor-misc
 font-daewoo-misc
 font-dec-misc
 font-ibm-type1
 font-isas-misc
 font-jis-misc
 font-micro-misc
 font-misc-cyrillic
 font-misc-meltho
 font-misc-misc
 font-mutt-misc
 font-schumacher-misc
 font-screen-cyrillic
 font-sony-misc
 font-sun-misc
 font-winitzki-cyrillic
 font-xfree86-type1
 fontconfig
 ossp-uuid
 xorg-fonts
Continue? [Y/n]: Y
--->  Fetching archive for ossp-uuid
--->  Attempting to fetch ossp-uuid-1.6.2_11+perl5_26.darwin_19.x86_64.tbz2 from https://packages.macports.org/ossp-uuid
--->  Attempting to fetch ossp-uuid-1.6.2_11+perl5_26.darwin_19.x86_64.tbz2 from http://nue.de.packages.macports.org/ossp-uuid
--->  Attempting to fetch ossp-uuid-1.6.2_11+perl5_26.darwin_19.x86_64.tbz2 from http://lil.fr.packages.macports.org/ossp-uuid
--->  Building ossp-uuid
Error: Failed to build ossp-uuid: command execution failed
Error: See /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_devel_ossp-uuid/ossp-uuid/main.log for details.
Error: Follow https://guide.macports.org/#project.tickets to report a bug.
Error: Processing of port xorg-server failed
kuku@Christophs-MBP ~ % 


On 9 May 2020, at 12:39 pm, Christoph Kukulies <[hidden email]> wrote:



Am 09.05.2020 um 13:22 schrieb Richard Tobin <[hidden email]>:


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.


Reply | Threaded
Open this post in threaded view
|

Re: X11 no longer working

Christopher Jones

then you need to figure out what is failing for you with ossp-uuid ...

On 9 May 2020, at 12:48 pm, Christoph Kukulies <[hidden email]> wrote:





Am 09.05.2020 um 13:41 schrieb Christopher Jones <[hidden email]>:

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-MBP ~ % sudo port install xorg-server
--->  Computing dependencies for xorg-server
The following dependencies will be installed: 
 font-adobe-100dpi
 font-adobe-75dpi
 font-adobe-utopia-100dpi
 font-adobe-utopia-75dpi
 font-adobe-utopia-type1
 font-arabic-misc
 font-bh-100dpi
 font-bh-75dpi
 font-bh-lucidatypewriter-100dpi
 font-bh-lucidatypewriter-75dpi
 font-bh-ttf
 font-bh-type1
 font-bitstream-100dpi
 font-bitstream-75dpi
 font-bitstream-speedo
 font-bitstream-type1
 font-cronyx-cyrillic
 font-cursor-misc
 font-daewoo-misc
 font-dec-misc
 font-ibm-type1
 font-isas-misc
 font-jis-misc
 font-micro-misc
 font-misc-cyrillic
 font-misc-meltho
 font-misc-misc
 font-mutt-misc
 font-schumacher-misc
 font-screen-cyrillic
 font-sony-misc
 font-sun-misc
 font-winitzki-cyrillic
 font-xfree86-type1
 fontconfig
 ossp-uuid
 xorg-fonts
Continue? [Y/n]: Y
--->  Fetching archive for ossp-uuid
--->  Attempting to fetch ossp-uuid-1.6.2_11+perl5_26.darwin_19.x86_64.tbz2 from https://packages.macports.org/ossp-uuid
--->  Attempting to fetch ossp-uuid-1.6.2_11+perl5_26.darwin_19.x86_64.tbz2 from http://nue.de.packages.macports.org/ossp-uuid
--->  Attempting to fetch ossp-uuid-1.6.2_11+perl5_26.darwin_19.x86_64.tbz2 from http://lil.fr.packages.macports.org/ossp-uuid
--->  Building ossp-uuid
Error: Failed to build ossp-uuid: command execution failed
Error: See /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_devel_ossp-uuid/ossp-uuid/main.log for details.
Error: Follow https://guide.macports.org/#project.tickets to report a bug.
Error: Processing of port xorg-server failed
kuku@Christophs-MBP ~ % 


On 9 May 2020, at 12:39 pm, Christoph Kukulies <[hidden email]> wrote:



Am 09.05.2020 um 13:22 schrieb Richard Tobin <[hidden email]>:


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.




smime.p7s (2K) Download Attachment
Reply | Threaded
Open this post in threaded view
|

Re: X11 no longer working

Christoph Kukulies


Am 09.05.2020 um 13:51 schrieb Christopher Jones <[hidden email]>:


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.. -fno-common -DPERL_DARWIN -mmacosx-version-min=10.15 -pipe -Os -isysroot/Library/Developer/CommandLineTools/SDKs/MacOSX10.15.sdk -fno-strict-aliasing -fstack-protector-strong -I/opt/local/include -DPERL_USE_SAFE_PUTENV -O3   -DVERSION=\"1.0602\" -DXS_VERSION=\"1.0602\"  "-I/opt/local/lib/perl5/5.26/darwin-thread-multi-2level/CORE"   uuid.c
:info:build clang: warning: no such sysroot directory: '/Library/Developer/CommandLineTools/SDKs/MacOSX10.15.sdk' [-Wmissing-sysroot]
:info:build In file included from uuid.xs:30:
:info:build ../uuid.h:39:10: fatal error: 'sys/types.h' file not found
:info:build #include <sys/types.h>
:info:build          ^~~~~~~~~~~~~
:info:build 1 error generated.
:info:build make[1]: *** [uuid.o] Error 1
:info:build make[1]: Leaving directory `/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_devel_ossp-uuid/ossp-uuid/work/uuid-1.6.2/perl'
:info:build make: *** [perl/blib/lib/OSSP/uuid.pm] Error 2
:info:build make: Leaving directory `/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_devel_ossp-uuid/ossp-uuid/work/uuid-1.6.2'
:info:build Command failed:  cd "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_devel_ossp-uuid/ossp-uuid/work/uuid-1.6.2" && /usr/bin/make -j8 -w all
:info:build Exit code: 2
:error:build Failed to build ossp-uuid: command execution failed
:debug:build Error code: CHILDSTATUS 19252 2
:debug:build Backtrace: command execution failed
:debug:build     while executing
:debug:build "system {*}$notty {*}$nice $fullcmdstring"
:debug:build     invoked from within
:debug:build "command_exec build"
:debug:build     (procedure "portbuild::build_main" line 8)
:debug:build     invoked from within
:debug:build "$procedure $targetname"
:error:build See /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_devel_ossp-uuid/ossp-uuid/main.log for details.
version:1
:debug:sysinfo macOS 10.15 (darwin/19.4.0) arch i386
:debug:sysinfo MacPorts 2.6.2
:debug:sysinfo Xcode 11.4.1
:debug:sysinfo SDK 10.15
:debug:sysinfo MACOSX_DEPLOYMENT_TARGET: 10.15
:debug:clean dropping privileges: euid changed to 502, egid changed to 501.
:debug:main Executing org.macports.main (ossp-uuid)


On 9 May 2020, at 12:48 pm, Christoph Kukulies <[hidden email]> wrote:





Am 09.05.2020 um 13:41 schrieb Christopher Jones <[hidden email]>:

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-MBP ~ % sudo port install xorg-server
--->  Computing dependencies for xorg-server
The following dependencies will be installed: 
 font-adobe-100dpi
 font-adobe-75dpi
 font-adobe-utopia-100dpi
 font-adobe-utopia-75dpi
 font-adobe-utopia-type1
 font-arabic-misc
 font-bh-100dpi
 font-bh-75dpi
 font-bh-lucidatypewriter-100dpi
 font-bh-lucidatypewriter-75dpi
 font-bh-ttf
 font-bh-type1
 font-bitstream-100dpi
 font-bitstream-75dpi
 font-bitstream-speedo
 font-bitstream-type1
 font-cronyx-cyrillic
 font-cursor-misc
 font-daewoo-misc
 font-dec-misc
 font-ibm-type1
 font-isas-misc
 font-jis-misc
 font-micro-misc
 font-misc-cyrillic
 font-misc-meltho
 font-misc-misc
 font-mutt-misc
 font-schumacher-misc
 font-screen-cyrillic
 font-sony-misc
 font-sun-misc
 font-winitzki-cyrillic
 font-xfree86-type1
 fontconfig
 ossp-uuid
 xorg-fonts
Continue? [Y/n]: Y
--->  Fetching archive for ossp-uuid
--->  Attempting to fetch ossp-uuid-1.6.2_11+perl5_26.darwin_19.x86_64.tbz2 from https://packages.macports.org/ossp-uuid
--->  Attempting to fetch ossp-uuid-1.6.2_11+perl5_26.darwin_19.x86_64.tbz2 from http://nue.de.packages.macports.org/ossp-uuid
--->  Attempting to fetch ossp-uuid-1.6.2_11+perl5_26.darwin_19.x86_64.tbz2 from http://lil.fr.packages.macports.org/ossp-uuid
--->  Building ossp-uuid
Error: Failed to build ossp-uuid: command execution failed
Error: See /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_devel_ossp-uuid/ossp-uuid/main.log for details.
Error: Follow https://guide.macports.org/#project.tickets to report a bug.
Error: Processing of port xorg-server failed
kuku@Christophs-MBP ~ % 


On 9 May 2020, at 12:39 pm, Christoph Kukulies <[hidden email]> wrote:



Am 09.05.2020 um 13:22 schrieb Richard Tobin <[hidden email]>:


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.




Reply | Threaded
Open this post in threaded view
|

Re: X11 no longer working

Christopher Jones

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 <[hidden email]> wrote:



Am 09.05.2020 um 13:51 schrieb Christopher Jones <[hidden email]>:


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.. -fno-common -DPERL_DARWIN -mmacosx-version-min=10.15 -pipe -Os -isysroot/Library/Developer/CommandLineTools/SDKs/MacOSX10.15.sdk -fno-strict-aliasing -fstack-protector-strong -I/opt/local/include -DPERL_USE_SAFE_PUTENV -O3   -DVERSION=\"1.0602\" -DXS_VERSION=\"1.0602\"  "-I/opt/local/lib/perl5/5.26/darwin-thread-multi-2level/CORE"   uuid.c
:info:build clang: warning: no such sysroot directory: '/Library/Developer/CommandLineTools/SDKs/MacOSX10.15.sdk' [-Wmissing-sysroot]
:info:build In file included from uuid.xs:30:
:info:build ../uuid.h:39:10: fatal error: 'sys/types.h' file not found
:info:build #include <sys/types.h>
:info:build          ^~~~~~~~~~~~~
:info:build 1 error generated.
:info:build make[1]: *** [uuid.o] Error 1
:info:build make[1]: Leaving directory `/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_devel_ossp-uuid/ossp-uuid/work/uuid-1.6.2/perl'
:info:build make: *** [perl/blib/lib/OSSP/uuid.pm] Error 2
:info:build make: Leaving directory `/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_devel_ossp-uuid/ossp-uuid/work/uuid-1.6.2'
:info:build Command failed:  cd "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_devel_ossp-uuid/ossp-uuid/work/uuid-1.6.2" && /usr/bin/make -j8 -w all
:info:build Exit code: 2
:error:build Failed to build ossp-uuid: command execution failed
:debug:build Error code: CHILDSTATUS 19252 2
:debug:build Backtrace: command execution failed
:debug:build     while executing
:debug:build "system {*}$notty {*}$nice $fullcmdstring"
:debug:build     invoked from within
:debug:build "command_exec build"
:debug:build     (procedure "portbuild::build_main" line 8)
:debug:build     invoked from within
:debug:build "$procedure $targetname"
:error:build See /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_devel_ossp-uuid/ossp-uuid/main.log for details.
version:1
:debug:sysinfo macOS 10.15 (darwin/19.4.0) arch i386
:debug:sysinfo MacPorts 2.6.2
:debug:sysinfo Xcode 11.4.1
:debug:sysinfo SDK 10.15
:debug:sysinfo MACOSX_DEPLOYMENT_TARGET: 10.15
:debug:clean dropping privileges: euid changed to 502, egid changed to 501.
:debug:main Executing org.macports.main (ossp-uuid)


On 9 May 2020, at 12:48 pm, Christoph Kukulies <[hidden email]> wrote:





Am 09.05.2020 um 13:41 schrieb Christopher Jones <[hidden email]>:

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-MBP ~ % sudo port install xorg-server
--->  Computing dependencies for xorg-server
The following dependencies will be installed: 
 font-adobe-100dpi
 font-adobe-75dpi
 font-adobe-utopia-100dpi
 font-adobe-utopia-75dpi
 font-adobe-utopia-type1
 font-arabic-misc
 font-bh-100dpi
 font-bh-75dpi
 font-bh-lucidatypewriter-100dpi
 font-bh-lucidatypewriter-75dpi
 font-bh-ttf
 font-bh-type1
 font-bitstream-100dpi
 font-bitstream-75dpi
 font-bitstream-speedo
 font-bitstream-type1
 font-cronyx-cyrillic
 font-cursor-misc
 font-daewoo-misc
 font-dec-misc
 font-ibm-type1
 font-isas-misc
 font-jis-misc
 font-micro-misc
 font-misc-cyrillic
 font-misc-meltho
 font-misc-misc
 font-mutt-misc
 font-schumacher-misc
 font-screen-cyrillic
 font-sony-misc
 font-sun-misc
 font-winitzki-cyrillic
 font-xfree86-type1
 fontconfig
 ossp-uuid
 xorg-fonts
Continue? [Y/n]: Y
--->  Fetching archive for ossp-uuid
--->  Attempting to fetch ossp-uuid-1.6.2_11+perl5_26.darwin_19.x86_64.tbz2 from https://packages.macports.org/ossp-uuid
--->  Attempting to fetch ossp-uuid-1.6.2_11+perl5_26.darwin_19.x86_64.tbz2 from http://nue.de.packages.macports.org/ossp-uuid
--->  Attempting to fetch ossp-uuid-1.6.2_11+perl5_26.darwin_19.x86_64.tbz2 from http://lil.fr.packages.macports.org/ossp-uuid
--->  Building ossp-uuid
Error: Failed to build ossp-uuid: command execution failed
Error: See /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_devel_ossp-uuid/ossp-uuid/main.log for details.
Error: Follow https://guide.macports.org/#project.tickets to report a bug.
Error: Processing of port xorg-server failed
kuku@Christophs-MBP ~ % 


On 9 May 2020, at 12:39 pm, Christoph Kukulies <[hidden email]> wrote:



Am 09.05.2020 um 13:22 schrieb Richard Tobin <[hidden email]>:


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.






smime.p7s (2K) Download Attachment
Reply | Threaded
Open this post in threaded view
|

Re: X11 no longer working

Christoph Kukulies
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 didn’t compile anything.

So I didn’t run into this error below again.

Thanks to all. 


X11 working again.

Christoph


Am 09.05.2020 um 14:09 schrieb Christopher Jones <[hidden email]>:


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 <[hidden email]> wrote:



Am 09.05.2020 um 13:51 schrieb Christopher Jones <[hidden email]>:


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.. -fno-common -DPERL_DARWIN -mmacosx-version-min=10.15 -pipe -Os -isysroot/Library/Developer/CommandLineTools/SDKs/MacOSX10.15.sdk -fno-strict-aliasing -fstack-protector-strong -I/opt/local/include -DPERL_USE_SAFE_PUTENV -O3   -DVERSION=\"1.0602\" -DXS_VERSION=\"1.0602\"  "-I/opt/local/lib/perl5/5.26/darwin-thread-multi-2level/CORE"   uuid.c
:info:build clang: warning: no such sysroot directory: '/Library/Developer/CommandLineTools/SDKs/MacOSX10.15.sdk' [-Wmissing-sysroot]
:info:build In file included from uuid.xs:30:
:info:build ../uuid.h:39:10: fatal error: 'sys/types.h' file not found
:info:build #include <sys/types.h>
:info:build          ^~~~~~~~~~~~~
:info:build 1 error generated.
:info:build make[1]: *** [uuid.o] Error 1
:info:build make[1]: Leaving directory `/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_devel_ossp-uuid/ossp-uuid/work/uuid-1.6.2/perl'
:info:build make: *** [perl/blib/lib/OSSP/uuid.pm] Error 2
:info:build make: Leaving directory `/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_devel_ossp-uuid/ossp-uuid/work/uuid-1.6.2'
:info:build Command failed:  cd "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_devel_ossp-uuid/ossp-uuid/work/uuid-1.6.2" && /usr/bin/make -j8 -w all
:info:build Exit code: 2
:error:build Failed to build ossp-uuid: command execution failed
:debug:build Error code: CHILDSTATUS 19252 2
:debug:build Backtrace: command execution failed
:debug:build     while executing
:debug:build "system {*}$notty {*}$nice $fullcmdstring"
:debug:build     invoked from within
:debug:build "command_exec build"
:debug:build     (procedure "portbuild::build_main" line 8)
:debug:build     invoked from within
:debug:build "$procedure $targetname"
:error:build See /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_devel_ossp-uuid/ossp-uuid/main.log for details.
version:1
:debug:sysinfo macOS 10.15 (darwin/19.4.0) arch i386
:debug:sysinfo MacPorts 2.6.2
:debug:sysinfo Xcode 11.4.1
:debug:sysinfo SDK 10.15
:debug:sysinfo MACOSX_DEPLOYMENT_TARGET: 10.15
:debug:clean dropping privileges: euid changed to 502, egid changed to 501.
:debug:main Executing org.macports.main (ossp-uuid)


On 9 May 2020, at 12:48 pm, Christoph Kukulies <[hidden email]> wrote:





Am 09.05.2020 um 13:41 schrieb Christopher Jones <[hidden email]>:

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-MBP ~ % sudo port install xorg-server
--->  Computing dependencies for xorg-server
The following dependencies will be installed: 
 font-adobe-100dpi
 font-adobe-75dpi
 font-adobe-utopia-100dpi
 font-adobe-utopia-75dpi
 font-adobe-utopia-type1
 font-arabic-misc
 font-bh-100dpi
 font-bh-75dpi
 font-bh-lucidatypewriter-100dpi
 font-bh-lucidatypewriter-75dpi
 font-bh-ttf
 font-bh-type1
 font-bitstream-100dpi
 font-bitstream-75dpi
 font-bitstream-speedo
 font-bitstream-type1
 font-cronyx-cyrillic
 font-cursor-misc
 font-daewoo-misc
 font-dec-misc
 font-ibm-type1
 font-isas-misc
 font-jis-misc
 font-micro-misc
 font-misc-cyrillic
 font-misc-meltho
 font-misc-misc
 font-mutt-misc
 font-schumacher-misc
 font-screen-cyrillic
 font-sony-misc
 font-sun-misc
 font-winitzki-cyrillic
 font-xfree86-type1
 fontconfig
 ossp-uuid
 xorg-fonts
Continue? [Y/n]: Y
--->  Fetching archive for ossp-uuid
--->  Attempting to fetch ossp-uuid-1.6.2_11+perl5_26.darwin_19.x86_64.tbz2 from https://packages.macports.org/ossp-uuid
--->  Attempting to fetch ossp-uuid-1.6.2_11+perl5_26.darwin_19.x86_64.tbz2 from http://nue.de.packages.macports.org/ossp-uuid
--->  Attempting to fetch ossp-uuid-1.6.2_11+perl5_26.darwin_19.x86_64.tbz2 from http://lil.fr.packages.macports.org/ossp-uuid
--->  Building ossp-uuid
Error: Failed to build ossp-uuid: command execution failed
Error: See /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_devel_ossp-uuid/ossp-uuid/main.log for details.
Error: Follow https://guide.macports.org/#project.tickets to report a bug.
Error: Processing of port xorg-server failed
kuku@Christophs-MBP ~ % 


On 9 May 2020, at 12:39 pm, Christoph Kukulies <[hidden email]> wrote:



Am 09.05.2020 um 13:22 schrieb Richard Tobin <[hidden email]>:


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.






Reply | Threaded
Open this post in threaded view
|

Re: X11 no longer working

Richard Tobin-2
In reply to this post by Christoph Kukulies
> > 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=
> /QuickLookUIService
> 13030 s008  R+     0:00.00 grep -i quartz

That's not even showing the Xquartz process!

-- Richard

--
The University of Edinburgh is a charitable body, registered in
Scotland, with registration number SC005336.

Reply | Threaded
Open this post in threaded view
|

Re: X11 no longer working

Christopher Jones
In reply to this post by Christoph Kukulies


On 9 May 2020, at 1:21 pm, Christoph Kukulies <[hidden email]> 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-server and then sudo install xorg-server. It ran much faster now as if it didn’t compile anything.

If you don’t follow the instructions in the link I sent you you will likely have other problems. The above means nothing as you didn’t rebuild anything. You have been warned...


So I didn’t run into this error below again.

Thanks to all. 


X11 working again.

Christoph


Am 09.05.2020 um 14:09 schrieb Christopher Jones <[hidden email]>:


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 <[hidden email]> wrote:



Am 09.05.2020 um 13:51 schrieb Christopher Jones <[hidden email]>:


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.. -fno-common -DPERL_DARWIN -mmacosx-version-min=10.15 -pipe -Os -isysroot/Library/Developer/CommandLineTools/SDKs/MacOSX10.15.sdk -fno-strict-aliasing -fstack-protector-strong -I/opt/local/include -DPERL_USE_SAFE_PUTENV -O3   -DVERSION=\"1.0602\" -DXS_VERSION=\"1.0602\"  "-I/opt/local/lib/perl5/5.26/darwin-thread-multi-2level/CORE"   uuid.c
:info:build clang: warning: no such sysroot directory: '/Library/Developer/CommandLineTools/SDKs/MacOSX10.15.sdk' [-Wmissing-sysroot]
:info:build In file included from uuid.xs:30:
:info:build ../uuid.h:39:10: fatal error: 'sys/types.h' file not found
:info:build #include <sys/types.h>
:info:build          ^~~~~~~~~~~~~
:info:build 1 error generated.
:info:build make[1]: *** [uuid.o] Error 1
:info:build make[1]: Leaving directory `/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_devel_ossp-uuid/ossp-uuid/work/uuid-1.6.2/perl'
:info:build make: *** [perl/blib/lib/OSSP/uuid.pm] Error 2
:info:build make: Leaving directory `/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_devel_ossp-uuid/ossp-uuid/work/uuid-1.6.2'
:info:build Command failed:  cd "/opt/local/var/macports/build/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_devel_ossp-uuid/ossp-uuid/work/uuid-1.6.2" && /usr/bin/make -j8 -w all
:info:build Exit code: 2
:error:build Failed to build ossp-uuid: command execution failed
:debug:build Error code: CHILDSTATUS 19252 2
:debug:build Backtrace: command execution failed
:debug:build     while executing
:debug:build "system {*}$notty {*}$nice $fullcmdstring"
:debug:build     invoked from within
:debug:build "command_exec build"
:debug:build     (procedure "portbuild::build_main" line 8)
:debug:build     invoked from within
:debug:build "$procedure $targetname"
:error:build See /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_devel_ossp-uuid/ossp-uuid/main.log for details.
version:1
:debug:sysinfo macOS 10.15 (darwin/19.4.0) arch i386
:debug:sysinfo MacPorts 2.6.2
:debug:sysinfo Xcode 11.4.1
:debug:sysinfo SDK 10.15
:debug:sysinfo MACOSX_DEPLOYMENT_TARGET: 10.15
:debug:clean dropping privileges: euid changed to 502, egid changed to 501.
:debug:main Executing org.macports.main (ossp-uuid)


On 9 May 2020, at 12:48 pm, Christoph Kukulies <[hidden email]> wrote:





Am 09.05.2020 um 13:41 schrieb Christopher Jones <[hidden email]>:

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-MBP ~ % sudo port install xorg-server
--->  Computing dependencies for xorg-server
The following dependencies will be installed: 
 font-adobe-100dpi
 font-adobe-75dpi
 font-adobe-utopia-100dpi
 font-adobe-utopia-75dpi
 font-adobe-utopia-type1
 font-arabic-misc
 font-bh-100dpi
 font-bh-75dpi
 font-bh-lucidatypewriter-100dpi
 font-bh-lucidatypewriter-75dpi
 font-bh-ttf
 font-bh-type1
 font-bitstream-100dpi
 font-bitstream-75dpi
 font-bitstream-speedo
 font-bitstream-type1
 font-cronyx-cyrillic
 font-cursor-misc
 font-daewoo-misc
 font-dec-misc
 font-ibm-type1
 font-isas-misc
 font-jis-misc
 font-micro-misc
 font-misc-cyrillic
 font-misc-meltho
 font-misc-misc
 font-mutt-misc
 font-schumacher-misc
 font-screen-cyrillic
 font-sony-misc
 font-sun-misc
 font-winitzki-cyrillic
 font-xfree86-type1
 fontconfig
 ossp-uuid
 xorg-fonts
Continue? [Y/n]: Y
--->  Fetching archive for ossp-uuid
--->  Attempting to fetch ossp-uuid-1.6.2_11+perl5_26.darwin_19.x86_64.tbz2 from https://packages.macports.org/ossp-uuid
--->  Attempting to fetch ossp-uuid-1.6.2_11+perl5_26.darwin_19.x86_64.tbz2 from http://nue.de.packages.macports.org/ossp-uuid
--->  Attempting to fetch ossp-uuid-1.6.2_11+perl5_26.darwin_19.x86_64.tbz2 from http://lil.fr.packages.macports.org/ossp-uuid
--->  Building ossp-uuid
Error: Failed to build ossp-uuid: command execution failed
Error: See /opt/local/var/macports/logs/_opt_local_var_macports_sources_rsync.macports.org_macports_release_tarballs_ports_devel_ossp-uuid/ossp-uuid/main.log for details.
Error: Follow https://guide.macports.org/#project.tickets to report a bug.
Error: Processing of port xorg-server failed
kuku@Christophs-MBP ~ % 


On 9 May 2020, at 12:39 pm, Christoph Kukulies <[hidden email]> wrote:



Am 09.05.2020 um 13:22 schrieb Richard Tobin <[hidden email]>:


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.








smime.p7s (2K) Download Attachment
Reply | Threaded
Open this post in threaded view
|

Re: X11 no longer working

Christoph Kukulies


Am 09.05.2020 um 16:29 schrieb Christopher Jones <[hidden email]>:



On 9 May 2020, at 1:21 pm, Christoph Kukulies <[hidden email]> 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-server and then sudo install xorg-server. It ran much faster now as if it didn’t compile anything.

If you don’t follow the instructions in the link I sent you you will likely have other problems. The above means nothing as you didn’t rebuild anything. You have been warned…



I followed the link you gave me but I didn’t find the cause I should look for in the list of possible failures on that page.

Also cannot reconstruct the failing case now. The log file seems to be overwritten.


12