As far as downloading updates, same here. (Not that I can think of other serious problems...)
Got a tip for us?
Let us know
Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
Security Update 2020-005
- Thread starter Earl Urley
- Start date
- Sort by reaction score
I wound up throwing caution to the wind (after a good updated clone backup, that is) and doing the updates via Software Update a few days ago, and all is well!
As a matter of fact, since I have Turbo Boost Switcher Pro installed, I keep a close eye on my CPU temperature at all times...and since doing these updates I'm noticing my MBP running at least 5 degrees cooler on average when running Avid Pro Tools. It had been hovering around 55-56 degrees Celsius previously, and the past few days it's been at or under 50. Nice perk.
As a matter of fact, since I have Turbo Boost Switcher Pro installed, I keep a close eye on my CPU temperature at all times...and since doing these updates I'm noticing my MBP running at least 5 degrees cooler on average when running Avid Pro Tools. It had been hovering around 55-56 degrees Celsius previously, and the past few days it's been at or under 50. Nice perk.
I first posted this question in another thread, perhaps one that you do not watch so often, as there has been no answer.
So once again, "Did you actually get cDock working after that Apple induced one-week horror show?
What version are you using? I have a valid license for version 3, but not for version 4.
I tried cDock 4.15 once after the episode, and while it doesn't crash, it does not display any of the themes or other visual enhancements."
Last edited:
OS freezes with Mojave + Security update 2020-005 are far from fixed. 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.
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:
tccd: [com.apple.TCC:access] From PID[66174]: realPath of reponsible path () fails: open() for F_GETPATH failed.
But 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. So instead of the above non-fatal error, we're now getting a crash in tccd:
tccd: (CoreFoundation) *** Terminating app due to uncaught exception 'NSInvalidArgumentException', reason: '*** -[NSFileManager fileSystemRepresentationWithPath:]: nil or empty path argument'
Since tccd is an important system process, whole system freezes until this process is recovered.
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.
Yes, fixes in some applications helped to avoid those crashes, but user-space application should NEVER be able to crash system processes!
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:
tccd: [com.apple.TCC:access] From PID[66174]: realPath of reponsible path () fails: open() for F_GETPATH failed.
But 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. So instead of the above non-fatal error, we're now getting a crash in tccd:
tccd: (CoreFoundation) *** Terminating app due to uncaught exception 'NSInvalidArgumentException', reason: '*** -[NSFileManager fileSystemRepresentationWithPath:]: nil or empty path argument'
Since tccd is an important system process, whole system freezes until this process is recovered.
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.
Yes, fixes in some applications helped to avoid those crashes, but user-space application should NEVER be able to crash system processes!
If there are any of you, like me, who had no idea of what the last post was about, there is a very clear description of Transparency Consent and Control (TCC) here:
eclecticlight.co
Watching Mojave’s privacy protection at work
TCC observed loading overrides during startup, and two typical sequences responding to access requests. Useful tips for fixing problems.
eclecticlight.co
We got the fault back on the Mini of constantly waking from sleep and found that is was Safari that was the problem. We usually use Firefox on the Mini but were trying another browser because of a problem with Firefox. After we closed Safari down, the wake from sleep problem disappeared again. Fortunately, we prefer Firefox on the Mini and solved the problem with that with a refresh!
For example Microsoft Autoupdate (from Office for MAC) triggered tccd crash yesterday. Virtual keyboard asking for smartcard PIN is another example.
And Dropbox - see here: https://forums.macrumors.com/thread...04.2246032/page-3?post=28970745#post-28970745
You might try resetting tcc: https://eclecticlight.co/2020/01/28/a-guide-to-catalinas-privacy-protection-4-tccutil/
Try using SilentKnight to make sure you have the latest xprotect, etc.
SilentKnight, Skint, silnite, LockRattler, SystHist & Scrub
Skint – a watchful eye on security settings Updated! Checks key security settings and features including SIP, SSV, Gatekeeper, XProtect, XProtect Remediator and macOS security updates. Runs a…
eclecticlight.co
@Mr_Brightside_@ gave the solution for this and it worked like a charm:
https://forums.macrumors.com/thread...ed.2258119/page-7?post=28979200#post-28979200
@davidlv : is your CDock malfunction resolved?Try using SilentKnight to make sure you have the latest xprotect, etc.
I do not know about the App Store ....SilentKnight, Skint, silnite, LockRattler, SystHist & Scrub
Skint – a watchful eye on security settings Updated! Checks key security settings and features including SIP, SSV, Gatekeeper, XProtect, XProtect Remediator and macOS security updates. Runs a…
No, cDock refuses to work on my Mojave and my High Sierra systems, iMac 2012 and MBP 2011 respectively.
I have installed the security update 005 on both systems and the supplemental update (Safari) on the Mojave system. I don't use Safari, but it is there for the rare occasion that Firefox won't work.
I have a license for cDock 3.1.2, but it crashes immediately on restart, flashing the Dock on and off. Removing the launch Daemons with "Wolf" in the anme, that is, in the main Library, is the only way I have found to get back to normal. Version 4.15 doesn't crash but it refuses to show any theme and none of the other functions work, like coloring the Dock divider. I got very used to having the Transparent Dock, and now the stock grey Dock is rather an eye-sore.
Did you get it working?
I got a letter from the developer saying he can't do anything on Mojave, and suggested upgrading to Catalina, which I am very reluctant to do, as I use several 32 bit apps constantly.
I answered your PM a couple of weeks ago I think... Yes, works fine here on two iMacs with latest Mojave updates.
You did try a complete reinstall of 10.14.6 on top followed by 2020-005 and Supplemental Update?
What version of cDock do you have installed and working?
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. According to the mail I got from the developer of cDock:
This is a generic email going out as a response to many people who have contacted us regarding Security Update 2020-005 Mojave <https://support.apple.com/en-us/HT211849>
As you have probably already noticed cDock and MacForge are broken with this update.
After some investigation this issue appears to be something we're unlikely to be able to fix.
For an explanation of what’s happening: cDock and MacForge use mach_inject to load code into the Dock process
After the security update any process being injected into using mach_inject immediately crashes.
This leaves a few options for you:
1. Reinstall Mojave https://support.apple.com/en-us/HT204904 and then do not install
Security Update 2020-005 Mojave
2 Update to Catalina https://apps.apple.com/us/app/macos-catalina/id1466841314
3. Stop using cDock (and/or MacForge) and delete this folder /Library/
Application Support/MacEnhance/Plugins
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:
>Download and install mySIMBL https://github.com/w0lfschild/mySIMBL
>Copy /Library/Application Support/MacEnhance/Plugins/cDock.bundle to /
>Library/Application Support/SIMBL/Plugins/cDock.bundle
>Delete /Library/Application Support/MacEnhance/Plugins/cDock.bundle/
>Contents (not the main bundle, just the contents)
>Lock /Library/Application Support/MacEnhance/Plugins/cDock.bundle (to
>prevent modifications)
>
>Conclusion:
>
>Unfortunately unless a fix is made by someone else or Apple releases
>another update no fixes will come for cDock.
>Mainly for the following reasons
>We don’t write or maintain mach_inject
>The same issue isn’t present in the same security patch for 10.15 or the
>11.0 Betas. (which the majority of users are running)
>cDock will work on 10.14 if you do not install the latest security patch
>It’s possible we will release a patcher that can apply the fix detailed
>above on 10.14 but no ETA
So, I wonder why you have cDock working with Mojave. It's good that it works for you! But I cannot get it working.
I tried that "final option which is semi-complex", but it was a no go. I probably did something wrong there.
Sorry for you, I don’t know what’s different on your side? Ugly duck... I mean Dock!
Nice Joke! I am trying to reinstall Mojave and intend to stop after the 004 security update, just to see if I can get that transparent uglyDock'n theme working again. Will keep you posted.
Did you see my request for "What version of cDock are you using"? I am a registered user of ver. 3.1.2, all paid up.
No, I mean the stock Dock is ugly in my point of view... Using the Mavericks good old dock theme in CDock.
You should normally be ok with 004 and without Safari 14...
*Sorry, 3.1.2 too here...
Yes, the standard Dock is an ugly Dockling!
I did a reinstall of Mojave, and stopped after running Security Update 004. Now cDock is back! Welcome home.
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.
That app SilentKnight is awesome, as are the other free apps at https://eclecticlight.co/lockrattler-systhist/
Update: I used CCC to backup this working cDock system, and then ran the 005 security update again as you did.
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. I have installed Safari 13, and do not intend to try the Supplemental Update (safari 14) update.
There are still questions remaining; cDock prompts for installing a cDockHelper when I startup the cDock app, but that produces an error, and fails to install. Still cDock is working.
Head shift to a 30 degree angle...
Last edited:
Maybe the helper is already installed? It needs it to work properly and starts the CDock dock at boot up. Strange! Maybe try uninstall and install of CDock? Be sure to have a backup...Yes, the standard Dock is an ugly Dockling!
I did a reinstall of Mojave, and stopped after running Security Update 004. Now cDock is back! Welcome home.
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.
That app SilentKnight is awesome, as are the other free apps at https://eclecticlight.co/lockrattler-systhist/
Update: I used CCC to backup this working cDock system, and then ran the 005 security update again as you did.
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. I have installed Safari 13, and do not intend to try the Supplemental Update (safari 14) update.
There are still questions remaining; cDock prompts for installing a cDockHelper when I startup the cDock app, but that produces an error, and fails to install. Still cDock is working.
Head shift to a 30 degree angle...