After installing security update 2021-007 on Catalina, MAMP stopped working and flags a bug with the graphics kernel
MacBook Pro 13″, macOS 10.15
steve626 wrote:
[...] Being able to go all the way up to Catalina minus the very last security update is not too bad.
I can easily share this point of view. :-)
I just found a workaround so that Security Update 2021-007 Catalina can be installed... minus 'AppleIntelHD4000GraphicsGLDriver.bundle'. :
As already told I have a clean install of Catalina on a second Harddisk. I installed 'Security Update 2021-006 Catalina' onto this HD. This includes "/System/Library/Extensions/AppleIntelHD4000GraphicsGLDriver.bundle" Version 14.7.18
(This is the last working version of this bundle. Update 007 installs version 14.7.20, which is obviously broken)
I copied this bundle (and only this) to my primary System with 'Security Update 2021-007 Catalina' installed.
After a reboot to my primary system everything works again as expected, all WebGL-Pages can be loaded. :-)
This has the advantage that 'Security Update 2021-007 Catalina' is still installed, so there's no annoying reminder to install new updates from the system preferences. And in fact all Security Updates are installed - only with the exception of the GLDriver bundle.
I think that's currently the least possible violation of system security.
Regards - Matthias
Just installed 008 update and everything is working alright again and safe as apple says. No need to replace HD4000 driver.
@ikrupp: You're right regarding the recommendations of Apple Support.
I did a fresh install of MacOS 10.15.7 Catalina on a second hard disk - with the same results. After installation of the "Security Update 2021-007 Catalina" OpenGL/WebGL is broken on Intel HD4000 graphics. Not a single piece of additional software was installed nor was the initial admin account modified in any way. It was the most clean (current) Catalina installation one can think of.
Regards - Matthias
No, according to Apple Support that won't be fixed.
I just got a callback from Apple Support. They said that my Mac Mini (Late 2012) has the status "vintage" and won't be supported any more. I guess that's true for all Macs with this HD4000 GPU... :-(
I argued that the OS (Catalina) is still supported but they responded that the underlying graphics hardware isn't.
This is not sustainable but nevertheless I must admit that even until that point this MacMini is the longest lasting Computer I ever had. 9 Years usable period is quite much for a computer.
Regards - Matthias
Yes , Starry Night Pro and Stellarium (Astro apps) both fail as well. Clean install with no security update or Time Machine restore (one with no security update!) required to run things normally.
I have contacted Apple (via chat support) but not holding my breath.
kestrel9532 wrote:
No, according to Apple Support that won't be fixed.
I just got a callback from Apple Support. They said that my Mac Mini (Late 2012) has the status "vintage" and won't be supported any more. I guess that's true for all Macs with this HD4000 GPU... :-(
I argued that the OS (Catalina) is still supported but they responded that the underlying graphics hardware isn't.
This is not sustainable but nevertheless I must admit that even until that point this MacMini is the longest lasting Computer I ever had. 9 Years usable period is quite much for a computer.
Regards - Matthias
I am using new MacBook Pros, but I also, like you, have some "vintage" Macs. For instance, a 2008 iMac (with a built in DVD superdrive), 2010 MacBook Air, and 2013 MacBook Air. In fact worse, than "vintage," Apple classifies all these 2013 and older Macs as "obsolete" and no longer supports them nor stocks parts for them. I found this out when I needed a new battery and SSD for that 2013 Mac, but I was ultimately able to get excellent parts from OWC.
These "vintage" or "obsolete" Macs continue to run great for me. But the 2008 can't go past 10.11, the 2010 can't go past 10.13, and the 2013 can't go past Big Sur. Ultimately, one must accept the security shortcomings of "obsolete" equipment or get a new computer. Being able to go all the way up to Catalina minus the very last security update is not too bad.
Reinstall Catalina from the Recovery Partition (Boot with CMD+R pressed) and Security Update 2021-006 Catalina afterwards.
It's a bit time consuming (approx. 2 hours) but simple and save - no user data will be destroyed.
there is a simple way to go back.
You have to reinstall OS10.15.7 using the R command at startup.
This OS version does not contain the security update 2021-007 for Catalina.
HectorMI wrote:
After installing security update 2021-007 on Catalina, MAMP stopped working and flags a bug with the graphics kernel
Verify your MAMP software is up to date — v6.6 is now available
Yes! Everything is working again after installing update 2021-008. Adobe Illustrator and other graphics software no longer crashes on startup. Hallelujah, I can finally get back to work.
This is what I noticed in the log (Process: com.apple.WebKit.WebContent [2178]). MacMini 2012 w/Catalina Sec.Update 2021-007
Since Sec.Update 007, Google Street View crashes, myTuner Radio crashes. I agree, it's the HD4000GraphicsGLDriver.
Thread 0 Crashed:: Dispatch queue: com.apple.main-thread
0 libsystem_kernel.dylib 0x00007fff6e36733a __pthread_kill + 10
1 libsystem_pthread.dylib 0x00007fff6e427e60 pthread_kill + 430
2 libsystem_c.dylib 0x00007fff6e2ee808 abort + 120
3 libGPUSupportMercury.dylib 0x00007fff554020a5 gpusGenerateCrashLog.cold.1 + 95
4 libGPUSupportMercury.dylib 0x00007fff553f918f gpusGenerateCrashLog + 89
5 com.apple.driver.AppleIntelHD4000GraphicsGLDriver 0x00007fff29cd0dd0 gpusKillClientExt + 9
6 libGPUSupportMercury.dylib 0x00007fff553fa55b gpusSubmitDataBuffers + 164
7 com.apple.driver.AppleIntelHD4000GraphicsGLDriver 0x00007fff298a6c78 IntelCommandBuffer::getNew(GLDContextRec*) + 48
8 com.apple.driver.AppleIntelHD4000GraphicsGLDriver 0x00007fff298a6aa6 intelSubmitCommands + 187
9 libANGLE-shared.dylib 0x0000000110d7a53b rx::ContextGL::flush(gl::Context const*) + 17
10 libANGLE-shared.dylib 0x0000000110dd75cf gl::Flush() + 93
11 com.apple.WebCore 0x000000010c0aeb76 WebCore::GraphicsContextGLOpenGL::prepareForDisplay() + 134
12 com.apple.WebCore 0x000000010c778862 WebCore::Document::prepareCanvasesForDisplayIfNeeded() + 242
13 com.apple.WebCore 0x000000010ce3d6ae WebCore::Page::forEachDocument(WTF::Function<void (WebCore::Document&)> const&) const + 398
14 com.apple.WebCore 0x000000010ce4514a WebCore::Page::updateRendering() + 2698
15 com.apple.WebKit 0x000000010a3f0930 WebKit::TiledCoreAnimationDrawingArea::updateRendering(WebKit::TiledCoreAnimationDrawingArea::UpdateRenderingType) + 774
16 com.apple.CoreFoundation 0x00007fff33f6b6ec __CFRUNLOOP_IS_CALLING_OUT_TO_AN_OBSERVER_CALLBACK_FUNCTION__ + 23
17 com.apple.CoreFoundation 0x00007fff33f6b61c __CFRunLoopDoObservers + 457
18 com.apple.CoreFoundation 0x00007fff33f6a21e CFRunLoopRunSpecific + 525
19 com.apple.Foundation 0x00007fff3662bc38 -[NSRunLoop(NSRunLoop) runMode:beforeDate:] + 212
20 com.apple.Foundation 0x00007fff366de6df -[NSRunLoop(NSRunLoop) run] + 76
21 libxpc.dylib 0x00007fff6e4714ea _xpc_objc_main.cold.4 + 49
22 libxpc.dylib 0x00007fff6e471430 _xpc_objc_main + 559
23 libxpc.dylib 0x00007fff6e470f63 xpc_main + 377
24 com.apple.WebKit 0x000000010a0f68d9 WebKit::XPCServiceMain(int, char const**) + 266
25 libdyld.dylib 0x00007fff6e21fcc9 start + 1
Let me start over.
My english is not the best.
My Mac is a Mac mini Late 20212 and after 10.15.7 some apps that I need for work not open anymore.
The console show me Graphics kernel error: 0xfffffffb
Investigating this issue in other forums founded the same error on other Mac OS versions so it worth try.
After disabling SIP and reboot in safe mode
What I done is copy this files and folders inside SecUpd2021-006Catalina.pkg in my /system/Library/Extensions folder.
reenable SIP reboot and everything work fine again.
I´m not an expert. Need to do something to get my Mac working again
I had a Catalina clean install with no sec. updates other than the included with the package, when I booted the Mac it offered 2021-005, but soon jumped to 2021-007. Yesterday, the same happened, but jumped directly to the 008 one, so If it automatically jumps to it, it's OK to just install 008.
I say this because in the past if an update has been required to go forward It offers that update until you install it and only then the newer ones.
Suprisingly 008 fixed all the problems I noticed with the "James Bond: A Mac to be killed" one :'-)
Interesting in that Safe Mode disables all third party extensions, plugins, etc. It’s just macOS running without any third party stuff to contend with. So at least in your case, the security patch does not seem to be the problem. Many times support will make the suggestion to create another user account and test from that account. If things are okay it means something went off the rails in the main account.
All that has to happen is a single bit getting switched on or off by corruption or a download glitch. Corruption does happen and it can brick even the most cared for installation.
While you're at it: Please also check the file 'AppleIntelHD4000GraphicsGLDriver.bundle' - the error occurs there.
And look *into* the bundle please: Select the bundle -> CTRL+Click -> 'Show Content' (or similar)
This quick solution worked addressed the WebGL problems I was having in Safari after the update, thank you for sharing Matthias.
================================
" BTW: A guy at mactechnews.de found a pretty simple solution for the "Safari/WebGL"-Problem:
In Safari check "Develop -> Experimental Features -> WebGL via Metal" to "on" - then WebGL-pages load again without problems (so far).
That does not help Firefox (still crashes with these pages) nor does it help standalone apps with these HD4000 problems (presumably, I have none).
Regards - Matthias "
After security update 2021-007 for catalina MAMP isn't working, Graphics kernel error: 0xfffffffb
