Chromium update to 76.0.3809.132.
Updates may require up to 24 hours to propagate to mirrors. If the following command doesn't work, please retry later:
sudo dnf upgrade --refresh --advisory=FEDORA-2019-5d2420030cPlease login to add feedback.
This update has been submitted for testing by tpopela.
This update's test gating status has been changed to 'waiting'.
This update's test gating status has been changed to 'ignored'.
This update has been pushed to testing.
LGTM
tpopela edited this update.
New build(s):
Removed build(s):
Karma has been reset.
This update has been submitted for testing by tpopela.
This update has been pushed to testing.
Some websites fail loading with
NET::ERR_CERTIFICATE_TRANSPARENCY_REQUIRED. Examples are https://duckduckgo.com/ and https://www.bloomberg.com/. They work both with the Firefox 68.0.2 and Google Chrome 76.0.3809.132Same issue
NET::ERR_CERTIFICATE_TRANSPARENCY_REQUIRED. chromium-vaapi 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.
This update has been obsoleted.
Same issue NET::ERR_CERTIFICATE_TRANSPARENCY_REQUIRED, e.g. gist.github.com
tpopela edited this update.
New build(s):
Removed build(s):
Karma has been reset.
tpopela edited this update.
This update has been submitted for testing by tpopela.
Build chromium-76.0.3809.132-2.fc30 appears to have resolved the NET::ERR_CERTIFICATE_TRANSPARENCY_REQUIRED errors.
This update has been pushed to testing.
LGTM with this new update
This update can be pushed to stable now if the maintainer wishes
Seems fine now.
This update has been submitted for stable by tpopela.
This update has been pushed to stable.