Unable to print to a HP laserjet pro M102W after installing this update - message "cfFilterChain: ghostscript (PID 22089) exited with no errors." is returned but no actual printing takes place Downgrading to 3.23.5-1 resolves issue.
This package is not installable due to a conflict with existing udica package. The updated udica 0.2.6 package is not available for F34.
$ sudo dnf update Last metadata expiration check: 3:52:14 ago on Mon 25 Oct 2021 06:17:54 BST. Dependencies resolved.
Problem: package container-selinux-2:2.170.0-2.fc34.noarch conflicts with udica < 0.2.6-1 provided by udica-0.2.5-1.fc34.noarch - cannot install the best update candidate for package udica-0.2.5-1.fc34.noarch - cannot install the best update candidate for package container-selinux-2:2.170.0-1.fc34.noarch
Doesnt install in this workstation that has been upgraded from fc31 to fc32:
Error: Transaction test error: file /usr/bin/dul-receive-pack from install of python3-dulwich-0.20.2-1.fc32.x86_64 conflicts with file from package dulwich-core-0.19.12-1.fc31.x86_64 file /usr/bin/dul-upload-pack from install of python3-dulwich-0.20.2-1.fc32.x86_64 conflicts with file from package dulwich-core-0.19.12-1.fc31.x86_64
Running dnf erase dulwich-core and then running the upgrade succeeds.
At some point the dulwich-core package has been removed, but needs to be obsoleted by the spec file.
I should add that this only causes issues after a workstation reboot (ie have a container running then reboot the workstation and attempt to start the container again). Very similar to upstream #4522 https://github.com/containers/libpod/issues/4522
Unable to start podman containers following this update, for example:
podman start heimdall Error: unable to start container "heimdall": container create failed (no logs from conmon): EOF
Deleting and recreating the podman container works fine.
Both the chromium-76.0.3809.100-1.fc30 and chromium-76.0.3809.132-1.fc30 builds have a number of issues with NET::ERR_CERTIFICATE_TRANSPARENCY_REQUIRED erros, refusing to load for example www.google.com. Rolling back to chromium-75.0.3770.100-3.fc30 resolves these issues.