You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
A ddcutil-service user raised an issue where detect is failing resulting in DDCRC_OTHER (-3022) being returned by ddca_get_display_info_list2().
It appears the user has some non-display i2c devices that cannot be accessed. This causes set_ddca_error_detail_from_open_errors() to return DDCRC_OTHER. Which in turn results in ddca_get_display_info_list2() also returning DDCRC_OTHER even though there are displays in the return list from i2c devices that could be opened. If some devices are in the list, perhaps DDCRC_OTHER is inappropriate, or needs documenting.
I've pushed a change to ddcutil-service that filters DDCRC_OTHER which has fixed the user's issue.
If other projects are using libddcutil, it may be causing them issues as well. KDE PowerDevil comes to mind and, of course, ddcui.
The text was updated successfully, but these errors were encountered:
A ddcutil-service user raised an issue where detect is failing resulting in DDCRC_OTHER (-3022) being returned by ddca_get_display_info_list2().
It appears the user has some non-display i2c devices that cannot be accessed. This causes
set_ddca_error_detail_from_open_errors()
to returnDDCRC_OTHER
. Which in turn results inddca_get_display_info_list2()
also returningDDCRC_OTHER
even though there are displays in the return list from i2c devices that could be opened. If some devices are in the list, perhapsDDCRC_OTHER
is inappropriate, or needs documenting.I've pushed a change to
ddcutil-service
that filtersDDCRC_OTHER
which has fixed the user's issue.If other projects are using libddcutil, it may be causing them issues as well. KDE PowerDevil comes to mind and, of course, ddcui.
The text was updated successfully, but these errors were encountered: