-
-
Notifications
You must be signed in to change notification settings - Fork 179
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Monitor DDC not detected sometimes (new wmi-bridge on beta) #809
Comments
i cloned the repo on the beta branch and started it locally, there i can see that i get "Sorry, no updates right now!" all the time. so it seems the monitorthread is never launched somehow or there is a race condition. so clickMonitorDDC does not seem to have anything to do with it. i also don't see "WMI-BRIDGE TEST" in that case. trying it again after a few times it works and i can see my monitor. will see if i can pinpoint the exact cause |
ok i think there is something going on in the getWMIMonitors c++ code. |
i found out how to print the debug lines here is the log where the monitor was not detected. i can now say he is stalling at this line and never continues and resolves the promise https://github.com/xanderfrangos/twinkle-tray/blob/master/src/wmi-bridge-test.js#L22
|
i suspect the loop https://github.com/xanderfrangos/twinkle-tray/blob/master/src/modules/wmi-bridge/wmi-bridge.cc#L243 is never finishing, i am now trying to debug this. unfortunately once the monitor was detected after a few attempts i need to wait again until the error happens. maybe it is caused by hibernation? let's see |
@eikaramba If you disable Do you ever get Also, are you on a laptop or desktop? |
For the rest i need to check again, because the error unfortunately only happens sometimes... |
@eikaramba Rolled out a new beta that might help. It's possible there was a race condition that caused the test to never finish. |
thanks i will test it. on the old version disabling wmi bridge did not help. unfortunately i rarely happened in the last days so i wasn't able to debug it more but will test the new version. if it does not happen in the next 3 months i will close this issue |
I have the LG 34GN850-B Monitor which offers DDC. Working 100% in ClickMonitorDDC (https://github.com/chrismah/ClickMonitorDDC7.2)
Now i switched to Twinkle-Tray because ClickMonitor crashes after hibernation.
Twinkle-Tray was detecting my monitor with the default settings, however today it stopped working and no restart, switching to legacy mode etc did not helped. Then i started ClickMonitor again to see if it is working. Low and behold after THEN exiting ClickMonitor and starting Twinkle it was able to detect the Monitor. Weird right? Is there any way i can help debugging the issue?
I am on latest beta 1.16.0-beta7
The text was updated successfully, but these errors were encountered: