eoyilmaz / displaycal-py3

DisplayCAL Modernization Project
https://eoyilmaz.github.io/displaycal-py3/
GNU General Public License v3.0
774 stars 56 forks source link

Sonoma 14.4 & Spyder X black screen #395

Open Tonym69 opened 1 month ago

Tonym69 commented 1 month ago

Hello, I'm trying to calibrate the Iiyama ProLite XB3070WQS monitor attached to my MacBook Air M1.

About 8 minutes into calibration, there is a "whooshing wind" sound effect (maybe completion of calibration?) and both monitors go black (not disabled, just black pixel values).

From there, system is visually unresponsive. If I blindly tab through open apps then some produce keyboard error tones and some do not, so it seem the system is still running in the background but nothing works to restore the displays.

Only way out is to force shutdown.

Is there a place where I would find an error log or record after reboot? I can offer no further info about the problem, only what I described.

Running MacOS Sonoma 14.4 on 2020 MacBook Air M1 using a DataColor SpyderX. Python 3.12.5 also wxPython 4.2.1 (both read from launch commentary in Terminal) DisplayCal 3.9.12 Argyll "up to date" according to launch commentary (downloaded this morning, don't know version)

Any help appreciated! Thanks.

son01490517 commented 5 days ago

This bug has been present since the original DisplayCal (Python 2.x). Just unplug the monitor and plug it back in and it will work fine. I am using a dummy HDMI via type C hub, just plug it in and out with the same result.

Tonym69 commented 4 days ago

That's very helpful, thank you! I will have another go and see what happens. Tony

Sent with Proton Mail secure email.

On Monday, 23 September 2024 at 23:52, SCN @.***> wrote:

This bug has been present since the original DisplayCal (Python 2.x). Just unplug the monitor and plug it back in and it will work fine. I am using a dummy HDMI via type C hub, just plug it in and out with the same result.

— Reply to this email directly, view it on GitHub, or unsubscribe. You are receiving this because you authored the thread.Message ID: @.***>