[MacPorts] #70891: at-spi2-core: Since upgrade to 2.44.1_0 dbind-WARNING messages.

[MacPorts]

#70891: at-spi2-core: Since upgrade to 2.44.1_0 dbind-WARNING messages.
----------------------------+----------------------
  Reporter:  christophecvr  |      Owner:  mascguy
      Type:  defect         |     Status:  assigned
  Priority:  Normal         |  Milestone:
 Component:  ports          |    Version:  2.9.99
Resolution:                 |   Keywords:
      Port:  at-spi2-core   |
----------------------------+----------------------

Comment (by christophecvr):

 Found the real problem why the message :


 {{{
 (gedit:511): dbind-WARNING **: 08:49:23.882: Couldn't connect to
 accessibility bus: Empty address ''
 }}}

 Shows up when starting gedit after upgraded at-spi-core.

 The at-spi-bus-launcher can not start due to wrong linking.

 {{{
 /opt/local/libexec/at-spi-bus-launcher --launch-immediately &
 [1] 1656
 MacBookProCvr:libexec christophe$ dbus-daemon[1658]: Failed to start
 message bus: Failed to bind socket "/Users/christophe/.cache/at-
 spi/bus/private/tmp/com.apple.launchd.Sz9Mu7FV6T/org.macports_0": No such
 file or directory
 Failed to launch bus: Bus exited with code 1
 }}}

 the socket is made and loaded at start the location is :


 {{{
 /private/tmp/com.apple.launchd.Sz9Mu7FV6T
 }}}

 A temporary workaround can be made by placing a link to tmp in you're home
 map.


 {{{
 cd ~
 cd .cache/at-spi
 mkdir bus
 cd bus
 mkdir private
 cd private
 ln -s /private/tmp tmp
 }}}

 after this login logout or restart you're mac

 p.s. if export NO_AT_BRIDGE=1 is set to you're profile or bash_profile
 remove it again.

-- 
Ticket URL: <https://trac.macports.org/ticket/70891#comment:12>
MacPorts <https://www.macports.org/>
Ports system for macOS