Mac goes to sleep directly after session opening

Question

Level 1

22 points

Mac goes to sleep directly after session opening

My MacBook Pro (15-inches, 2019) goes sometimes to sleep by itself just after start-up and opening my session. It's like it is put in deep sleep mode as I have to wait 2-3 minutes after the display gone black to get it back on (by touching any key) and it asks me for my password, not Touch ID as it would for a "standard" sleep.

As sometimes I also got the big red battery warning (with a battery above 50%), I initially thought about a battery management issue. I tried resetting both SMC and NVRAM without success.

I took my Mac to a Genius Bar, they ran some tests and didn't find any hardware issue. So there is definitely something wrong in the system. But before wiping out my Mac and taking hours to reinstall and set-up everything on a clean install, I wanted to know if someone had an idea (and a solution!) of what the issue could be.

The two last times I had the problem, I noticed the same `lsd` crash report in Console.app. I searched about this on the forum and found a solution with this terminal command, which didn't solve the issue (I tried this yesterday and I got the same issue today):

/System/Library/Frameworks/CoreServices.framework/Versions/A/Frameworks/LaunchSe rvices.framework/Versions/A/Support/lsregister -kill -r -domain local -domain system -domain user

I attach both the EtreCheckPro and `lsd` crash reports.

EtreCheckPro Report

lsd Crash Report

MacBook Pro 15″, macOS 11.2

Posted on Feb 25, 2021 12:52 AM

Reply

Answer 1

fon112

Level 1

19 points

Feb 25, 2021 6:44 AM in response to the.dreamer

Hi, the same thing happens to me and other users. This is a real odyssey. I am in contact with Apple and the development team to fix it. Everything seems to indicate that it is a failure of the operating system. My computer is a 13-inch macbook pro. I have performed a lot of actions, I explain:

1- I have taken it to the repair center, they did not detect anything

2- I have reinstalled big sur from a usb

3- I have installed big sur in another partition as a test and without linking with icloud

4- I have checked the console

The error persists. Can you tell me, please, the registration of your console in an hour close to the shutdown?

In case you wish, here is my original post in which I talk about this:

https://discussions.apple.com/thread/252480159

Reply

Answer 2

the.dreamer Author

Level 1

22 points

Feb 25, 2021 8:29 AM in response to fon112

I do not have this kind of message at the time of the issue, but only one minute after, so I'm not sure this is related. And this error does not seem to be severe as it is quite present in my system.log (548 times today).

I opened a radar on Feedback Assistant to signal the bug. You can do that too (and mention mine: FB8968951), this usually helps a little to reach Apple engineers with our issues.

Reply

Answer 3

the.dreamer Author

Level 1

22 points

Feb 27, 2021 12:47 AM in response to fon112

Quick update: this morning the issue occurred both before and after session opening. This proves this is not an issue related to my own session (like a third-party software messing things up) and is more system-wide.

Always the same: display turns off, fans keep working for a moment before turning off, wait a few minutes, and touching a key usually wakes it up (without restarting). Connecting to the charger is not always required (it wasn't this morning).

If an Apple employee is reading this: I updated the radar (FB8968951) accordingly with the system.log file.

Reply

Answer 4

the.dreamer Author

Level 1

22 points

Apr 9, 2021 12:57 AM in response to the.dreamer

I just spent two days doing a complete clean install of macOS on my Mac for… nothing.

The issue is still present, which confirms this is a macOS problem and not something weird on my own and previous installation.

Reply

Answer 5

the.dreamer Author

Level 1

22 points

Feb 25, 2021 8:14 AM in response to fon112

Hi, thanks for the quick reply!

We definitely have a similar issue (except my Mac does not completely shut down as yours, but goes to deep sleep).

What do you mean by console registration? The system.log file?

Did Apple confirm you it is working on a bug fix?

Reply

Answer 6

fon112

Level 1

19 points

Feb 25, 2021 8:16 AM in response to the.dreamer

Yes, I mean that, can you check if you find this error?

(com.apple.mdworker.shared.02000000-0500-0000-0000-000000000000 [1152]): Service exited due to SIGKILL | sent by mds [96]

I don't know if it could be related.

No, nothing has been confirmed to me at the moment, but I know that the development team is analyzing it. I've been testing for weeks. It's all quite annoying.

Reply

Answer 7

fon112

Level 1

19 points

Feb 27, 2021 12:30 AM in response to the.dreamer

Thanks, from Apple they tell me that they are investigating it, but this is tremendously annoying. The first disagreement I have with the company. There are numerous posts about it: it is a real annoyance for any user to have to connect the computer to the power outlet so that it works first thing in the day.

PS: Yesterday's update still hasn't fixed this issue

Reply

Answer 8

the.dreamer Author

Level 1

22 points

Mar 7, 2021 2:02 AM in response to the.dreamer

Update: Just before my Mac going to unexpected sleep (right after startup process), I noticed these lines in system.log:

Mar  7 10:50:52 MBP Installer Progress[98]: Start quit timer, will attempt to quit in 5 second(s) at 10:50:57
Mar  7 10:50:53 MBP Installer Progress[98]: Order Out CG Shield Window
Mar  7 10:50:57 MBP Installer Progress[98]: Quitting because there are no phases. There are no connected processes. The UI is not showing.
Mar  7 10:50:57 MBP Installer Progress[98]: Quitting Progress App
Mar  7 10:50:57 MBP Installer Progress[98]: Showing the cursor in Progress UI
Mar  7 10:50:57 MBP Installer Progress[98]: GUI session is not logged in
Mar  7 10:50:57 MBP Installer Progress[98]: Setting window alpha values to 0.0
Mar  7 10:50:57 MBP Installer Progress[98]: Ordering windows out
Mar  7 10:50:57 MBP Installer Progress[98]: Showing the cursor in Progress UI
Mar  7 10:50:57 MBP loginwindow[158]: The connection was interrupted, calling interruption handlers

Reply

Answer 9

fon112

Level 1

19 points

Feb 27, 2021 12:33 AM in response to the.dreamer

Well, at least we know we have the same error ... It's something, right? Have you discovered something? All the best

Reply

Mac goes to sleep directly after session opening

Similar questions