github-starred/MonitorControl

Fork 0

mirror of https://github.com/MonitorControl/MonitorControl.git synced 2026-05-15 14:15:55 -06:00

[GH-ISSUE #285] MonitorControl 2.0.0 Resume From Sleep Bug #224

New issue

Closed

opened 2026-05-05 05:27:01 -06:00 by gitea-mirror · 16 comments

gitea-mirror commented

2026-05-05 05:27:01 -06:00

Owner

Originally created by @danielxul on GitHub (Sep 8, 2020).
Original GitHub issue: https://github.com/MonitorControl/MonitorControl/issues/285

Originally assigned to: @waydabber on GitHub.

Checklist

I have searched for existing issues
I have looked through the wiki
I have updated MonitorControl to the latest version

Describe the bug
My monitor (iiyama ProLite XB3288UHSU-B1) stays black or shows my desktop for a second and goes black (in an infinite loop) after resume from sleep. I have this issue since version 2.0.0 of MonitorControl. With version 1.7.1 everything works as it should.

To Reproduce
Steps to reproduce the behavior:

Start MonitorControl
Put Mac into sleep mode
Press a key on the keyboard to resume Mac from sleep
Monitor either stays black or goes into an infinite loop of reconnections

Expected behavior
MonitorControl 2.0.0 should work like version 1.7.1 so that I can resume my Mac from sleep and my monitor connects as usual.

Additional context
Maybe my monitor is special because it needs some time to connect to my Mac (~5 seconds). My monitors usual connection behaviour is like this: My Macbook Pro detects my external monitor and transforms into a secondary screen, then it transforms back to primary screen and transforms back to secondary screen again with my main monitor being the primary screen and showing my desktop.

Environment Information (please complete the following information):

macOS version: 10.15.4, 10.15.5, 10.15.6, 11.0 Public Beta 2
MonitorControl version: 2.0.0
Monitor(s): iiyama ProLite XB3288UHSU-B1

Originally created by @danielxul on GitHub (Sep 8, 2020). Original GitHub issue: https://github.com/MonitorControl/MonitorControl/issues/285 Originally assigned to: @waydabber on GitHub. **Checklist**  - [x] I have searched for existing issues - [x] I have looked through [the wiki](https://github.com/MonitorControl/MonitorControl/wiki) - [x] I have updated MonitorControl to the latest version **Describe the bug** My monitor (iiyama ProLite XB3288UHSU-B1) stays black or shows my desktop for a second and goes black (in an infinite loop) after resume from sleep. I have this issue since version 2.0.0 of MonitorControl. With version 1.7.1 everything works as it should. **To Reproduce** Steps to reproduce the behavior: 1. Start MonitorControl 2. Put Mac into sleep mode 3. Press a key on the keyboard to resume Mac from sleep 4. Monitor either stays black or goes into an infinite loop of reconnections **Expected behavior** MonitorControl 2.0.0 should work like version 1.7.1 so that I can resume my Mac from sleep and my monitor connects as usual. **Additional context** Maybe my monitor is special because it needs some time to connect to my Mac (~5 seconds). My monitors usual connection behaviour is like this: My Macbook Pro detects my external monitor and transforms into a secondary screen, then it transforms back to primary screen and transforms back to secondary screen again with my main monitor being the primary screen and showing my desktop. **Environment Information (please complete the following information):** - macOS version: 10.15.4, 10.15.5, 10.15.6, 11.0 Public Beta 2 - MonitorControl version: 2.0.0 - Monitor(s): iiyama ProLite XB3288UHSU-B1

gitea-mirror

2026-05-05 05:27:01 -06:00

closed this issue
added the
bug

done

feedback needed from reporter
labels

gitea-mirror commented

2026-05-05 05:27:05 -06:00

Author

Owner

@mkaflowski commented on GitHub (Sep 9, 2020):

I have the same problem.

@mkaflowski commented on GitHub (Sep 9, 2020): I have the same problem.

gitea-mirror commented

2026-05-05 05:27:08 -06:00

Author

Owner

@danielxul commented on GitHub (Sep 10, 2020):

I have the same problem.

Good to hear that I'm not the only person. Let's hope that this is getting fixed.

Also with MonitorControl 1.7.1 my monitor connects properly during resume from sleep but takes a lot more time than without MonitorControl running at all.

@danielxul commented on GitHub (Sep 10, 2020): > I have the same problem. Good to hear that I'm not the only person. Let's hope that this is getting fixed. Also with MonitorControl 1.7.1 my monitor connects properly during resume from sleep but takes a lot more time than without MonitorControl running at all.

gitea-mirror commented

2026-05-05 05:27:11 -06:00

Author

Owner

@JoniVR commented on GitHub (Sep 19, 2020):

Can you try going into Settings > Advanced and set Polling Mode to None? Does that help resolve the issue? Might give a clue to the underlying problem.

@JoniVR commented on GitHub (Sep 19, 2020): Can you try going into `Settings > Advanced` and set `Polling Mode` to `None`? Does that help resolve the issue? Might give a clue to the underlying problem.

gitea-mirror commented

2026-05-05 05:27:14 -06:00

Author

Owner

@danielxul commented on GitHub (Sep 20, 2020):

Can you try going into Settings > Advanced and set Polling Mode to None? Does that help resolve the issue? Might give a clue to the underlying problem.

I have already tried that. Same issue.

@danielxul commented on GitHub (Sep 20, 2020): > Can you try going into `Settings > Advanced` and set `Polling Mode` to `None`? Does that help resolve the issue? Might give a clue to the underlying problem. I have already tried that. Same issue.

gitea-mirror commented

2026-05-05 05:27:16 -06:00

Author

Owner

@danielxul commented on GitHub (Sep 20, 2020):

I only have this issue on resume from sleep and not on reboot.

@danielxul commented on GitHub (Sep 20, 2020): I only have this issue on resume from sleep and not on reboot.

gitea-mirror commented

2026-05-05 05:27:19 -06:00

Author

Owner

@danielxul commented on GitHub (Sep 21, 2020):

I also have this issue with MonitorControl 1.7.1 now though. That is surprising because I never had this issue with version 1.7.1 and macOS <= 10.15.3. The issue only occurs when I change the brightness with MonitorControl and put the Mac into sleep mode and wake it up again.

@danielxul commented on GitHub (Sep 21, 2020): I also have this issue with MonitorControl 1.7.1 now though. That is surprising because I never had this issue with version 1.7.1 and macOS <= 10.15.3. The issue only occurs when I change the brightness with MonitorControl and put the Mac into sleep mode and wake it up again.

gitea-mirror commented

2026-05-05 05:27:22 -06:00

Author

Owner

@ccharlton commented on GitHub (Oct 2, 2020):

I am being bit by this, too.

@ccharlton commented on GitHub (Oct 2, 2020): I am being bit by this, too.

gitea-mirror commented

2026-05-05 05:27:24 -06:00

Author

Owner

@Lightblues commented on GitHub (Oct 17, 2020):

I have the same problem and can not fix it even after uninstalling MonitorControl.

@Lightblues commented on GitHub (Oct 17, 2020): I have the same problem and can not fix it even after uninstalling MonitorControl.

gitea-mirror commented

2026-05-05 05:27:27 -06:00

Author

Owner

@JoniVR commented on GitHub (Oct 18, 2020):

@mkaflowski @ccharlton @Lightblues Are you all using the same monitor (iiyama ProLite XB3288UHSU-B1)? Please try to provide information when you comment, just saying "I have the same issue" doesn't really add much value to the issue, in that case just give it a thumbs up 😉

@JoniVR commented on GitHub (Oct 18, 2020): @mkaflowski @ccharlton @Lightblues Are you all using the same monitor (iiyama ProLite XB3288UHSU-B1)? Please try to provide information when you comment, just saying "I have the same issue" doesn't really add much value to the issue, in that case just give it a thumbs up 😉

gitea-mirror commented

2026-05-05 05:27:28 -06:00

Author

Owner

@Marmelatze commented on GitHub (Oct 18, 2020):

I have a Philips 346b1c and the same problem with 2.1.0. Setting polling to none fixed the wake from sleep problem for me.

@Marmelatze commented on GitHub (Oct 18, 2020): I have a Philips 346b1c and the same problem with 2.1.0. Setting polling to none fixed the wake from sleep problem for me.

gitea-mirror commented

2026-05-05 05:27:30 -06:00

Author

Owner

@danielxul commented on GitHub (Nov 7, 2020):

Have you looked into the issue or do you have a clue why this bug exists?

@danielxul commented on GitHub (Nov 7, 2020): Have you looked into the issue or do you have a clue why this bug exists?

gitea-mirror commented

2026-05-05 05:27:31 -06:00

Author

Owner

@waydabber commented on GitHub (Aug 19, 2021):

Hi, the new 3.0.0 versions handle sleep somewhat better. Please try and see if that helps. Thank you!

@waydabber commented on GitHub (Aug 19, 2021): Hi, the new 3.0.0 versions handle sleep somewhat better. Please try and see if that helps. Thank you!

gitea-mirror commented

2026-05-05 05:27:32 -06:00

Author

Owner

@waydabber commented on GitHub (Aug 21, 2021):

Hi, we have relased the 3.0.0 version. Could you please test if this issue is resolved and report back? Thank you!

@waydabber commented on GitHub (Aug 21, 2021): Hi, we have relased the [3.0.0 version](https://github.com/MonitorControl/MonitorControl/releases/tag/v3.0.0-rc1). Could you please test if this issue is resolved and report back? Thank you!

gitea-mirror commented

2026-05-05 05:27:34 -06:00

Author

Owner

@waydabber commented on GitHub (Aug 25, 2021):

I'll close this one since it should be solved. If there is any issue with this, please feel free to comment and ask for a reopen! Thank you!

@waydabber commented on GitHub (Aug 25, 2021): I'll close this one since it should be solved. If there is any issue with this, please feel free to comment and ask for a reopen! Thank you!

gitea-mirror commented

2026-05-05 05:27:37 -06:00

Author

Owner

@danielxul commented on GitHub (Sep 3, 2021):

The issue is solved. The new version works perfectly.

@danielxul commented on GitHub (Sep 3, 2021): The issue is solved. The new version works perfectly.

gitea-mirror commented

2026-05-05 05:27:40 -06:00

Author

Owner

@waydabber commented on GitHub (Sep 3, 2021):