Become a MacRumors Supporter for $50/year with no ads, ability to filter front page stories, and private forums.
I have wake from sleep delays/crashes ever day since April on my 15 2018 MBP. Reinstalled several times and brought it in for repair twice. They told me they can't repair it since it "isn't a hardware issue".

Just installed the patch but the MBP had the usual kernel panic right after I closed the lid. I'm very disappointed and don't understand how this issue is even possible.

That sounds suspiciously like a T2 issue.
[doublepost=1564847021][/doublepost]
The large download doesn't bother me near as much as how long it takes to install the damn thing (this on a 2017 MBP). Same with the last update - took forever. Either Apple's developers are getting sloppy, or (more likely) we're not being told everything that's being patched.

Bingo, Ringo.
 
FWIW, I had a slow wake from sleep problem with my 27" 2011 iMac. Spent weeks with Apple on the phone about it, and the issue turned out to be a bug that appeared in 10.13.6. They acknowledged the bug, and said it would not be fixed as the team had moved on to Mojave updates.

As someone who's still on 10.13.6, this is my greatest fear of upgrading to the last OS that supports 32-bit apps.
 
Which beta are you trying to get? There is no Mojave beta, as far as I know. If you are trying to get to Catalina beta, please see if you have the correct profile installed.
Catalina, I did have the correct profile but software just would not find the update. Oddly enough, when i wasnt ready to update the catalina upgrade would appear, but once I had my backup ready the catalina upgrade would no longer show. I have fixed my issue though. I had to follow the procedure found here (which was originally posted on macrumors) and use terminal. Strange, but I am not all that surprised with anything when it comes to beta software.

Special thanks to the original poster here on macrumors, bogdanw. His post describing the process can be found at https://forums.macrumors.com/threads/still-no-catalina-download-for-me.2184586/#post-27463971
 
Last edited:
  • Like
Reactions: macintoshmac
I found that just turning the monitor off and on again has the same effect as a reset (minus loosing* settings). I recognize that second bug too, super annoying.

My guess is this would not happen over DisplayPort or HDMI, just USB-C, which happens to be exclusive to the most recent Macs and monitors.

I’ll need a few days to determine if the bugs are resolved as they only appear about half the time.
[doublepost=1564735970][/doublepost]

Yes, the 2018 (which is the only one with USB-C). Very annoying indeed.

*As noted by @dickie001x who went through the trouble of sending me a private message, I made a typo here.

The update did not fix the issue I had, it showed up again today. I'm considering switching to DisplayPort, but my cables are so well-managed that it's hard to undo them :rolleyes:
 
  • Like
Reactions: macintoshmac
I have a question, if I download the entire operating system from the Mac App Store (to perform a clean install) will this patch be included?
Just downloaded the full installer. I can confirm that, yes, the current 10.14.6 full installer from the App Store does include this patch. (I checked by comparing the build number for the version the installer contains, and the build number within the OS with the supplemental update installed. They match.)
 
  • Like
Reactions: Populus
macOS 10.14.6 Update - 3.01 GB

• Fixes an issue that may cause fullscreen video to appear black on Mac mini -

Something else has been at work here since I HAD been able to view videos at FULL SCREEN.
 
They still have not fixed the wake-from-slepp bug where it briefly flashes whatever was on the screen before it went to sleep, before showing the lock screen. Absolutely a security problem.
I agree that if anyone has a camera on your screen, they can capture what was on there when you put it to sleep with a simple slow motion or free frame

The iPhone is like that too. Once I open mail, it breifly flashes a screen shot of what was there before...I don't understand the logic
 
Software Update says macOS 10.14.6 is available. Mac mini (2018)- internet.
Started download after closing all apps.
Said it would be 3.01 GB to download, taking about 2 hours, and install after restart.
Did some chores, returned, NOTHING.
Another time SU says update available, started, downloading from 160 MB.
Quit a couple times at less than 200 MB.
Started dl again - stopped at 396 MB this time.
Selected Download & Restart - AGAIN.
Spontaneously stops and checks for updates - AGAIN.
Started dl AGAIN, this time at 165 MB.

What is the problem?

After seeing the "Will try again tonight" message, a storm caused the internet to go off. Tried it the next day, went on an errand, and when I returned it was at 10.14.6. Display still does not always go to sleep according to the specified length of time in Energy Saver.
 
Last edited:
Your network internet ?

I had just done totally clean setup and upgrades, just needed the supplemental who h was ~950MB and took 30 seconds max then restarted and took~15-20 minutes. Wonder if some systems are getting UEFI firmware update applied as part of this, use to be SMC was sometimes patched, and this could easily be part of a wake from sleep issue. Someone here said they did do NVRAM, SMC reset it to no avail.
 
Shoot - this is an 2011 iMac and therefore can't run this release - I had thought I was hanging back intentionally and as it turns out this particular machine was never eligible to begin with...

Hopefully they'll look at High Sierra and back-port the fixes... not holding my breath though.

(Yes, I know, it's been time for a new iMac for a while now. Certainly have been getting my money's worth out of this set up [2 x 27" screens, SSD] for a while now]

Well, what do you know, a new update just offered today for High Sierra...

Downloaded, installation updated the firmware and had 4 if not 5 reboots.

We'll see if this fixes the issue.
 
  • Like
Reactions: macintoshmac
So far, so good. Let the computer sleep overnight, which has resulted in a sleep-wake issue crash nearly 100%, no issue this morning.
 
Your network internet ?

I had just done totally clean setup and upgrades, just needed the supplemental who h was ~950MB and took 30 seconds max then restarted and took~15-20 minutes. Wonder if some systems are getting UEFI firmware update applied as part of this, use to be SMC was sometimes patched, and this could easily be part of a wake from sleep issue. Someone here said they did do NVRAM, SMC reset it to no avail.

Yes, the latest 10.14.6 installer updated the EFI firmware on a MBP 2012 I have here.
 
My Mac was updated to this a day or 2 ago and today I was using it at work and the last I noticed said it had 34%, so I didn’t go out of my way to plug it in yet. After never once getting the alert that the battery was below 5% or whatever the number is that moves it into the red area the screen went blank. I plugged it back in and low and behold it’s been over 5 hours, has fully charged, and I can’t get it to turn on.
Is this related to this? Usually when I plug it in it starts up almost immediately due to having electricity again
 
Just downloaded the full installer. I can confirm that, yes, the current 10.14.6 full installer from the App Store does include this patch. (I checked by comparing the build number for the version the installer contains, and the build number within the OS with the supplemental update installed. They match.)
Thank you very much!
 
I found that just turning the monitor off and on again has the same effect as a reset (minus loosing* settings). I recognize that second bug too, super annoying.

My guess is this would not happen over DisplayPort or HDMI, just USB-C, which happens to be exclusive to the most recent Macs and monitors.

I’ll need a few days to determine if the bugs are resolved as they only appear about half the time.
[doublepost=1564735970][/doublepost]

Yes, the 2018 (which is the only one with USB-C). Very annoying indeed.

*As noted by @dickie001x who went through the trouble of sending me a private message, I made a typo here.

My solution was to let the display go to sleep, but never the minis. And I bought usb-c to HDMI adapters as I heard that can provide a fix. So I hedged my bets by doing two things. No complaints (so far)
 
Still having the damn issue on my 2019 13" MacBook Pro on Catalina. I guess they didn't add the update to it?

Which issue specifically? I just got my 2017 13" replaced by apple under warranty based on a wake from dead battery issue, but would love to know if there's anything I should test for on my new one.
 
This update fixed the boot up progress bar not working properly. It would fill up immediately and stay like that, pull back at the last second and finally fill up again.

Now it works properly again slowly filling up until going to the desktop.
 
This update is supposed to fix wake from sleep issues. Now I seem to suddenly have them....Guess I enable Prevent from Sleeping.
 
When I was young (12-16), we wrote 4KB programs. Then it started increasing, 60KB, 200KB, with Windows 95, 1MB, by the year 2000, 6MB, and we're well into 60MB per executable territory. The bloat is incredible.

Part of the problem is how large teams work. You have to break the problem down into smaller pieces, so small that you can hire 40+ developers, and that means everyone writes their own sort function, everyone writes their boilerplate code to interface with other modules, layers upon layers upon layers of interoperability. Of course this affects battery life, too, when the individual modules are doing little more than communicating with other modules.

That might be how large teams used to work. Today, there's project management, code review, and IME, a greater push to use stuff like boost and other third party libraries rather than write-your-own.

This is especially true for C++, which doesn't support shared libraries, so you have to "glue" the same code into each module over and over and over. Probably 50+ megabytes of core libraries duplicated in every file. There's a way to share, but it's more difficult, it's easier to duplicate. You'll end up with 80% of your executable being either a duplicate, or boilerplate.

This claim is false. C++ has supported shared libraries for quite a long time. In fact, it's been my experience that building and linking shared libraries is easier (at least with the GNU toolchain) than static libraries, as the last time I had to use static libraries, I ran into tons of link-time collisions with template specializations; whereas with code compiled -fPIC, those specializations magically had their scope limited to the translation unit in which they were generated.
 
Anyone having install problems? and why does it show catalina if that Mac never had it?

IMG_0186.jpg
 
Register on MacRumors! This sidebar will go away, and you'll see fewer ads.