[MacPorts] #67797: virt-manager @4.1.0_1+quartz: fails on start with +[NSPlaceholderMutableString initialize] may have been in progress in another thread when fork() was called.

[MacPorts]

#67797: virt-manager @4.1.0_1+quartz: fails on start with
+[NSPlaceholderMutableString initialize] may have been in progress in
another thread when fork() was called.
---------------------------+--------------------
  Reporter:  fabianwenk    |      Owner:  (none)
      Type:  defect        |     Status:  new
  Priority:  Normal        |  Milestone:
 Component:  ports         |    Version:
Resolution:                |   Keywords:
      Port:  virt-manager  |
---------------------------+--------------------
Changes (by ryandesign):

 * cc: mohd-akram (added)


Comment:

 Fabian, what version of macOS are you using and does your Mac use an Intel
 or Apple Silicon processor?

 Mohamed, do you have any ideas? It was your commit that
 [changeset:bb6b0683541bcefce8ff56f92bd67e77596c77c8/macports-ports updated
 virt-manager from 4.1.0_0 to 4.1.0_1].

 Googling this error message, [https://stackoverflow.com/questions/73638290
 /python-on-mac-is-it-safe-to-set-objc-disable-initialize-fork-safety-yes-
 globall it looks like] Apple added this new protection in macOS High
 Sierra and you can disable it by setting
 `OBJC_DISABLE_INITIALIZE_FORK_SAFETY=YES`. I'm not sure what the
 consequence of disabling the protection is nor why this update would have
 caused the protection to suddenly kick in.

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