Bug #9215

MacBook Air OS 11.4 Big Sur - Chirp Crashes without launching (Last two builds, never - worked)

Added by Brian Baldwin 2 months ago. Updated about 1 month ago.

Status:Resolved Start date:07/15/2021
Priority:Normal Due date:
Assignee:- % Done:

0%

Category:-
Target version:chirp-daily
Chirp Version:daily Platform:MacOS
Model affected:Program execution

Description

Installed Python per troubleshooting guide, no help, new Mac, new CHIRP daily build, Windows version runs fine on an old Win 8 laptop

Process: CHIRP [35875]
Path: /private/var/folders/*/CHIRP.app/Contents/MacOS/chirp
Identifier: com.danplanet.chirp
Version: ?
Code Type: X86-64 (Translated)
Parent Process: ?
[1]
Responsible: CHIRP [35875]
User ID: 501

Date/Time: 2021-07-15 20:26:52.752 -0700
OS Version: macOS 11.4 (20F71)
Report Version: 12
Anonymous UUID: BC2E8FF1-D51D-D96D-6AE2-0FFB74B7DCDE

Sleep/Wake UUID: B83F2585-66DF-4DC9-A53D-5606E28B667D

Time Awake Since Boot: 170000 seconds
Time Since Wake: 31000 seconds

System Integrity Protection: enabled

Notes: Translocated Process

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:

VM Regions Near 0 (cr2):
-->
mapped file 1000ee000-1000f0000 [ 8K] r-x/rwx SM=COW Object_id=83068cc3

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: 0x00000003046f07d8 pc: 0x00007ffdffcf122c 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: 0
thread_create: 0
thread_set_state: 0

VM Region Summary:
Writable regions: Total=18.8M written=0K(0%) resident=0K(0%) swapped_out=0K(0%) unallocated=18.8M(100%) =========== ======= =======
STACK GUARD 56.0M 1
Stack 8176K 1
VM_ALLOCATE 10.5M 1
VM_ALLOCATE (reserved) 68K 2 reserved VM address space (unallocated)
mapped file 4.7G 11 =========== ======= =======
TOTAL 4.8G 16
TOTAL, minus reserved VM space 4.8G 16

VIRTUAL   REGION 
REGION TYPE SIZE COUNT (non-coalesced)

Model: MacBookAir10,1, BootROM 6723.120.36, proc 8:4:4 processors, 16 GB, SMC
Graphics: kHW_AppleM1Item, Apple M1, spdisplays_builtin
Memory Module: LPDDR4
AirPort: spairport_wireless_card_type_airport_extreme, wl0: Apr 28 2021 19:53:33 version 18.50.40.7.7.8.119 FWID 01-e6894c69
Bluetooth: Version 8.0.5d7, 3 services, 27 devices, 1 incoming serial ports
Network Service: Wi-Fi, AirPort, en0
USB Device: USB 3.1 Bus
USB Device: USB3.0 Hub
USB Device: USB 10/100/1000 LAN
USB Device: USB2.0 Hub
USB Device: USB Receiver
USB Device: USB 2.0 Hub
USB Device: USB 2.0 BILLBOARD
USB Device: Officejet 5740 series
USB Device: USB 3.1 Bus
USB Device: G-DRIVE mobile USB-C
Thunderbolt Bus: MacBook Air, Apple Inc.
Thunderbolt Bus: MacBook Air, Apple Inc.

History

Updated by Brian Baldwin 2 months ago

Found the problem with the help of a coder. The M1 processor appears to have been contributing to the problem. (?) The OS refused to run even an older version of Chirp. We searched on line and as I suspected, the OS did not like the unsigned app. We "self signed" the app, using the commands below and it ran the Jan. 10th version of Chirp. Downloaded the latest Daily and will try it next.
Do not have the Applications open in Finder!
xattr -c ~/Applications/CHIRP.app
xattr -c ~/Applications/CHIRP.app/Contents
codesign --force --deep --sign - ~/Applications/CHIRP.app

Updated by Bernhard Hailer 2 months ago

  • Status changed from New to Resolved
  • Priority changed from High to Normal
  • Model affected changed from (All models) to Program execution
  • Platform changed from Windows to MacOS

Keeping open (as "Resolved") until we add the solution to the Wiki.

Updated by Brian Baldwin about 1 month ago

Downloaded the "Daily Build" and cannot duplicate the self signing process. I am not a coder.This really sucks!

Updated by Brian Baldwin about 1 month ago

Why can't you just sign the frigging code?

Updated by Brian Baldwin about 1 month ago

My ignorance of using the xttr command line instructions has contributed to the problems I'm having. My work-around is to move Chirp to the Users/brianbaldwin/ folder, execute the xttr commands to self-sign the package, then move it into the applications folder. The program images still reside in the user folder but that is minor compared to not being able to run Chirp.

Also available in: Atom PDF