This works for me. Can we push it out more quickly than waiting for the batch, due to the high profile of the issues it mitigates?
There is currently a released update for docker which relies on a version of atomic-registries newer than the released version of that. (Like, for example this one.) Assuming the functionality checks out (and it looks like it does from comments), please expedite this update.
Confirmed that the reproducer in bug #1440287 no longer hangs on 100 runs. Also, rest of system seems to work.
Updated my system with this a couple of hours ago and have been running existing and new VMs under that. It's an Intel (Skylake) system so I can't test the AMD bug, but general functionality seems... functional.
I have concerns about this. Primarily, the JPEG images are of visibly low quality. The fine detail in the trees here is like a torture-test for JPEG compression. I can see obvious-as-JPEG-artifacts with compression in GIMP at 95% (and these seem to have been saved at 90%). To my eye, at 98% or higher there is still some visible loss but it blends in to the overall texture and isn't discernible as JPEG at least. One possible way to save more space is to use chroma subsampling, which does have a subtle overall effect but is less obvious on inspection without a reference.
Also:
I'm worried about losing the PNG image this late in the cycle, because I'm not sure what all might be referencing it.
The dawn, dusk, and night images aren't just color shifts; the hills behind the trees change in weird ways.
In the previous version, there was no "foreground fog" on the dawn, dusk, and night images, but here it is there in all three with no change in color, which means there's a lot of contrast at night. I'm not opposed to the "fog at night" look, but I think the texture of the brush jumps out too much here.
Tested on Workstation and Cloud Base.
@m4rtink, this has bug #1462825 linked (a F26 blocker!) but the description says that this is about blivit-gui and python-meh only. Can you clarify?
$ sudo dnf remove sudo
Error: The operation would result in removing the following protected packages: sudo
awesome :)
Works. Tested both bugs and they seem fine (no AVCs, and pull from gcr.io works). The good ol' docker run --rm -ti fedora:rawhide /bin/bash
test works too.
Works! Note that to test, one can use gst-launch-1.0 -v playbin
, like this:
gst-launch-1.0 -v playbin uri=file:///path/to/file.mp3
Without this plugin, you should get a number of errors about missing plugins (and no sound, obviously). With it, your file will play.
Works. Does more than just "Remove pointless Enhances", even. :)
Err. "Write", not "right". Long day today!
@vgoyal — it doesn't matter what you right in the notes. It's the "Feedback" checkboxes over to the right → of the comment box that matter.
Works for me. I tried some CVE-2016-5195, but could not get it to function on older kernel, so I can't easily verify that that hole is fixed here - but, at least the new kernel does actually work.
Oooh! Look at those automatically-linked test-cases. Cool!
Users of the updated lib seem to very reliably crash.
WFM
Confirming that this works with a test password with an initial capital.