[GH-ISSUE #65] Completely crashes display output after starting the app #63

New issue

Closed

opened 2026-05-05 04:55:52 -06:00 by gitea-mirror · 1 comment

gitea-mirror commented

2026-05-05 04:55:52 -06:00

Owner

Originally created by @mauritsvdvijgh on GitHub (May 4, 2019).
Original GitHub issue: https://github.com/MonitorControl/MonitorControl/issues/65

Starting the app leaves my Macbook Pro 11,4 without any video output on the external monitor and the internal display. The only way to recover from this seems to be forcing the computer to shutdown and starting the computer again. The internal display is also broken after unplugging the external monitor.

Using https://github.com/kfix/ddcctl I can control the monitor brightness/volume without problems.
I also tested MonitorControl with the latest ddcctl master commit, same results.

The monitor is: Iiyama ProLite B2888UHSU

Originally created by @mauritsvdvijgh on GitHub (May 4, 2019). Original GitHub issue: https://github.com/MonitorControl/MonitorControl/issues/65 Starting the app leaves my Macbook Pro 11,4 without any video output on the external monitor and the internal display. The only way to recover from this seems to be forcing the computer to shutdown and starting the computer again. The internal display is also broken after unplugging the external monitor. Using https://github.com/kfix/ddcctl I can control the monitor brightness/volume without problems. I also tested MonitorControl with the latest ddcctl master commit, same results. The monitor is: Iiyama ProLite B2888UHSU

gitea-mirror closed this issue

2026-05-05 04:55:55 -06:00

gitea-mirror commented

2026-05-05 04:56:00 -06:00

Author

Owner

@mauritsvdvijgh commented on GitHub (May 4, 2019):

I see, ddcctl works for setting the brightness but reading the brightness crashes the display:

./ddcctl -d 1 -b '?'

crashes bot displays (internal and external)

while:

./ddcctl -d 1 -b 100

Works fine

@mauritsvdvijgh commented on GitHub (May 4, 2019): I see, ddcctl works for setting the brightness but reading the brightness crashes the display: ``` ./ddcctl -d 1 -b '?' ``` crashes bot displays (internal and external) while: ``` ./ddcctl -d 1 -b 100 ``` Works fine