https://bugs.kde.org/show_bug.cgi?id=517290
Au09 <[email protected]> changed: What |Removed |Added ---------------------------------------------------------------------------- Resolution|WAITINGFORINFO |FIXED Status|NEEDSINFO |RESOLVED --- Comment #10 from Au09 <[email protected]> --- (In reply to Sanfod Rockowitz from comment #7) > This may not be the only issue, but one thing of note in in the logs is > > [1304978] Emitting DDCA_EVENT_DDC_ENABLED, card1-HDMI-A-1, ddc working: false > > Background: It is possible that, when a new monitor is detected, DDC > communication is not immediately enabled. In that case, libddcutil emits > DDC_EVENT_DDC_ENABLED with flag DDCA_EVENT_DDC_WORKING not set. The display > watch recheck thread watches to see if DDC communication becomes enabled. > If it does, a second DDCA_EVENT_DDC_ENABLED event is emitted, with flag > DDCA_DISPLAY_EVENT_DDC_WORKING set. (Note that for displays, such as laptop > displays, that truly do not support DDC, event DDCA_DISPLAY > _EVENT_DDC_ENABLED will never be emitted.) > > Prior to ddcutil release 2.2.7, this algorithm was not working properly, and > a DDCA_EVENT_DDC_ENABLED event could be prematurely emitted with > DDCA_EVENT_DDC_WORKING not set, which is what the log reports. This was > fixed in release 2.2.7. > > Suggest you retest with libddcutil from release 2.2.7 installed. (In reply to Nate Graham from comment #8) > Thanks for the update, Sanfod. > > Can affected people please re-test with ddcutil 2.2.7 or later? I have update my system and it is now fixed. Thank you. -- You are receiving this mail because: You are watching all bug changes.
