Bug #8639
closedMac M1 Chip
0%
Description
I have 2 MacBooks. One with intel chip; the other with new M1 chip.
Chirp works with the MacBook with intel chip.
Chirp crashes immediately on the MacBook with M1 chip.
Is the issue the M1 chip or something else.
Files
Updated by Erik Rogers almost 4 years ago
Also for me on a new M1 Mac mini (2020):
Process: CHIRP [1057] Path: /Applications/CHIRP.app/Contents/MacOS/chirp Identifier: com.danplanet.chirp Version: ??? Code Type: X86-64 (Translated) Parent Process: ??? [1] Responsible: CHIRP [1057] User ID: 501 Date/Time: 2021-01-03 01:35:31.896 -0500 OS Version: macOS 11.1 (20C69) Report Version: 12 Anonymous UUID: 047503EE-3C3F-3786-F6E2-B24D8A87C23D Time Awake Since Boot: 6800 seconds System Integrity Protection: enabled Crashed Thread: Unknown Exception Type: EXC_CRASH (Code Signature Invalid) Exception Codes: 0x0000000000000000, 0x0000000000000000 Exception Note: EXC_CORPSE_NOTIFY Termination Reason: Namespace CODESIGNING, Code 0x1 kernel messages: Backtrace not available Unknown thread crashed with ARM Thread State (64-bit): x0: 0x0000000000000000 x1: 0x0000000000000000 x2: 0x0000000000000000 x3: 0x0000000000000000 x4: 0x0000000000000000 x5: 0x0000000000000000 x6: 0x0000000000000000 x7: 0x0000000000000000 x8: 0x0000000000000000 x9: 0x0000000000000000 x10: 0x0000000000000000 x11: 0x0000000000000000 x12: 0x0000000000000000 x13: 0x0000000000000000 x14: 0x0000000000000000 x15: 0x0000000000000000 x16: 0x0000000000000000 x17: 0x0000000000000000 x18: 0x0000000000000000 x19: 0x0000000000000000 x20: 0x0000000000000000 x21: 0x0000000000000000 x22: 0x0000000000000000 x23: 0x0000000000000000 x24: 0x0000000000000000 x25: 0x0000000000000000 x26: 0x0000000000000000 x27: 0x0000000000000000 x28: 0x0000000000000000 fp: 0x0000000000000000 lr: 0x0000000000000000 sp: 0x00000003098e4a68 pc: 0x00007ffdffb7e46c cpsr: 0x00000000 far: 0x0000000000000000 esr: 0x00000000 Binary images description not available External Modification Summary: Calls made by other processes targeting this process: task_for_pid: 0 thread_create: 0 thread_set_state: 0 Calls made by this process: task_for_pid: 0 thread_create: 0 thread_set_state: 0 Calls made by all processes on this machine: task_for_pid: 4291 thread_create: 0 thread_set_state: 0 Model: Macmini9,1, BootROM 6723.61.3, proc 8:4:4 processors, 16 GB, SMC Graphics: kHW_AppleM1Item, Apple M1, spdisplays_builtin Memory Module: lp_ddr4 AirPort: spairport_wireless_card_type_airport_extreme, wl0: Oct 20 2020 12:49:54 version 18.20.222.14.7.8.100 FWID 01-ba327c2d Bluetooth: Version 8.0.2f9, 3 services, 27 devices, 1 incoming serial ports Network Service: Wi-Fi, AirPort, en1 USB Device: USB 3.1 Bus USB Device: USB 3.1 Bus USB Device: Cable Matters USB-C Video Cable USB Device: USB 3.0 Bus USB Device: USB Receiver Thunderbolt Bus: Mac mini, Apple Inc., 0.0 Thunderbolt Bus: Mac mini, Apple Inc., 0.0
Looks like a code-signing issue. Perhaps the binary needs to be re-built with signing? I don't mind taking a look at the code as I'm a developer.
Updated by Erik Rogers almost 4 years ago
Did a little digging and seems this is one way to fix it, by signing the app yourself:
Open a terminal and perform the following:
xcode-select --install codesign --force --deep --sign - /Applications/CHIRP.app
The first installs the Xcode command line tools needed, the second will sign the application and allow you to run it on your local machine.
Updated by Brian Jalet almost 4 years ago
I attempted this approach, and it didn't work for me. :-(
Updated by Bernhard Hailer almost 4 years ago
- Status changed from Closed to Feedback
- Platform changed from Windows to MacOS
Reopening.
Please provide more information about how it doesn't work (details such as error messages etc.).
Please also discuss this on the "mailing list":http://intrepid.danplanet.com/mailman/listinfo/chirp_users. Perhaps someone finds a solution which works indeed.
Let us know here!
Updated by Colin Lord almost 4 years ago
Erik Rogers wrote:
Did a little digging and seems this is one way to fix it, by signing the app yourself:
Open a terminal and perform the following:
[...]The first installs the Xcode command line tools needed, the second will sign the application and allow you to run it on your local machine.
Signing the application using the Terminal commands above solved the issue for me on my M1.
Updated by Brian Fox almost 4 years ago
I also tried the steps above without resolution:
First command "xcode-select --install"
Gave this message:
xcode-select: error: command line tools are already installed, use "Software Update" to install updates
Trying the second command: "codesign --force --deep --sign - /Applications/CHIRP.app" gave the following error:
xcrun: error: unable to load libxcrun (dlopen(/Library/Developer/CommandLineTools/usr/lib/libxcrun.dylib, 0x0005): could not use '/Library/Developer/CommandLineTools/usr/lib/libxcrun.dylib' because it is not a compatible arch).
/Applications/CHIRP.app: the codesign_allocate helper tool cannot be found or used
In subcomponent: /Applications/CHIRP.app/Contents/CHIRP
Updated by Brian Fox almost 4 years ago
CHIRP quits unexpectedly on launch. With error:
Click Report to see more detailed information and send a report to Apple.
Process: CHIRP [15199]
Path: /Applications/CHIRP.app/Contents/MacOS/chirp
Identifier: com.danplanet.chirp
Version: ???
Code Type: X86-64 (Translated)
Parent Process: ??? [1]
Responsible: CHIRP [15199]
User ID: 501Date/Time: 2021-02-15 12:06:04.754 -0800
OS Version: macOS 11.2.1 (20D74)
Report Version: 12
Anonymous UUID: 9F88A4B5-31E6-497F-6F22-78A97B577082Time Awake Since Boot: 5200 seconds
System Integrity Protection: enabled
Crashed Thread: Unknown
Exception Type: EXC_CRASH (Code Signature Invalid)
Exception Codes: 0x0000000000000000, 0x0000000000000000
Exception Note: EXC_CORPSE_NOTIFYTermination Reason: Namespace CODESIGNING, Code 0x1
kernel messages:
Backtrace not available
Unknown thread crashed with ARM Thread State (64-bit):
x0: 0x0000000000000000 x1: 0x0000000000000000 x2: 0x0000000000000000 x3: 0x0000000000000000
x4: 0x0000000000000000 x5: 0x0000000000000000 x6: 0x0000000000000000 x7: 0x0000000000000000
x8: 0x0000000000000000 x9: 0x0000000000000000 x10: 0x0000000000000000 x11: 0x0000000000000000
x12: 0x0000000000000000 x13: 0x0000000000000000 x14: 0x0000000000000000 x15: 0x0000000000000000
x16: 0x0000000000000000 x17: 0x0000000000000000 x18: 0x0000000000000000 x19: 0x0000000000000000
x20: 0x0000000000000000 x21: 0x0000000000000000 x22: 0x0000000000000000 x23: 0x0000000000000000
x24: 0x0000000000000000 x25: 0x0000000000000000 x26: 0x0000000000000000 x27: 0x0000000000000000
x28: 0x0000000000000000 fp: 0x0000000000000000 lr: 0x0000000000000000
sp: 0x000000030a106a60 pc: 0x00007ffdffe1ac0c cpsr: 0x00000000
far: 0x0000000000000000 esr: 0x00000000Binary images description not available
External Modification Summary:
Calls made by other processes targeting this process:
task_for_pid: 0
thread_create: 0
thread_set_state: 0
Calls made by this process:
task_for_pid: 0
thread_create: 0
thread_set_state: 0
Calls made by all processes on this machine:
task_for_pid: 4461
thread_create: 0
thread_set_state: 0
Updated by Sebastien Lesieur almost 4 years ago
Erik Rogers wrote:
Did a little digging and seems this is one way to fix it, by signing the app yourself:
Open a terminal and perform the following:
[...]The first installs the Xcode command line tools needed, the second will sign the application and allow you to run it on your local machine.
Everything works fine with this solution.
Thanks a lot man !!
One question, I can just remove Xcode command line tools by deleting Library/Developer/CommandLineTools folder ?
Every Gb counts in a 256Gb SSD... _^
Updated by Sebastien Lesieur almost 4 years ago
Erik Rogers wrote:
Did a little digging and seems this is one way to fix it, by signing the app yourself:
Open a terminal and perform the following:
[...]The first installs the Xcode command line tools needed, the second will sign the application and allow you to run it on your local machine.
Everything works fine with this solution on my M1 MacBook Air.
Thanks a lot man !!
One question, I can just remove Xcode command line tools by deleting Library/Developer/CommandLineTools folder ?
Every Gb counts in a 256Gb SSD... _^
Updated by Brian Fox almost 4 years ago
Thanks to Sebastien above, I re-read my error message when trying to sign app package, and realized that my Command Line Dev tools were likely migrated from my old Intel machine. So I deleted the /Library/Developer/CommandLineTools folder, and then re-tried the above mentioned work around:
@xcode-select --install
codesign --force --deep --sign - /Applications/CHIRP.app@
And it all worked well. Chirp now launches again for me. Thanks!
Updated by Elie Rebetez almost 4 years ago
for me it does not work, I still cannot access certain part of my disk, such as the desktop or my documents, on the other hand I have access to my image folder for example
Updated by Aaron Jarnigan over 3 years ago
Hello everyone, I have been struggling to get chirp running following the terminal commands as suggested by Erik Rogers on my Mac Mini M1. After sometime of dabbling around I would like to share that you must make sure you have the installer package in "applications" and not on your desktop to make the terminal code work. The code looks for the program in Applications and with me having the installer folder on my desktop, it could not be located.
Updated by Scott Lopez over 3 years ago
❯ cd /Applications ❯ codesign --force --deep --sign - /Applications/CHIRP.app /Applications/CHIRP.app: resource fork, Finder information, or similar detritus not allowed
This work-around no longer appears to work.
Updated by Scott Lopez over 3 years ago
Should add, MacOS 11.4 on Macbook Air M1.
Updated by Scott Lopez over 3 years ago
I got it working on MacOS 11.4 on my Macbook Air M1. Here's what I did:
- Copy CHIRP.app to ~/Applications
- Run the following from Terminal:
xattr -c ~/Applications/CHIRP.app xattr -c ~/Applications/CHIRP.app/Contents codesign --force --deep --sign - ~/Applications/CHIRP.app
Updated by Scott Lopez over 3 years ago
Still working on 11.5.2, with running those commands from a terminal.
Updated by Brian Jalet about 3 years ago
Still not working for me, after following every instruction above. I am on 12.1 Monterey, so I know I'm bleeding edge. But this was still the case on earlier OS versions. Macbook Air M1.
Updated by Scott Lopez about 3 years ago
The instructions I gave still work for me, on a MBA M1, running 12.1 as well. Can you please provide some diagnostic information as to what is wrong?
Updated by Brian Jalet about 3 years ago
Thanks for the response. I should know this, but can you tell me how to sow the diagnostic information? Forgive me if this is readily available information.
Updated by Brian Jalet about 3 years ago
I'm sorry, I should also probably state that for whatever reason, I cannot find the debug log where it the instructions state it should be hiding. What I get...
Last login: Thu Nov 11 16:17:25 on ttys000
name@computer ~ % cp ~/.chirp/debug.log ~/Desktop
cp: /Users/name/.chirp/debug.log: No such file or directory
name@computer ~ %
Updated by Brian Jalet about 3 years ago
In fact, I can't even find the ~/.chirp directory at all. Confused....Thanks again for any help you can provide.
Updated by Brian Jalet about 3 years ago
Ok, sorry for all the noise from me here. I ran chirp.app while holding the
[2021-11-11 16:42:02,622] chirp.ui.mainapp - WARNING: Icon not found
/Applications/CHIRP.app/Contents/Resources/chirp/chirp/ui/mainapp.py:2245: Warning: invalid cast from 'GtkMenuBar' to 'GtkWindow'
macapp.set_menu_bar(menu_bar)
/Applications/CHIRP.app/Contents/Resources/chirp/chirp/ui/mainapp.py:2245: GtkWarning: gtk_window_add_accel_group: assertion 'GTK_IS_WINDOW (window)' failed
macapp.set_menu_bar(menu_bar)
[2021-11-11 16:42:02,715] chirp.ui.mainapp - DEBUG: Initialized MacOS support
/Applications/CHIRP.app/Contents/Resources/chirp/chirp/ui/mainapp.py:2331: GtkWarning: Cannot open pixbuf loader module file '/usr/local/lib/gdk-pixbuf-2.0/2.10.0/loaders.cache': No such file or directory
This likely means that your installation is broken.
Try running the command
gdk-pixbuf-query-loaders > /usr/local/lib/gdk-pixbuf-2.0/2.10.0/loaders.cache
to make things work again for the time being.
d.run()
[2021-11-11 16:42:06,911] chirp.ui.mainapp - DEBUG: Copying /Applications/CHIRP.app/Contents/Resources/chirp/stock_configs/DE Freenet Frequencies.csv -> /Users/bigbluebottle/.chirp/stock_configs
[2021-11-11 16:42:06,912] chirp.ui.mainapp - DEBUG: Copying /Applications/CHIRP.app/Contents/Resources/chirp/stock_configs/US 60 meter channels (Center).csv -> /Users/bigbluebottle/.chirp/stock_configs
[2021-11-11 16:42:06,913] chirp.ui.mainapp - DEBUG: Copying /Applications/CHIRP.app/Contents/Resources/chirp/stock_configs/US FRS and GMRS Channels.csv -> /Users/bigbluebottle/.chirp/stock_configs
[2021-11-11 16:42:06,914] chirp.ui.mainapp - DEBUG: Copying /Applications/CHIRP.app/Contents/Resources/chirp/stock_configs/US 60 meter channels (Dial).csv -> /Users/bigbluebottle/.chirp/stock_configs
[2021-11-11 16:42:06,914] chirp.ui.mainapp - DEBUG: Copying /Applications/CHIRP.app/Contents/Resources/chirp/stock_configs/UK Business Radio Simple Light Frequencies.csv -> /Users/bigbluebottle/.chirp/stock_configs
[2021-11-11 16:42:06,915] chirp.ui.mainapp - DEBUG: Copying /Applications/CHIRP.app/Contents/Resources/chirp/stock_configs/US CA Railroad Channels.csv -> /Users/bigbluebottle/.chirp/stock_configs
[2021-11-11 16:42:06,916] chirp.ui.mainapp - DEBUG: Copying /Applications/CHIRP.app/Contents/Resources/chirp/stock_configs/NOAA Weather Alert.csv -> /Users/bigbluebottle/.chirp/stock_configs
[2021-11-11 16:42:06,916] chirp.ui.mainapp - DEBUG: Copying /Applications/CHIRP.app/Contents/Resources/chirp/stock_configs/EU LPD and PMR Channels.csv -> /Users/bigbluebottle/.chirp/stock_configs
[2021-11-11 16:42:06,917] chirp.ui.mainapp - DEBUG: Copying /Applications/CHIRP.app/Contents/Resources/chirp/stock_configs/US MURS Channels.csv -> /Users/bigbluebottle/.chirp/stock_configs
[2021-11-11 16:42:06,917] chirp.ui.mainapp - DEBUG: Copying /Applications/CHIRP.app/Contents/Resources/chirp/stock_configs/US Marine VHF Channels.csv -> /Users/bigbluebottle/.chirp/stock_configs
[2021-11-11 16:42:06,918] chirp.ui.mainapp - DEBUG: Copying /Applications/CHIRP.app/Contents/Resources/chirp/stock_configs/US Calling Frequencies.csv -> /Users/bigbluebottle/.chirp/stock_configs
[2021-11-11 16:42:06,918] chirp.ui.mainapp - DEBUG: Copying /Applications/CHIRP.app/Contents/Resources/chirp/stock_configs/FR Marine VHF Channels.csv -> /Users/bigbluebottle/.chirp/stock_configs
[2021-11-11 16:42:06,919] chirp.ui.mainapp - DEBUG: Copying /Applications/CHIRP.app/Contents/Resources/chirp/stock_configs/KDR444.csv -> /Users/bigbluebottle/.chirp/stock_configs
[2021-11-11 16:42:06,921] chirp.ui.reporting - DEBUG: Checking for updates
[2021-11-11 16:42:07,121] chirp.ui.reporting - DEBUG: Server reports version daily-20211105 is latest
So it looks like I'm getting somewhere. I just don't know what this all means.
Updated by Brian Jalet about 3 years ago
Oddly, when loaded in "Error Reporting Mode, I was able to connect and download my config from my Baofeng UV-5R. But it simply won't run without being in Error Reporting mode.
Updated by Scott Lopez about 3 years ago
Ok, my instructions earlier assume you're copying it to the Applications directory in your user directory (~/Applications). If you are copying it to the system Applications directory then use the following:
@xattr -c /Applications/CHIRP.app
xattr -c /Applications/CHIRP.app/Contents
codesign --force --deep --sign - /Applications/CHIRP.app@
I generally try to avoid modifying things in /Applications directly.
You will need to run these commands any time you update the application.
Updated by Alastair Bor about 3 years ago
The instructions posted by Scott Lopez (#26) work perfectly on M1. This info should be added to the macOS FAQ page if it's not able to be resolved in future releases.
Updated by Alastair Bor about 3 years ago
Alastair Bor wrote:
The instructions posted by Scott Lopez (https://chirp.danplanet.com/issues/8639#note-26) work perfectly on M1. This info should be added to the macOS FAQ page if it's not able to be resolved in future releases.
Updated by Bernhard Hailer almost 3 years ago
- Status changed from Feedback to Closed
- Model affected changed from (All models) to M1 chip
It looks like this issue has been resolved (see Scott Lopez' comments - thank you!).
Updated by Stephen Grosch over 2 years ago
#26 did it!!!
I have been trying for a year to get this working!
Just ran every line 1 at a time, and downloaded the python package before, not sure if it also helped, but did both and now it is working. here-https://chirp.danplanet.com/projects/chirp/wiki/MacOS_Tips
Thank you Scott!