Black screen on wake with some custom color profiles and color table based image adjustments + FIX #5802
|
This is on a m4 minimac running Tahoe 26.6.2 Since the last update of better display, when the minimac goes to sleep, the display does not wake back up when I try to sign in. The only solution has been to manually shut down the minimac and restart. Thanks |
Replies: 9 comments 2 replies
|
I am not entirely sure why this would happen. When the app is not running, do you experience the same? |
|
I can concur here but with Golden Gate RC. Downgraded to 5.0.4 and it's fine again, seems to be a regression on 5.0.5. |
|
Hmm. So when the app is running, the display does not wake up - does it mean not powering on, or the screen just remains black but it has power? Can you copy the log output from Tools > Show Console (with logging enabled in the header), and provide a bit more context on the connected displays, connection type and the Mac model? The v5.0.5 version has some changes on how the OSD and app menu looks like and deals with Right-To-Left localizations and localizaton support mostly plus introduces a new privilege elevation model when saving system configurations - the version does not contain much direct display management related changes or things that could affect sleep, so at first glance I don't see much that could cause this issue. |
|
Remains black, it does feel like the display is connected (there isn't any No Signal message on the MSI) but it didn't show anything. Can't do anything to it tho unless I restart the Mac. This is running 5.0.4 currently lemme know if you also need the 5.0.5 output (I'd rather have it stable than broken right now, maybe after work): |
|
@d5mby66jby-alt - please let me know whether you have the same issue and whether the solution applies to you as well. I originally understood the problem as the display not powering on, not as a blank/black screen on wake. |
|
Alright can try, wonder why it's been rock stable with 5.0.4 and almost always triggered with 5.0.5. I'll let you know once i upgrade, tried it and is stable over the long run. |
|
Not sure why, this has been a longstanding issue like forever in macOS. But the problem is intermittent and low level, the app can't even detect if anything is wrong as macOS reports a color table that is perfectly fine and working. |
|
I donʻt know how to check whether iʻm using a custom profile. I didnʻt ask for one I just installed it with a dell monitor with defaults. The problem did show on the last code update. Could you kindly tell me how to revert the code to the previous rev?
Paul Kuykendall
Sent with [Proton Mail](https://proton.me/mail/home) secure email.
…On Friday, September 11th, 2026 at 8:10 AM, waydabber ***@***.***> wrote:
But can you confirm ***@***.***(https://github.com/DarrellTheWoof) that you are indeed using a custom-made color profile for the display on which this happens?
—
Reply to this email directly, [view it on GitHub](#5802?email_source=notifications&email_token=COEHTKGFY6PCWAZCV54TQ2T5OQ5Y5A5CNFSNUABIM5UWIORPF5TWS5BNNB2WEL2ENFZWG5LTONUW63SDN5WW2ZLOOQXTCOBUGA2DKOBYUZZGKYLTN5XKO3LFNZ2GS33OUVSXMZLOOSWGM33PORSXEX3DNRUWG2Y#discussioncomment-18404588), or [unsubscribe](https://github.com/notifications/unsubscribe-auth/COEHTKFVS465L5OK6RNYYLT5OQ5Y5AVCNFSNUABIKJSXA33TNF2G64TZHM2DEMBWGI4DOMZXHNCGS43DOVZXG2LPNY5TCMBXHE3TCMZYUF3AE).
Triage notifications, keep track of coding agent tasks and review pull requests on the go with GitHub Mobile for [iOS](https://github.com/notifications/mobile/ios/COEHTKHMBOZUSKD7NBXV3ND5OQ5Y5A5CNFSNUABIM5UWIORPF5TWS5BNNB2WEL2ENFZWG5LTONUW63SDN5WW2ZLOOQXTCOBUGA2DKOBYUZZGKYLTN5XKO3LFNZ2GS33OUVSXMZLOOSVGM33PORSXEX3JN5ZQ) and [Android](https://github.com/notifications/mobile/android/COEHTKGVFRCXWB6JUYRMAUL5OQ5Y5A5CNFSNUABIM5UWIORPF5TWS5BNNB2WEL2ENFZWG5LTONUW63SDN5WW2ZLOOQXTCOBUGA2DKOBYUZZGKYLTN5XKO3LFNZ2GS33OUVSXMZLOOSXGM33PORSXEX3BNZSHE33JMQ). Download it today!
You are receiving this because you were mentioned.Message ID: ***@***.***>
|

Oh, ok. The problem then is probably related to a custom color profile you may be using with macOS. This is sadly a general macOS issue with some malformed custom profiles - with such the macOS gamma table control API causes a black screen when an app attempts to alter colors. You can fix this either by
For the second option you can change either of these settings - one will have…