The previous Chrome update broke hardware acceleration in F38 such that it would only display correctly if hardware acceleration were disabled.
The version just pushed fixes that.
Most likely just the Chrome update invalidated all the stored cache, and the problem will repeat with a future Mesa release-only bump. Or have you tested that?
Good point.
I have no idea how to test that, since only my production box was affected by the bug and I try not to experiment with it (well, not on purpose, anyway).
But I’ll know what to do if it happens again …
Thanks,
Fred
If anyone else reads this topic, you can find a Common Issue documented here:
2 Likes