bug – Find out how to debug M2 Macbook Air display going black proper after unlocking

First of the {hardware}/software program concerned right here:

• 2023 15” MacBook Air M2
• 16GB RAM
• Sonoma 14.4

Randomly, however somewhat ceaselessly, proper after unlocking my Mac with Contact ID my display go black and unresponsive. The one repair I’ve discovered thus far is to bodily shut the laptop computer, reopen it and unlock it once more (to be clear: there is no want for a reboot).

This can be a minor, however recurring, inconvenience and I am a bit at a loss on methods to troubleshoot it. The logs clearly present the primary unlock adopted by the shut laptop computer/second unlock:

$ log present --predicate '(eventMessage CONTAINS "lockUIPresentedWithoutSuccessfulUnlock = NO")' --style syslog --last 1h
Filtering the log knowledge utilizing "composedMessage CONTAINS "lockUIPresentedWithoutSuccessfulUnlock = NO""
Skipping information and debug messages, cross --info and/or --debug to incorporate.
Timestamp                       (course of)[PID]
2024-03-11 17:51:50.195153+0000  localhost loginwindow[544]: [com.apple.loginwindow.logging:Standard] -[LWScreenLock handleUnlockResult:]_block_invoke |      _lockUIPresentedWithoutSuccessfulUnlock = NO
2024-03-11 17:51:54.912174+0000  localhost loginwindow[544]: [com.apple.loginwindow.logging:Standard] -[LWScreenLock handleUnlockResult:]_block_invoke |      _lockUIPresentedWithoutSuccessfulUnlock = NO

Which logs between these two timestamps ought to I be to debug this additional. I absolutely admire this is perhaps a difficulty with the {hardware}, or MacOS itself however equally it may very well be a person error (or perhaps attributable to some software program I put in), both approach, I am searching for route on methods to slender down the habits I am seeing (even when that is solely having the ability to repro it persistently).

Edit:

Working pmset displaysleepnow a couple of instances in a row make it simpler to repro, it is nonetheless not constant nevertheless it hurries up the lock/unlock/repro cycle. Will try protected mode.

Edit 2:

I do know have a constant repro, that additionally repros in protected mode:

1. Run pmset displaysleepnow from a shell
2. Rapidly use Contact ID as quickly because the display goes to sleep
3. The display is now black/unusable, and requires the laptop computer to be closed/open