Error resolving _g_cclosure_marshal_VOID__VOID when starting up chirp
Please read in conjunction with 8845, since this is only in the log once the patch there is applied.
When starting up chirp, the application mentioned that it cannot resolve g_cclosure_marshal_VOID_VOID. Please see in attached log line 267 and following.
[2021-02-28 19:22:13,405] chirp.ui.mainapp - ERROR: No MacOS support: dlopen(/private/var/folders/yr/m0c8tjs531123jgh8hsdk9hw0000gn/T/AppTranslocation/E3B679A0-ED20-4510-8363-8271E6875CAB/d/CHIRP-2.app/Contents/Resources/site-packages/gtkosx_application/_gtkosx_application.so, 2): Symbol not found: _g_cclosure_marshal_VOID__VOID Referenced from: /private/var/folders/yr/m0c8tjs531123jgh8hsdk9hw0000gn/T/AppTranslocation/E3B679A0-ED20-4510-8363-8271E6875CAB/d/CHIRP-2.app/Contents/MacOS/../Resources/lib/libgtkmacintegration-gtk2.2.dylib Expected in: /usr/local/opt/gtk+/lib/libgtk-quartz-2.0.0.dylib in /private/var/folders/yr/m0c8tjs531123jgh8hsdk9hw0000gn/T/AppTranslocation/E3B679A0-ED20-4510-8363-8271E6875CAB/d/CHIRP-2.app/Contents/MacOS/../Resources/lib/libgtkmacintegration-gtk2.2.dylib
This might be caused by a recent update through brew. It might also be an issue with Big Sur 11.2. See brew info below:
uwe$ brew info gtk+ gtk+: stable 2.24.33 (bottled), HEAD GUI toolkit https://gtk.org/ /usr/local/Cellar/gtk+/2.24.33 (1,194 files, 60.6MB) * Poured from bottle on 2021-02-03 at 08:11:00 From: https://github.com/Homebrew/homebrew-core/blob/HEAD/Formula/gtk+.rb License: LGPL-2.0-or-later ==> Dependencies Build: gobject-introspection ✔, pkg-config ✔ Required: atk ✔, gdk-pixbuf ✔, hicolor-icon-theme ✔, pango ✔ ==> Options --HEAD Install HEAD version ==> Analytics install: 11,389 (30 days), 38,134 (90 days), 98,221 (365 days) install-on-request: 5,633 (30 days), 19,006 (90 days), 42,852 (365 days) build-error: 0 (30 days)
Updated by Martin Cooper about 2 years ago
Please try the MacOS Unified Application instead of brewing Chirp yourself. Per the download page:
"running CHIRP using Homebrew is obsolete. MacOS Unified Application build is now the recommended way"
The error you are seeing is a result of a mismatch between GTK Mac integration packages. These packages are included in the unified application, so you should no longer encounter this issue.
Also, FYI, #8845 was fixed in the most recent build.