[GH-ISSUE #804] MonitorControl exits after sleep/wake of LG 34WK95U #515

New issue

Closed

opened 2026-05-05 06:10:09 -06:00 by gitea-mirror · 3 comments

gitea-mirror commented

2026-05-05 06:10:09 -06:00

Owner

Originally created by @xszuflax on GitHub (Nov 19, 2021).
Original GitHub issue: https://github.com/MonitorControl/MonitorControl/issues/804

Before opening the issue, have you...?

Searched for existing issues
Looked through the wiki
Updated MonitorControl to the latest version (if applicable)

Describe the bug

Hello,

I'm using MonitorControl since version 3.x on this setup. Since I've update to macOS 12.0.1 or MonitorControl 4.0.1. Not sure exactly when it started MonitorControl exits after external monitor wakes up or goes to sleep. I need to reopen the app. All functions work well just the app is not there when I need it and need to reopen.

Setup:
MacBook: MacBookPro17,1 (M1 MacBook Pro 13")
Monitor: LG 34WK95U connected via Thunderbolt 3 (Newest firmware)
Dock: Elgato Dock Pro (Monitor is connected via TB3 to the dock and the dock to the MacBook also via TB3)

Steps to reproduce

Put MacBook to the lock screen and let monitors to turn off. Once unlocked MonitorControl is not active and needs to be relaunched.

Expected behavior

MonitorControl still works after monitor wakes up from sleep.

Anything else?

No response

Environment Information (please complete the following information)

- macOS version: 12.0.1
- Mac model: MacBookPro17,1 (M1 MacBook Pro 13")
- MonitorControl version: 4.0.2
- Monitor(s): LG 34WK95U
- Apple Silicon/M1 (yes or no): yes

Originally created by @xszuflax on GitHub (Nov 19, 2021). Original GitHub issue: https://github.com/MonitorControl/MonitorControl/issues/804 ### Before opening the issue, have you...? - [X] Searched for existing issues - [X] Looked through [the wiki](https://github.com/MonitorControl/MonitorControl/wiki) - [X] Updated MonitorControl to the latest version (if applicable) ### Describe the bug Hello, I'm using MonitorControl since version 3.x on this setup. Since I've update to macOS 12.0.1 or MonitorControl 4.0.1. Not sure exactly when it started MonitorControl exits after external monitor wakes up or goes to sleep. I need to reopen the app. All functions work well just the app is not there when I need it and need to reopen. Setup: MacBook: MacBookPro17,1 (M1 MacBook Pro 13") Monitor: LG 34WK95U connected via Thunderbolt 3 (Newest firmware) Dock: Elgato Dock Pro (Monitor is connected via TB3 to the dock and the dock to the MacBook also via TB3) ### Steps to reproduce Put MacBook to the lock screen and let monitors to turn off. Once unlocked MonitorControl is not active and needs to be relaunched. ### Expected behavior MonitorControl still works after monitor wakes up from sleep. ### Anything else? _No response_ ### Environment Information (please complete the following information) ```markdown - macOS version: 12.0.1 - Mac model: MacBookPro17,1 (M1 MacBook Pro 13") - MonitorControl version: 4.0.2 - Monitor(s): LG 34WK95U - Apple Silicon/M1 (yes or no): yes ```

gitea-mirror

2026-05-05 06:10:09 -06:00

closed this issue
added the
feedback needed from reporter
label

gitea-mirror commented

2026-05-05 06:10:15 -06:00

Author

Owner

@waydabber commented on GitHub (Nov 20, 2021):

Hi @xszuflax , handling of sleep was changed a bit in 4.0.2 (wait times were shortened). Can you please try 4.0.1 and see if the issue is present with that version as well? Thank you!

@waydabber commented on GitHub (Nov 20, 2021): Hi @xszuflax , handling of sleep was changed a bit in 4.0.2 (wait times were shortened). Can you please try 4.0.1 and see if the issue is present with that version as well? Thank you!

gitea-mirror commented

2026-05-05 06:10:16 -06:00

Author

Owner

@xszuflax commented on GitHub (Nov 20, 2021):

Hello @waydabber this issue actually started on 4.0.1. I've updated to 4.0.2 hoping for the fix...

And now the funny thing. Since I created this very ticket the issue is gone... not sure what happened.

@xszuflax commented on GitHub (Nov 20, 2021): Hello @waydabber this issue actually started on 4.0.1. I've updated to 4.0.2 hoping for the fix... And now the funny thing. Since I created this very ticket the issue is gone... not sure what happened.

gitea-mirror commented

2026-05-05 06:10:18 -06:00

Author

Owner

@waydabber commented on GitHub (Nov 20, 2021):

Well, next time you have this issue, just create a ticket, that will solve it. :)

All right, if the problem comes back, let me know!

@waydabber commented on GitHub (Nov 20, 2021): Well, next time you have this issue, just create a ticket, that will solve it. :) All right, if the problem comes back, let me know!