[MacPorts] #69869: kicad @7.0.11: crashes when run (was: KiCad 7.0.11 crashes when run)

[MacPorts]

#69869: kicad @7.0.11: crashes when run
--------------------------+----------------------
  Reporter:  Gamespeople  |      Owner:  ra1nb0w
      Type:  defect       |     Status:  assigned
  Priority:  Normal       |  Milestone:
 Component:  ports        |    Version:  2.9.3
Resolution:               |   Keywords:  catalina
      Port:  kicad        |
--------------------------+----------------------
Changes (by ryandesign):

 * status:  new => assigned
 * keywords:  Kicad crash => catalina
 * version:   => 2.9.3
 * owner:  (none) => ra1nb0w
 * port:  Kicad => kicad


Old description:

> Catalina 10.15.7
>
> Installed fine:
>
> --->  Verifying checksums for kicad\\
> --->  Extracting kicad\\
> --->  Applying patches to kicad\\
> --->  Configuring kicad\\
> --->  Building kicad\\
> --->  Staging kicad into destroot\\
> --->  Installing kicad @7.0.11_0\\
> --->  Activating kicad @7.0.11_0\\
> --->  Cleaning kicad\\
> --->  Updating database of binaries\\
> --->  Scanning binaries for linking errors\\
> --->  No broken files found.\\
> --->  No broken ports found.\\
>
> however when trying to launch KiCad 7.0.11 it crashes when I try to do
> anything past the opening screen.
>
> Is this a Ports problem or a KiCad issue.
>
> I've attached the Apple error report.
> Thanks!

New description:

 Catalina 10.15.7

 Installed fine:

 {{{
 --->  Verifying checksums for kicad
 --->  Extracting kicad
 --->  Applying patches to kicad
 --->  Configuring kicad
 --->  Building kicad
 --->  Staging kicad into destroot
 --->  Installing kicad @7.0.11_0
 --->  Activating kicad @7.0.11_0
 --->  Cleaning kicad
 --->  Updating database of binaries
 --->  Scanning binaries for linking errors
 --->  No broken files found.
 --->  No broken ports found.
 }}}

 however when trying to launch KiCad 7.0.11 it crashes when I try to do
 anything past the opening screen.

 Is this a Ports problem or a KiCad issue.

 I've attached the Apple error report. \\
 Thanks!

--

Comment:

 Hmm. The crash log says:

 {{{
 Crashed Thread:        0  Dispatch queue: com.apple.main-thread
 }}}
 {{{
 Thread 0 Crashed:: Dispatch queue: com.apple.main-thread
 0   org.kicad.kicad                     0x0000000101fe548b
 KIWAY::Player(FRAME_T, bool, wxTopLevelWindow*) + 219
 1   org.kicad.kicad                     0x0000000101e8b5cc
 KICAD_MANAGER_CONTROL::ShowPlayer(TOOL_EVENT const&) + 428
 2   org.kicad.kicad                     0x000000010207d3e1 COROUTINE<int,
 TOOL_EVENT const&>::callerStub(long) + 49
 }}}

 I'm not sure why. I clicked around in the interface a bit and could not
 make it crash on macOS 12.

 The mention of `wx` in the backtrace reminds me that we already know that
 we are not conforming to kicad's requirements by using it with a standard
 copy of wxWidgets. kicad wants us to use their fork of wxWidgets instead.
 I had kinda expected to need to switch to that for the update to kicad 8
 anyway. It seems like a lot of work to need to build it separately so I
 was going to investigate if there is a preferred way to build kicad and
 their fork of wxWidgets and any other custom dependencies all at once in
 the kicad port.

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