Bug #8639

Mac M1 Chip

Added by Robert Aucoin 10 months ago. Updated about 1 month ago.

Status:Feedback Start date:01/02/2021
Priority:Normal Due date:
Assignee:- % Done:

0%

Category:-
Target version:-
Chirp Version:daily Platform:MacOS
Model affected:(All models)

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.

Capture d’écran 2021-03-03 à 21.37.46.png (194.4 kB) Elie Rebetez, 03/03/2021 12:38 pm


Related issues

related to Bug #8749: App crashes on launch on Apple Silicon M1 Mac running mac... Closed 01/28/2021
duplicated by Bug #8595: CHIRP MacOS Big Sur v.11.1 Puce Apple M1 Closed 12/26/2020
duplicated by Feature #8469: Support for Apple's new M1 System on a Chip Architecture Closed 11/23/2020
duplicated by Bug #9155: chirp does not work on mac m1 Closed 06/24/2021

History

Updated by Elie Rebetez 10 months ago

same for me

Updated by Erik Rogers 10 months 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 10 months 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 Bernhard Hailer 9 months ago

  • Status changed from New to Closed

Solution suggested.

Updated by Brian Jalet 9 months ago

I attempted this approach, and it didn't work for me. :-(

Updated by Bernhard Hailer 9 months 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. Perhaps someone finds a solution which works indeed.
Let us know here!

Updated by Colin Lord 9 months 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 8 months 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 8 months 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: 501

Date/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-78A97B577082

Time 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_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: 0x000000030a106a60 pc: 0x00007ffdffe1ac0c 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: 4461
thread_create: 0
thread_set_state: 0

Updated by Sebastien Lesieur 8 months 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 8 months 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 8 months 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 8 months 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 6 months 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 3 months 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 3 months ago

Should add, MacOS 11.4 on Macbook Air M1.

Updated by Scott Lopez 3 months 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 about 1 month ago

Still working on 11.5.2, with running those commands from a terminal.

Also available in: Atom PDF