I have installed Safari 13, and do not intend to try the Supplemental Update (safari 14) update. I really did not expect that to work, given the developer's letter in my post above, but to my surprise, cDock is working! Obviously, the order of installation is the key. Update: I used CCC to backup this working cDock system, and then ran the 005 security update again as you did.
#Lockrattler free#
That app SilentKnight is awesome, as are the other free apps at Running SilentKnight 1.1.1 I got a couple of updates using the File menu "Install named updates" function (just copy and paste the name from the text in the suggested updates section after SilentKnight runs its checks. I did a reinstall of Mojave, and stopped after running Security Update 004. What version of cDock do you have installed and working?Ĭlick to expand.Yes, the standard Dock is an ugly Dockling! I tried that "final option which is semi-complex", but it was a no go. It's good that it works for you! But I cannot get it working. So, I wonder why you have cDock working with Mojave. >It’s possible we will release a patcher that can apply the fix detailed
#Lockrattler install#
>cDock will work on 10.14 if you do not install the latest security patch (which the majority of users are running) >The same issue isn’t present in the same security patch for 10.15 or the >another update no fixes will come for cDock. >Unfortunately unless a fix is made by someone else or Apple releases >Lock /Library/Application Support/MacEnhance/Plugins/cDock.bundle (to >Contents (not the main bundle, just the contents)
>Library/Application Support/SIMBL/Plugins/cDock.bundle >Copy /Library/Application Support/MacEnhance/Plugins/cDock.bundle to / There is a final option which is semi-complex if you want to keep using cDock and can’t update but also refuse to not install the security patch: Stop using cDock (and/or MacForge) and delete this folder /Library/ Reinstall Mojave and then do not installģ.
#Lockrattler code#
This is a generic email going out as a response to many people who have contacted us regarding Security Update 2020-005 Mojave Īs you have probably already noticed cDock and MacForge are broken with this update.Īfter some investigation this issue appears to be something we're unlikely to be able to fix.įor an explanation of what’s happening: cDock and MacForge use mach_inject to load code into the Dock processĪfter the security update any process being injected into using mach_inject immediately crashes.ġ. According to the mail I got from the developer of cDock: I did do a reinstall of Mojave, overwrite of my present system, and later did those 2 updates, but I can't remember the order, what with having done the ones that were later replaced. Yes, fixes in some applications helped to avoid those crashes, but user-space application should NEVER be able to crash system processes!Ĭlick to expand.What version of cDock do you have installed and working? This is obviously a bug in tccd, since it should check for invalid or NULL pointers by itself and avoid calling system functions with invalid arguments. Since tccd is an important system process, whole system freezes until this process is recovered. Tccd: (CoreFoundation) *** Terminating app due to uncaught exception 'NSInvalidArgumentException', reason: '*** -: nil or empty path argument' So instead of the above non-fatal error, we're now getting a crash in tccd: Tccd: From PID: realPath of reponsible path () fails: open() for F_GETPATH failed.īut starting with Security update 2020-004 (and continuing with 2020-005), Mojave forcibly crashes processes, which pass invalid or NULL pointer to some system functions. Mojave 10.14.6 with older Security update 2020-003 just printed the following error into system log, when a buggy application requested access to non-existent or protected file: There are still some applications, which trigger these freezes for 100 seconds and it's not the application's fault, but apparently a (still undiscovered) bug in tccd.
OS freezes with Mojave + Security update 2020-005 are far from fixed.
0 kommentar(er)
