Bug 2223059

Scratch build failed. Details below:

BuilderException: Build failed:
Command '['rpmbuild', '-D', '_sourcedir .', '-D', '_topdir .', '-bs', '/var/tmp/thn-11p_5h7v/ddcutil.spec']' returned non-zero exit status 1.

StdOut:
setting SOURCE_DATE_EPOCH=1689379200
error: Bad file: ./ddcutil-2.0.0.tar.gz: No such file or directory

RPM build errors:
    Bad file: ./ddcutil-2.0.0.tar.gz: No such file or directory


Traceback:
  File "/usr/local/lib/python3.11/site-packages/hotness/use_cases/package_scratch_build_use_case.py", line 56, in build
    result = self.builder.build(request.package, request.opts)
             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.11/site-packages/hotness/builders/koji.py", line 229, in build
    raise BuilderException(

If you think this issue is caused by some bug in the-new-hotness, please report it on the-new-hotness issue tracker: https://github.com/fedora-infra/the-new-hotness/issues

Created attachment 1975893 [details]
Update to 2.0.0-rc1 (#2223059)

Releases retrieved: 2.0.0-rc2
Upstream release that is considered latest: 2.0.0-rc2
Current version/release in rawhide: 1.4.1-2.fc39
URL: http://www.ddcutil.com/

Please consult the package updates policy before you issue an update to a stable branch: https://docs.fedoraproject.org/en-US/fesco/Updates_Policy/


More information about the service that created this bug can be found at: https://docs.fedoraproject.org/en-US/package-maintainers/Upstream_Release_Monitoring


Please keep in mind that with any upstream change, there may also be packaging changes that need to be made. Specifically, please remember that it is your responsibility to review the new version to ensure that the licensing is still correct and that no non-free or legally problematic items have been added upstream.


Based on the information from Anitya: https://release-monitoring.org/project/242390/


To change the monitoring settings for the project, please visit:
https://src.fedoraproject.org/rpms/ddcutil

Scratch build failed. Details below:

BuilderException: Build failed:
Command '['rpmbuild', '-D', '_sourcedir .', '-D', '_topdir .', '-bs', '/var/tmp/thn-_a0w80ng/ddcutil.spec']' returned non-zero exit status 1.

StdOut:
setting SOURCE_DATE_EPOCH=1693440000
error: Bad file: ./ddcutil-2.0.0.tar.gz: No such file or directory

RPM build errors:
    Bad file: ./ddcutil-2.0.0.tar.gz: No such file or directory


Traceback:
  File "/usr/local/lib/python3.11/site-packages/hotness/use_cases/package_scratch_build_use_case.py", line 56, in build
    result = self.builder.build(request.package, request.opts)
             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.11/site-packages/hotness/builders/koji.py", line 229, in build
    raise BuilderException(

If you think this issue is caused by some bug in the-new-hotness, please report it on the-new-hotness issue tracker: https://github.com/fedora-infra/the-new-hotness/issues

Created attachment 1986263 [details]
Update to 2.0.0-rc2 (#2223059)

Releases retrieved: 2.0.0
Upstream release that is considered latest: 2.0.0
Current version/release in rawhide: 1.4.1-2.fc39
URL: http://www.ddcutil.com/

Please consult the package updates policy before you issue an update to a stable branch: https://docs.fedoraproject.org/en-US/fesco/Updates_Policy/


More information about the service that created this bug can be found at: https://docs.fedoraproject.org/en-US/package-maintainers/Upstream_Release_Monitoring


Please keep in mind that with any upstream change, there may also be packaging changes that need to be made. Specifically, please remember that it is your responsibility to review the new version to ensure that the licensing is still correct and that no non-free or legally problematic items have been added upstream.


Based on the information from Anitya: https://release-monitoring.org/project/242390/


To change the monitoring settings for the project, please visit:
https://src.fedoraproject.org/rpms/ddcutil

Created attachment 1991015 [details]
Update to 2.0.0 (#2223059)

the-new-hotness/release-monitoring.org's scratch build of ddcutil-2.0.0-1.fc38.src.rpm for rawhide failed http://koji.fedoraproject.org/koji/taskinfo?taskID=106866916

Scratch build failed. Details below:

BuilderException: Build failed:
Command '['git', 'commit', '-a', '-m', 'Update to 2.0.0 (#2223059)']' returned non-zero exit status 1.

StdOut:
On branch rawhide
Your branch is up to date with 'origin/rawhide'.

nothing to commit, working tree clean


Traceback:
  File "/usr/local/lib/python3.11/site-packages/hotness/use_cases/package_scratch_build_use_case.py", line 56, in build
    result = self.builder.build(request.package, request.opts)
             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.11/site-packages/hotness/builders/koji.py", line 185, in build
    raise BuilderException(

If you think this issue is caused by some bug in the-new-hotness, please report it on the-new-hotness issue tracker: https://github.com/fedora-infra/the-new-hotness/issues

Releases retrieved: 2.1.0
Upstream release that is considered latest: 2.1.0
Current version/release in rawhide: 2.0.0-1.fc40
URL: http://www.ddcutil.com/

Please consult the package updates policy before you issue an update to a stable branch: https://docs.fedoraproject.org/en-US/fesco/Updates_Policy/


More information about the service that created this bug can be found at: https://docs.fedoraproject.org/en-US/package-maintainers/Upstream_Release_Monitoring


Please keep in mind that with any upstream change, there may also be packaging changes that need to be made. Specifically, please remember that it is your responsibility to review the new version to ensure that the licensing is still correct and that no non-free or legally problematic items have been added upstream.


Based on the information from Anitya: https://release-monitoring.org/project/242390/


To change the monitoring settings for the project, please visit:
https://src.fedoraproject.org/rpms/ddcutil

Created attachment 2009014 [details]
Update to 2.1.0 (#2223059)

the-new-hotness/release-monitoring.org's scratch build of ddcutil-2.1.0-1.fc38.src.rpm for rawhide completed http://koji.fedoraproject.org/koji/taskinfo?taskID=111883876

Releases retrieved: 2.1.2
Upstream release that is considered latest: 2.1.2
Current version/release in rawhide: 2.0.0-1.fc40
URL: http://www.ddcutil.com/

Please consult the package updates policy before you issue an update to a stable branch: https://docs.fedoraproject.org/en-US/fesco/Updates_Policy/


More information about the service that created this bug can be found at: https://docs.fedoraproject.org/en-US/package-maintainers/Upstream_Release_Monitoring


Please keep in mind that with any upstream change, there may also be packaging changes that need to be made. Specifically, please remember that it is your responsibility to review the new version to ensure that the licensing is still correct and that no non-free or legally problematic items have been added upstream.


Based on the information from Anitya: https://release-monitoring.org/project/242390/


To change the monitoring settings for the project, please visit:
https://src.fedoraproject.org/rpms/ddcutil

Created attachment 2011159 [details]
Update to 2.1.2 (#2223059)

the-new-hotness/release-monitoring.org's scratch build of ddcutil-2.1.2-1.fc38.src.rpm for rawhide completed http://koji.fedoraproject.org/koji/taskinfo?taskID=112500946

Releases retrieved: 2.1.3
Upstream release that is considered latest: 2.1.3
Current version/release in rawhide: 2.1.2-1.fc40
URL: http://www.ddcutil.com/

Please consult the package updates policy before you issue an update to a stable branch: https://docs.fedoraproject.org/en-US/fesco/Updates_Policy/


More information about the service that created this bug can be found at: https://docs.fedoraproject.org/en-US/package-maintainers/Upstream_Release_Monitoring


Please keep in mind that with any upstream change, there may also be packaging changes that need to be made. Specifically, please remember that it is your responsibility to review the new version to ensure that the licensing is still correct and that no non-free or legally problematic items have been added upstream.


Based on the information from Anitya: https://release-monitoring.org/project/242390/


To change the monitoring settings for the project, please visit:
https://src.fedoraproject.org/rpms/ddcutil

Scratch build failed. Details below:

GSSAPIAuthError: unable to obtain a session (gssapi auth failed: requests.exceptions.HTTPError: 503 Server Error: Service Unavailable for url: https://koji.fedoraproject.org/kojihub/ssllogin)
Use following documentation to debug kerberos/gssapi auth issues. https://docs.pagure.org/koji/kerberos_gssapi_debug/
Traceback:
  File "/usr/local/lib/python3.11/site-packages/hotness/use_cases/package_scratch_build_use_case.py", line 56, in build
    result = self.builder.build(request.package, request.opts)
             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.11/site-packages/hotness/builders/koji.py", line 249, in build
    session = self._session_maker()
              ^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.11/site-packages/hotness/builders/koji.py", line 436, in _session_maker
    result = koji_session.gssapi_login(
             ^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/lib/python3.11/site-packages/koji/__init__.py", line 2791, in gssapi_login
    raise GSSAPIAuthError(err)

If you think this issue is caused by some bug in the-new-hotness, please report it on the-new-hotness issue tracker: https://github.com/fedora-infra/the-new-hotness/issues

Releases retrieved: 2.1.4
Upstream release that is considered latest: 2.1.4
Current version/release in rawhide: 2.1.2-1.fc40
URL: http://www.ddcutil.com/

Please consult the package updates policy before you issue an update to a stable branch: https://docs.fedoraproject.org/en-US/fesco/Updates_Policy/


More information about the service that created this bug can be found at: https://docs.fedoraproject.org/en-US/package-maintainers/Upstream_Release_Monitoring


Please keep in mind that with any upstream change, there may also be packaging changes that need to be made. Specifically, please remember that it is your responsibility to review the new version to ensure that the licensing is still correct and that no non-free or legally problematic items have been added upstream.


Based on the information from Anitya: https://release-monitoring.org/project/242390/


To change the monitoring settings for the project, please visit:
https://src.fedoraproject.org/rpms/ddcutil

Created attachment 2017610 [details]
Update to 2.1.4 (#2223059)

the-new-hotness/release-monitoring.org's scratch build of ddcutil-2.1.4-1.fc38.src.rpm for rawhide completed http://koji.fedoraproject.org/koji/taskinfo?taskID=113737458

Releases retrieved: 2.2.0
Upstream release that is considered latest: 2.2.0
Current version/release in rawhide: 2.1.4-2.fc42
URL: http://www.ddcutil.com/

Please consult the package updates policy before you issue an update to a stable branch: https://docs.fedoraproject.org/en-US/fesco/Updates_Policy/


More information about the service that created this bug can be found at: https://docs.fedoraproject.org/en-US/package-maintainers/Upstream_Release_Monitoring


Please keep in mind that with any upstream change, there may also be packaging changes that need to be made. Specifically, please remember that it is your responsibility to review the new version to ensure that the licensing is still correct and that no non-free or legally problematic items have been added upstream.


Based on the information from Anitya: https://release-monitoring.org/project/242390/


To change the monitoring settings for the project, please visit:
https://src.fedoraproject.org/rpms/ddcutil

Scratch build failed. Details below:

BuilderException: Build failed:
Couldn't upload source /var/tmp/thn-_seoiq10/./SRPMS/ddcutil-2.2.0-1.fc40.src.rpm to koji.

Traceback:
  File "/usr/local/lib/python3.12/site-packages/hotness/use_cases/package_scratch_build_use_case.py", line 56, in build
    result = self.builder.build(request.package, request.opts)
             ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.12/site-packages/hotness/builders/koji.py", line 252, in build
    output["build_id"] = self._scratch_build(session, package.name, srpm)
                         ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.12/site-packages/hotness/builders/koji.py", line 477, in _scratch_build
    raise BuilderException("Couldn't upload source {} to koji.".format(source))

If you think this issue is caused by some bug in the-new-hotness, please report it on the-new-hotness issue tracker: https://github.com/fedora-infra/the-new-hotness/issues

Releases retrieved: 2.2.1
Upstream release that is considered latest: 2.2.1
Current version/release in rawhide: 2.1.4-2.fc42
URL: http://www.ddcutil.com/

Please consult the package updates policy before you issue an update to a stable branch: https://docs.fedoraproject.org/en-US/fesco/Updates_Policy/


More information about the service that created this bug can be found at: https://docs.fedoraproject.org/en-US/package-maintainers/Upstream_Release_Monitoring


Please keep in mind that with any upstream change, there may also be packaging changes that need to be made. Specifically, please remember that it is your responsibility to review the new version to ensure that the licensing is still correct and that no non-free or legally problematic items have been added upstream.


Based on the information from Anitya: https://release-monitoring.org/project/242390/


To change the monitoring settings for the project, please visit:
https://src.fedoraproject.org/rpms/ddcutil

Created attachment 2096877 [details]
Update to 2.2.1 (#2223059)

the-new-hotness/release-monitoring.org's scratch build of ddcutil-2.2.1-1.fc40.src.rpm for rawhide failed http://koji.fedoraproject.org/koji/taskinfo?taskID=134727555

Releases retrieved: 2.2.2
Upstream release that is considered latest: 2.2.2
Current version/release in rawhide: 2.2.1-1.fc44
URL: https://www.ddcutil.com

Please consult the package updates policy before you issue an update to a stable branch: https://docs.fedoraproject.org/en-US/fesco/Updates_Policy/


More information about the service that created this bug can be found at: https://docs.fedoraproject.org/en-US/package-maintainers/Upstream_Release_Monitoring


Please keep in mind that with any upstream change, there may also be packaging changes that need to be made. Specifically, please remember that it is your responsibility to review the new version to ensure that the licensing is still correct and that no non-free or legally problematic items have been added upstream.


Based on the information from Anitya: https://release-monitoring.org/project/242390/


To change the monitoring settings for the project, please visit:
https://src.fedoraproject.org/rpms/ddcutil

Created attachment 2114330 [details]
Update to 2.2.2 (#2223059)

the-new-hotness/release-monitoring.org's scratch build of ddcutil-2.2.2-1.fc40.src.rpm for rawhide completed http://koji.fedoraproject.org/koji/taskinfo?taskID=138898144

Releases retrieved: 2.2.3
Upstream release that is considered latest: 2.2.3
Current version/release in rawhide: 2.2.1-1.fc44
URL: https://www.ddcutil.com

Please consult the package updates policy before you issue an update to a stable branch: https://docs.fedoraproject.org/en-US/fesco/Updates_Policy/


More information about the service that created this bug can be found at: https://docs.fedoraproject.org/en-US/package-maintainers/Upstream_Release_Monitoring


Please keep in mind that with any upstream change, there may also be packaging changes that need to be made. Specifically, please remember that it is your responsibility to review the new version to ensure that the licensing is still correct and that no non-free or legally problematic items have been added upstream.


Based on the information from Anitya: https://release-monitoring.org/project/242390/


To change the monitoring settings for the project, please visit:
https://src.fedoraproject.org/rpms/ddcutil

Created attachment 2114497 [details]
Update to 2.2.3 (#2223059)

the-new-hotness/release-monitoring.org's scratch build of ddcutil-2.2.3-1.fc40.src.rpm for rawhide completed http://koji.fedoraproject.org/koji/taskinfo?taskID=138918786

Releases retrieved: 2.2.4
Upstream release that is considered latest: 2.2.4
Current version/release in rawhide: 2.2.1-3.fc44
URL: https://www.ddcutil.com

Please consult the package updates policy before you issue an update to a stable branch: https://docs.fedoraproject.org/en-US/fesco/Updates_Policy/


More information about the service that created this bug can be found at: https://docs.fedoraproject.org/en-US/package-maintainers/Upstream_Release_Monitoring


Please keep in mind that with any upstream change, there may also be packaging changes that need to be made. Specifically, please remember that it is your responsibility to review the new version to ensure that the licensing is still correct and that no non-free or legally problematic items have been added upstream.


Based on the information from Anitya: https://release-monitoring.org/project/242390/


To change the monitoring settings for the project, please visit:
https://src.fedoraproject.org/rpms/ddcutil

Created attachment 2123037 [details]
Update to 2.2.4 (#2223059)

the-new-hotness/release-monitoring.org's scratch build of ddcutil-2.2.4-1.fc40.src.rpm for rawhide failed http://koji.fedoraproject.org/koji/taskinfo?taskID=141381741

Releases retrieved: 2.2.5
Upstream release that is considered latest: 2.2.5
Current version/release in rawhide: 2.2.1-3.fc44
URL: https://www.ddcutil.com

Please consult the package updates policy before you issue an update to a stable branch: https://docs.fedoraproject.org/en-US/fesco/Updates_Policy/


More information about the service that created this bug can be found at: https://docs.fedoraproject.org/en-US/package-maintainers/Upstream_Release_Monitoring


Please keep in mind that with any upstream change, there may also be packaging changes that need to be made. Specifically, please remember that it is your responsibility to review the new version to ensure that the licensing is still correct and that no non-free or legally problematic items have been added upstream.


Based on the information from Anitya: https://release-monitoring.org/project/242390/


To change the monitoring settings for the project, please visit:
https://src.fedoraproject.org/rpms/ddcutil

Created attachment 2123855 [details]
Update to 2.2.5 (#2223059)

the-new-hotness/release-monitoring.org's scratch build of ddcutil-2.2.5-1.fc40.src.rpm for rawhide completed http://koji.fedoraproject.org/koji/taskinfo?taskID=141598823

Releases retrieved: 2.2.6
Upstream release that is considered latest: 2.2.6
Current version/release in rawhide: 2.2.1-3.fc44
URL: https://www.ddcutil.com

Please consult the package updates policy before you issue an update to a stable branch: https://docs.fedoraproject.org/en-US/fesco/Updates_Policy/


More information about the service that created this bug can be found at: https://docs.fedoraproject.org/en-US/package-maintainers/Upstream_Release_Monitoring


Please keep in mind that with any upstream change, there may also be packaging changes that need to be made. Specifically, please remember that it is your responsibility to review the new version to ensure that the licensing is still correct and that no non-free or legally problematic items have been added upstream.


Based on the information from Anitya: https://release-monitoring.org/project/242390/


To change the monitoring settings for the project, please visit:
https://src.fedoraproject.org/rpms/ddcutil

Created attachment 2132776 [details]
Update to 2.2.6 (#2223059)

the-new-hotness/release-monitoring.org's scratch build of ddcutil-2.2.6-1.fc40.src.rpm for rawhide completed http://koji.fedoraproject.org/koji/taskinfo?taskID=143207373

(In reply to Upstream Release Monitoring from comment #38)

> Releases retrieved: 2.2.6
> Upstream release that is considered latest: 2.2.6
> Current version/release in rawhide: 2.2.1-3.fc44
> URL: https://www.ddcutil.com
> Based on the information from Anitya: https://release-monitoring.org/project/242390/
> To change the monitoring settings for the project, please visit: https://src.fedoraproject.org/rpms/ddcutil

## [2.2.6] 2025-03-08

Release 2.2.6 replaces release 2.2.5, which was reported to hang KDE Plasma
at login.

#### Added

- Added API function **ddca_get_non_table_vcp_value2()**. Unlike 
  **ddca_get_non_table_vcp_value()**, which is now deprecated, the new function
  never performs verification. 

#### Changed 

- Ignore laptop displays when processing display connection and disconneciton.
- Add "AMDGPU DM i2c OEM bus" to list of names of I2C buses to be 
  ignored. Theses buses are used to control display controller 
  features like RGB lighting.  
- Use up to date macros in Autotools configuration file configure.ac: 
  AC_SYSTEM_EXTENSIONS, AC_PROG_CC conditionally replaces AC_PROG_C99.
- Eliminate use in libddcutil of linux api function **access()** to check
  if the user has RW access to a /dev/i2c device. Bug reports suggest this
  function may not always respect UDEV token UACCESS.
- More extensive syslog trace messages. Needed to aid in remote debugging, 
  particularly for KDE PowerDevil.
- Functions in the call tree from **ddca_set_non_table_vcp_value()** consistenty
  return Error_Info structs instead of status codes to improve diagnostic 
  messages written to the system log andinformation returned by 
  **ddca_get_error_detail()**. 
- Allow VCP feature numbers to be specified as a single hex digit, e.g. "getvcp 2". 

#### Fixed

- Issue #581 "ddcutil 2.2.5 causes KDE Plasma freeze due to excessive 
  permission checkes".  For some undetermined reason, despite the logged on user
  having RW access to /dev/i2c-devices, attempting to open devices sometimes 
  fails with Linux error EACCES. Function **ddca_start_watch_displays()** now
  checks if the logged on user has has RW access, and returns DDCRC_INVALID_OPERATION
  if case of failure.  This avoids repeated permission failure during display 
  change detection. Callers should check for this failure and not call 
  **ddca_start_watch_displays()** again.
- Changes for glib 2.43, which is stricter about preserving const-ness of 
  function string arguments. 
- Command **traceable-functions** failed if a non-traceable function was 
  specified on the command line or in the ddcutil configuration file.
- Issue #585, "Displays with I2C bus name DPMST not detected". It was possible
  that the video adapter for a /dev/i2c devices was not located, causing MST
  connected displays to not be detected.(Fix based on diagnosis by Diego Nunes.) 
- Issue #587, "Assert failure in ddc_packet_io.c", due to an inconsistent
  data structure in ddc_open_display(). The inconsistency was apparently caused 
  by a race condition in display change detection. Added mutex. Also addresses 
  issue #586.
- Clear the display locks table during ddca_redetect_displays().  

## [2.2.5] 2026-01-26 

Release 2.2.5 replaces release 2.2.4, which failed to build on aarch64.

#### Changed

- **ddca_start_watch_displays()**: issue warning if displays exist for which 
  the EDID is readable using sysfs but not I2C.
- API functions that write a feature value (**ddca_set_non_table_vcp_value()** etc.) 
  return DDCRC_DISCONNECTED if called before libddcutil has been notified by 
  UDEV that the display has been removed.
- **ddca_report_display_info()**, **ddca_report_display_info2()**: do not include the
  display number in the report as this is meaningless for shared library clients.

#### Fixed

- Compilation failure in function xvrpt_vstring() when building on aarch64. 
  Issue $574.


## [2.2.4] 2026-01-21

### General

Display selection has been reworked to be more flexible while also simpler internally. 
Previously, options ***--display***, ***--bus***, ***--edid***, etc. were regarded as 
identifiers that uniquely picked a display.  Generally speaking, only one identifier
could be given, with special handling for the combination of ***--mfg***, ***--model***,
and ***-sn***.  

With this change identifiers are now treated as selection criteria. More than one
can be specified.  To be chosen, the display must satisfy all the criteria given.  
As before if no selection options are specified, ***--display 1*** is assumed.

#### Added

- Option ***--edp-ambiguous***. Normally, if the DRM connector name contains the string 
  "eDP", it reliably indicates that the connected display, typically a laptop display, 
  does not implement DDC/CI, and no further checking is needed.  Owing to a bug in the 
  amdgpu driver, there have been instances where "eDP" is in the DRM connector name for 
  an external display that does support DDC/CI. There will be no fix for this bug, which
  occurs only when the BIOS is operating in CSM mode, not EFI mode. If this option is 
  given, the contents of the EDID are also checked when "eDP" is in the connector name
  to confirm that display really is a laptop display. This test is imperfect, so 
  ***--edp-ambiguous*** should only be used as a workaround for the amdgpu bug.
- Option ***--ignore bus*** takes as its argument the /dev/i2c bus number for I2C bus 
  that should be completely ignored. This option can be specified multiple times.  
  It provides a workaround for obscure bugs.

#### Changed

- Option ***--edid***: If the value given starts with "...", the remainder of the value 
  is some number of hex digits, which are compared against the final bytes of the EDID
  for display selection.
- For commands that require a monitor, if no monitors implementing DDC/CI exist,
  the error message is "No displays implementing DDC/CI found" instead of "Display not 
  found". Suggested in issue #540. 
- Command **detect**:  Insert the word "correctly" into the phrase "Monitor correctly
  uses unsupported feature flag" to make clear that this is not an error.
- Command **capabilities**: Change message "Read cached capabilities string from ..."
  to "Obtained cached capabilities string from ..." so as to be clear that the 
  string was read from a file, not that it possibly will be.

#### Fixed 

- "eDP" in a DRM connector name once again always implies a laptop or other display 
  that does not implement DDC/CI. This test was relaxed in release 2.2.1 (commit 
  8580c3d...) as a workaround for issue #384 caused by a bug in the amdgpu driver. 
  Unfortunately, the workaround caused some laptop displays to be treated as if 
  they implemented DDC/CI, with resulting errors.  Addresses issue #559.
  For handling the extremely rare case of "eDP" in the DRM connector name for an
  external monitor, option ***--edp-ambiguous*** has been added.
- Command **detect**: For laptop displays, do not output a monitor-model-id and UDF 
  file name as these are meaningless.
- Segfault in function xvrpt_vstring() caused by an extermely log capabilities string.
  Addresses issue #568.
- If ddc_write_read() fails, only call ddc_check_open_bus_alive() when executing in
  libdcutil. The test is not meaningful when executing in command line ddcutil.
  In the case where a display's EDID was obtained from sysfs but is not readable
  using I2C, ddc_write_read_with_retry() repeatedly calls i2c_check_open_bus_alive(), 
  which fails with multiple waits, markedly slowing command **detect**. As a result, 
  GNOME extensions were seen to hang the user interface.  Addresses issue #559.
- Build failure on aarch64

### Shared Library

The shared library **libddcutil** is backwardly compatible with the one in 
ddcutil 2.2.1. The SONAME is unchanged as libddcutil.so.5. The released library
file is libddcutil.so.5.4.1. 

#### Fixed

- Segfault in dw_start_watch_displays() when Wayland-X11 bridge is not running.
  Change based on pull request #563. 
- Race condition failure in ddca_open_display2() triggered by disconnecting and 
  connecting display in KDE PowerDevil.  Make setting Display_Ref flag 
  DREF_DISCONNECTED and Display_Ref variable detail=NULL an atomic operation. 
  Fixes the problem identified in issue #556.
- Option ***--ignore-hiddev*** was not being processed for libdcutil.


## [2.2.2] 2025-11-13

### General

#### Added

- Option ***--trcback***: report call stack that led to specified function
  (initial implementation). Requires ***--enable-traced-function-stack***.
- Option ***--trace-to_syslog***: Direct trace output to the system log, without 
  disabling other destinations.

#### Changed

- Option ***--enable-traced-function-stack*** is now the default.
- Additional messages reporting configuration file errors. In particular, 
  section names and the names of keys within each section are validated.
  Section names other than [global], [ddcutil], and [libddcutil] are flagged
  as errors.
- If possible, obtain list of PNP ids from /usr/share/hwdata/pnp.ids instead
  of using hardcoded list.
- Reword the parser explanation of options ***--verify*** and ***--noverify***
  for clarity.

#### Fixed

- Command **setvcp --verify** and API function **ddca_set_non_table_vcp_value()**: 
  were not performing verification,
- Command **getvcp --verbose**: output was partially in a format intended for syslog
- **ddca_display_ref_from_handle()**: was not converting internal to external display 
  reference, causing a segfault. Issue #528.
- Relax the check of the device class when determining if a device is a video 
  controller.   Look only at the first byte in sysfs device attribute class.  
  An AMD Ryzen AI 9 365 based system was seen to report 0x038000, not 0x030000.  
  Addresses issue #530.
- Build failed with an undefined reference error when configure option ***--disable-drm***
  was specified. API function **ddca_redetect_displays()** now returns 
  DDCRC_INVALID_OPERATION if ddcutil was built with ***--disable-drm***.  
  (An alternative code path through **ddca_redetect_displays()** is possible for
  the ***--disable-drm*** case, but is non-trivial and so not implemented for now.)
  Also option ***--disable-drm*** forces ***--disable-watch-displays***. 
  Addresses issue #506
- man page ddcutil: correct typo in hyperlink. Patch #535
- man page ddcutil: document that **loadvcp** uses the display identifier on the 
  command line if one was specified, and ensures it identifies the same display as
  the one identified by the data in the file being loaded.  Noted in issue #552.
- Command **environment --verbose**: 
  - Permission denied errors corrupted output of the find command used to scan for 
    DisplayLink devices.
  - Incorrectly formed path name for examining /sys/class/drm
- Fix invalid hyperlink in README.md. Pull Request #558

#### Building

- Fix out-of-tree build reference to generated file /src/base/build_details.h. Pull request #544

### Shared library

The shared library **libddcutil** is backwardly compatible with the one in 
ddcutil 2.2.1. The SONAME is unchanged as libddcutil.so.5. The released library
file is libddcutil.so.5.4.0. 

#### Added

- Option ***--watch-mode udev***
  Uses libudev to watch for display connection and disconnection. This is now 
  the default watch mode when executing on wayland if ddcutil was built to use 
  libudev, which is normally the case (configure option ***--enable-udev***). 
  Xevent continues to be the default watch mode when executing on X11. A specific
  watch mode can be forced using ***--watch-mode udev***, ***--watch-mode xevent***, 
  or ***--watch-mode poll***.  Addresses issues in [KDE-Plasma Powerdevil merge request 542]
  (https://invent.kde.org/plasma/powerdevil/-/merge_requests/542)
- Define bit **DDCA_NOVERIFY** in **DDCA_Version_Feature_Flags**. 

#### Fixed

- **ddca_open_display2()**: Return DDCRC_INTERNAL_ERROR instead of terminating 
  with assert() failure in certain ill-defined situations.  Addresses issue #556
  reported by PowerDevil.
- **ddca_redetect_displays()**: Set the **DREF_REMOVED** bit in all entries
  in the table of published display references, i.e. references that have been 
  reported to the client program, instead of emptying the table.