Can't launch Chrome and other third party apps

[efferto]

Hello

I have an MacBook Pro8,1 and I did a fresh catalina installation with Catalina patcher. However, I cannot launch Chrome after installing the app. Catalina 10.15.5. When I click on the application it doesn't start bouncing on the dock, and after a while I get the following crash. Could it be related to some incompatibility with my Mac? Or it could be related to other issues?

Thanks.

Process:               Google Chrome [823]
Path:                  /Applications/Google Chrome.app/Contents/MacOS/Google Chrome
Identifier:            com.google.Chrome
Version:               ???
Code Type:             X86-64 (Native)
Parent Process:        ??? [1]
Responsible:           Google Chrome [823]
User ID:               501

Date/Time:             2020-10-06 22:56:43.272 +0200
OS Version:            Mac OS X 10.15.5 (19F101)
Report Version:        12
Anonymous UUID:        4C4BC4BD-8393-4136-A338-5A3647109DB2

Time Awake Since Boot: 860 seconds

System Integrity Protection: disabled

Crashed Thread:        0

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):
--> 
    __TEXT                 000000010d220000-000000010d249000 [  164K] r-x/r-x SM=COW  

Thread 0 Crashed:
0                                  0x00000001157e6000 _dyld_start + 0

Thread 0 crashed with X86 Thread State (64-bit):
  rax: 0x0000000000000000  rbx: 0x0000000000000000  rcx: 0x0000000000000000  rdx: 0x0000000000000000
  rdi: 0x0000000000000000  rsi: 0x0000000000000000  rbp: 0x0000000000000000  rsp: 0x00007ffee29dfc38
   r8: 0x0000000000000000   r9: 0x0000000000000000  r10: 0x0000000000000000  r11: 0x0000000000000000
  r12: 0x0000000000000000  r13: 0x0000000000000000  r14: 0x0000000000000000  r15: 0x0000000000000000
  rip: 0x00000001157e6000  rfl: 0x0000000000000200  cr2: 0x0000000000000000

Logical CPU:     0
Error Code:      0x00000000
Trap Number:     0

Binary Images:
       0x10d220000 -        0x10d248ff7 + (0) <A64397FD-BB57-3943-AA84-2ADB91C8D9F5> 
       0x1157e5000 -        0x115876eff + (750.5) <E4698FBD-806A-3396-B279-E685BA37430B> 

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: 686
    thread_create: 0
    thread_set_state: 0

VM Region Summary:
ReadOnly portion of Libraries: Total=1000K resident=0K(0%) swapped_out_or_unallocated=1000K(100%)
Writable regions: Total=8408K written=0K(0%) resident=0K(0%) swapped_out=0K(0%) unallocated=8408K(100%)

                                VIRTUAL   REGION 
REGION TYPE                        SIZE    COUNT (non-coalesced) 
===========                     =======  ======= 
STACK GUARD                       56.0M        1 
Stack                             8192K        1 
__DATA                             232K        4 
__DATA_CONST                        20K        1 
__LINKEDIT                         252K        2 
__TEXT                             748K        2 
shared memory                        8K        2 
===========                     =======  ======= 
TOTAL                             65.2M       13 

Model: MacBookPro8,1, BootROM 87.0.0.0.0, 2 processors, Dual-Core Intel Core i5, 2,4 GHz, 16 GB, SMC 1.68f99
Graphics: kHW_IntelHD3000Item, Intel HD Graphics 3000, spdisplays_builtin
Memory Module: BANK 0/DIMM0, 8 GB, DDR3, 1333 MHz, 0x859B, 0x43543130323436344246313333392E433136
Memory Module: BANK 1/DIMM0, 8 GB, DDR3, 1333 MHz, 0x859B, 0x43543130323436344246313333392E433136
AirPort: spairport_wireless_card_type_airport_extreme (0x14E4, 0xD6), Broadcom BCM43xx 1.0 (5.106.98.102.31)
Bluetooth: Version 7.0.5f6, 3 services, 27 devices, 1 incoming serial ports
Network Service: Wi-Fi, AirPort, en1
Serial ATA Device: Samsung SSD 850 PRO 256GB, 256,06 GB
Serial ATA Device: TOSHIBA MK5065GSXF, 500,11 GB
USB Device: USB 2.0 Bus
USB Device: Hub
USB Device: IR Receiver
USB Device: USB 2.0 Bus
USB Device: FaceTime HD Camera (Built-in)
USB Device: Hub
USB Device: 2.4G Wireless Mouse
USB Device: Apple Internal Keyboard / Trackpad
USB Device: BRCM2070 Hub
USB Device: Bluetooth USB Host Controller
Thunderbolt Bus: MacBook Pro, Apple Inc., 22.1

[jbinder6342]

Had the same issue with Edge... Latest library validation Disabler patch update fixed for me.

[efferto]

Yes, I confirm that the latest library validation Disabler patch fixed this issue and also the crashes when launching Office apps.

[efferto]

Hello,

I'm sorry but the issue is not completely fixed. It is fixed with Chrome, but for some other apps like Word, Office, Powerpoint and Teams the app doesn't launch...but it is random...

[leandroreis]

The same thing is happening to me... :(

[jbinder6342]

I had to reinstall the patch after taking an Edge update and reboot... Then edge ran again... Have't tried it with other apps as this system has a limited set of apps at the time.

[efferto]

Thanks @jbinder6342 , after reinstalling the patch the launch of those application appears to be fixed.

[DBD-001]

I've been looking into this, having some strange anomalies...

• Initially I updated the MacBookPro7,1 using the patcher - Followed all the guide and installed fine (retaining user data) • Setup iCloud and tested all OSX apps - All fine • Chrome, Word, OneDrive, CleanMyMac won't launch (Apps don't even bounce just hang then quit) • Checked Patch Updater - All up to date • Uninstalled apps in question and reinstalled - SOME worked, some didn't • Checked Application Support permissions (common Catalina issue) didn't resolve • Started safe mode from the Patcher disk and reinstalled all the patches - No change • Erased HD and done a clean install of Catalina • Updated Patch Updater • All OSX and the 3rd Party apps I installed (Chrome, Word, Excel etc) work • Restarts and testing seems fine (finally!) • Migration Assitant to transfer user docs from TimeMachine - OSX fell over and needed a restart... • Log back into user account and now SOME apps open (Excel, Chrome) some won't (Word) • It's really intermittent as to what apps will work and when

It's too unreliable to use. I'm contemplating going back to the original OSX or would Mojave be a better option? The whole reason for doing the update is so my wife can use her work OneDrive on the Mac which requires 10.12 Sierra?

[efferto]

Hi, I confirm that it's really intermittent also on my macbook pro. Sometimes Word, Excel works, someother no at all (especially the Office apps have this problem).

[DBD-001]

Hey @fab-bot I've been trying a few all sorts today to get it stable.

I think I might have come across a fix... As the apps (once open) are functioning fine I thought it might be a permissions issue however the clean install with a new user should have resolved any conflicts. Similar to permissions for limiting access is the awful 'Nanny' hidden within System Prefs > Security & Privacy > Privacy

If you scroll down to 'Full Dick Access' I added all the third-party apps that weren't working to this (just use the '+' and selects from the Applications folder.

So far, so good... Time will tell

[DBD-001]

Update

The 'Full Disk Access' helped to get the Apps to launch, they all worked flawlessly for the afternoon/Evening with scheduled restarts for testing. I thought I had it cracked until after a late restart it went back to not launching (the Apps don't even bounce in the dock when it decides not to work)

It seems as though there's something upon startup which blocks them perhaps? If the apps open before the block then they work fine so I thought I'd try and get in before the block... I set Chrome (as it seemed to be the App which fails most) to launch at login

System Prefs > Users & Groups > Login Items

This, along with the Patch Updater launching at login seems to open the gate for the other apps. So far, so good... Time will tell

[rafaelpegadodasilva]

SOLUTION - CHROME AND OFFICE, TERMINAL CODES IN VIDEO DESCRIPTION. https://www.youtube.com/watch?v=NLcRBxmPt8U

[yesnimofu]

Instructions from the video:

• If you can't open certain apps, eg. Word, run this in Terminal: sudo xattr -lr /Applications/Word.app (drag your app to Terminal window after entering sudo xattr -lr and space) sudo xattr -cr /Applications/Word.app sudo codesign -f -s - /Applications/Word.app

[DBD-001]

Thanks for the info @rafaelpegadodasilva and @yesnimofu - The terminal commands seem to have totally put the issues to bed. Would there be a way to globally do this for all apps in the Application folder?

[macklinb]

That solution worked for me, though I'm not certain that it will persist after app updates, plus it requires that you enter your password at every launch (though you can just click "Always Allow").

dosdude1 said that this was addressed in v1.3.6 of the patcher, but it seems to still be an issue in v1.4.4. In the same post he also mentioned that disabling AMFI would solve the issue - and that seems to work just as well. Just do sudo nvram boot-args=amfi_get_out_of_my_way=0x1, then reboot.

[moilejter]

Hmm - disabling AMFI is connected to disabling the security machinery in MacOS. Maybe I am just late to the game :-p - but does this mean that running with the catalina patcher disables some of that already, and this just completes that? (Maybe this was obvious - I just hadn't thought about it :-p)

[macklinb]

@moilejter I think most of these patchers have required disabling some security features in macOS in order to function, whether that's still the case today I can't say.

[chriswayg]

None of the workarounds for the code signing bug are a sufficient solution. I have multiple applications exhibiting this bug with the crash EXC_CRASH (Code Signature Invalid), among them 1Password and coconutBattery.

1) Sometimes its enough to try starting the app multiple times

2) Sometimes it works after starting the app from the terminal with /Applications/1Password 7.app/Contents/MacOS/1Password 7 for example

3) Sometimes the above fixes do not persist

4) The manual signing of the app seems to work in this case:

sudo xattr -lr /Applications/coconutBattery.app
sudo xattr -cr /Applications/coconutBattery.app
sudo codesign -f -s - /Applications/coconutBattery.app

5) Disabling almost all basic security is just not acceptable: sudo nvram boot-args=amfi_get_out_of_my_way=0x1,

Altogether this is a very unsatisfactory situation as the behavior is totally unpredictable, and especially since there are no such issues in Big Sur using OpenCore Legacy Patcher. But I cannot run Big Sur on my MacBook Pro 2010 due to graphics issues which do not occur in Catalina.

The Catalina Patcher has not received any updates for about 2 years and has not been updated for 10.15.7 (Build 19H15) it seems, but the OpenCore Legacy Patcher is not supported for Catalina.

@dosdude1, would it be possible to port the fixes that apparently resolve this issue in the Big Sur OpenCore Legacy Patcher to the Catalina Patcher?

Applications which crash repeatedly

• Adobe Desktop Service
• 1 Password 7 (manually signing breaks the app)
• coconutBattery
• OmniDiskSweeper
• Opera GX (repeatedly fails to start, but no crash in logs)
• BBEdit

System Info for MacBook Pro 2010

OS                             macOS Catalina Version 10.15.7 (Build 19H15)
RAM                            8.00 GB
Model Identifier               MacBookPro6,2
CPU                            Intel(R) Core(TM) i5 CPU       M 520  @ 2.40GHz
GPU Name                       GT216M [GeForce GT 330M]
Catalina Patcher               version 1.4.4

[NeoBlizzard-verbose]

I did a goofy experiment. I dug through the config plist OCLP offers and i noticed a kernel patch that describes itself as "Disable Library Validation Patch". I copied it over to the config plist of my patched Catalina setup, enabled it, changed minKernel to 19.0.0 and it just... works? Please let me know how to check whether this works, and if it does the same work as DisableLibraryValidation next (I'll look into it myself as well, after fixing my wifi)

Speaking of that, I would also like to know how to check whether the "sudo defaults write..." command stated here works, as I see no such plist on L/P and reading defaults via the terminal and narrowing it to this specific plist using grep shows no results, as well :/

[tejasraman]

@riglaze I already tried this. It messes up Apple Music the same way that disableLibraryValidation.kext does.

The plist exists for me so...

[NeoBlizzard-verbose]

@riglaze I already tried this. It messes up Apple Music the same way that disableLibraryValidation.kext does.

The plist exists for me so...

I see... Weird how I don't have the com.apple.security.libraryvalidation.plist, even though I'm on the latest Catalina build. I did reapply the patch from Patch Updater many times, but no profit. Also, did you see this? https://github.com/dortania/OpenCore-Legacy-Patcher/issues/739#issuecomment-971906016 I wonder if there is more to be done along with the kernel patch... https://github.com/dortania/OpenCore-Legacy-Patcher/blob/main/resources/defaults.py#L15-L16

EDIT:- can confirm, Music crashes :/ EDIT2:- Could you also please send me your com.apple.security.libraryvalidation.plist? I wonder if pasting it in the right path fixes my headache lol. While you are at it, let me know your output when you run sudo defaults read | grep com.apple.security.libraryvalidation and attach the output here? Thanks a ton in advance :)

[tejasraman]

That plist doesn't fix the issue FYI @riglaze

[NeoBlizzard-verbose]

goofy 2

so, y'all know how catalina and mojave produce pop-ups when the system reboots unexpectedly or crashes, right? i dug that error of mine and realized that the error shows two boot args not present in my nvram. this blew my mind, as one of them was amfi_allow_any_signature=1

i added it to my config plist's nvram section, cleaned kextcache and did a dozen reboots and in the past 24 hrs, faced zero issues with app crashes. With this, I suspect that library validation is being disabled/patched for good but amfi is to blame. the other command was -no_compat_check jfyi, but ig amfi_allow_any_signature=1 is worth trying as a boot arg? again, it could be a huge coincidence or a simple kext cache rebuild that could have fixed my issue, and idk how (and if) security is compromised as well...

[tejasraman]

@riglaze AMFI is essential security. That arg is NOT supposed to be there by default, and it breaks permissions for camera, mic, etc.

Honestly I would recommend OCLP at this point because these issues don't exist and all these issues are resolved.

By the way, there was a kext called CSLVFixup.kext (which OCLP has for Big Sur specifically as the issue doesn't exist on Monterey) that was supposed to patch Music.app on boot... But it only works on Big Sur for me, and the patcher dev said the same

See #200 (also see my post on #196 for context)

[NeoBlizzard-verbose]

@riglaze AMFI is essential security. That arg is NOT supposed to be there by default, and it breaks permissions for camera, mic, etc.

That's the reason why i removed get_out_of_my_way in the first place. allow_any_signature doesn't break permissions (at least didn't, for me :)) If my understanding is correct, i'm pretty sure 'allow_any_signature' is supposed to be applied as a boot-arg when installing the library validation patch but is unable to?

Honestly I would recommend OCLP at this point because these issues don't exist and all these issues are resolved.

By the way, there was a kext called CSLVFixup.kext (which OCLP has for Big Sur specifically as the issue doesn't exist on Monterey) that was supposed to patch Music.app on boot... But it only works on Big Sur for me, and the patcher dev said the same See #200 (also see my post on #196 for context)

I am aware of cslvfixup kext as well as OCLP but having a non-metal graphics card sucks. BS and above rely heavily on the Metal API and even though there are acceleration patches, i just want to use Catalina for as long as my hackintosh lives 😅

[tejasraman]

I'll have to test this myself once I get home. This is great news for some Macs I am dealing with :D

[tejasraman]

I've forgotten how the sip and LV patches work, so I'll check later.

[tejasraman]

Also, it seems like you're not using this patcher, but an OC config.... Which Mac model are you patching?

[Pigeo]

For Chrome / Edge / Chromium, there's another specific issue on top of that, see https://github.com/dosdude1/macos-catalina-patcher/issues/237: recent versions of Chrome / Edge / Chromium (e.g. versions 118 and 120) are not compatible with Catalina Patcher, so you need to block Chrome / Edge / Chromium updates and stay on an older version (for instance, version 111 is working).

After having downgraded Chrome / Edge / Chromium, you'll need to run this commands again from the Terminal:

sudo xattr -lr /Applications/Google\ Chrome.app
sudo xattr -cr /Applications/Google\ Chrome.app
sudo codesign -f -s - /Applications/Google\ Chrome.app

You can download older versions of Chrome here for instance : https://google-chrome.en.uptodown.com/mac/versions