Description of problem: After upgrading from 84.0.4147.89 to 85.0.4183.83 HW acceleration stopped working. I'm running Chrome with ignore-gpu-blacklist feature enabled using the built-in GPU0 "VENDOR= 0x10de, DEVICE=0x134d *ACTIVE*" Version-Release number of selected component (if applicable): chromium-85.0.4183.83-1.fc32.x86_64 chromium-common-85.0.4183.83-1.fc32.x86_64 How reproducible: Always Steps to Reproduce: 1. upgrade to 85 2. open URL chrome://gpu/ 3. Actual results: "Problems Detected Gpu compositing has been disabled, either via blacklist, about:flags or the command line. The browser will fall back to software compositing and hardware acceleration will be unavailable. Disabled Features: gpu_compositing" Expected results: "Compositing: Hardware accelerated" Additional info: On the console I can see a new error message with 85: [172275:172275:0909/114203.695163:ERROR:gl_implementation.cc(286)] Failed to load /usr/lib64/chromium-browser/libGLESv2.so: /usr/lib64/chromium-browser/libGLESv2.so: cannot open shared object file: No such file or directory The library is still there and in the same location as in 84: # rpm -qla "chrom*" | fgrep .so ... /usr/lib64/chromium-browser/swiftshader/libGLESv2.so /usr/lib64/chromium-browser/swiftshader/libGLESv2.so.TOC # ls -lht /usr/lib64/chromium-browser/libGLESv2.so ls: cannot access '/usr/lib64/chromium-browser/libGLESv2.so': No such file or directory After downgrading to 84 HW acceleration works fine again. I tried to figure out what 84 does differently so I used $ strace -o chromium.log -ff /usr/bin/chromium-browser $ fgrep GLES chromium.log* With 85 I get some hits: chromium.log.177646:openat(AT_FDCWD, "/usr/lib64/chromium-browser/libGLESv2.so", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory) chromium.log.177664:openat(AT_FDCWD, "/usr/lib64/chromium-browser/swiftshader/libGLESv2.so", O_RDONLY|O_CLOEXEC) = 131 chromium.log.177664:openat(AT_FDCWD, "/usr/lib64/chromium-browser/swiftshader/lib64GLES_V2_translator.so", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory) chromium.log.177664:openat(AT_FDCWD, "/usr/lib64/chromium-browser/swiftshader/libGLESv2.so.2", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory) chromium.log.177664:openat(AT_FDCWD, "/usr/lib64/chromium-browser/swiftshader/lib64GLES_CM_translator.so", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory) chromium.log.177664:openat(AT_FDCWD, "/usr/lib64/chromium-browser/swiftshader/libGLES_CM.so.1", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory) chromium.log.177664:openat(AT_FDCWD, "/usr/lib64/chromium-browser/swiftshader/libGLES_CM.so", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory) chromium.log.177664:openat(AT_FDCWD, "/usr/lib64/chromium-browser/swiftshader/lib64GLES_CM_translator.so", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory) chromium.log.177664:openat(AT_FDCWD, "/usr/lib64/chromium-browser/swiftshader/libGLES_CM.so.1", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory) chromium.log.177664:openat(AT_FDCWD, "/usr/lib64/chromium-browser/swiftshader/libGLES_CM.so", O_RDONLY|O_CLOEXEC) = -1 ENOENT (No such file or directory) but I don't get any hits for a 84 run. I guess something in that area has changed between 84 -> 85 and now chromium requires that library.
Yup. Looks like chromium has two different copies of those files now. Looks like an easy fix (we just need to package both copies).
The F32 build of 85.0.4183.102 failed (infra failure?), but the x86_64 part went through. After installing those RPMs manually I can confirm that HW acceleration is enabled again. Thanks.
The new F32 build on koji failed (infra failure?), but the x86_64 part went through. After installing those RPMs manually I can confirm that HW acceleration works again.
*** Bug 1878916 has been marked as a duplicate of this bug. ***
FEDORA-2020-59d3a84267 has been submitted as an update to Fedora 33. https://bodhi.fedoraproject.org/updates/FEDORA-2020-59d3a84267
FEDORA-2020-6fe1b505a5 has been submitted as an update to Fedora 31. https://bodhi.fedoraproject.org/updates/FEDORA-2020-6fe1b505a5
FEDORA-2020-9b9e8e5306 has been submitted as an update to Fedora 32. https://bodhi.fedoraproject.org/updates/FEDORA-2020-9b9e8e5306
FEDORA-EPEL-2020-dec199d5a2 has been submitted as an update to Fedora EPEL 7. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2020-dec199d5a2
FEDORA-EPEL-2020-b65eda12a7 has been submitted as an update to Fedora EPEL 8. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2020-b65eda12a7
FEDORA-2020-59d3a84267 has been pushed to the Fedora 33 testing repository. In short time you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2020-59d3a84267` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2020-59d3a84267 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2020-9b9e8e5306 has been pushed to the Fedora 32 stable repository. If problem still persists, please make note of it in this bug report.
FEDORA-EPEL-2020-dec199d5a2 has been pushed to the Fedora EPEL 7 testing repository. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2020-dec199d5a2 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-EPEL-2020-b65eda12a7 has been pushed to the Fedora EPEL 8 testing repository. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2020-b65eda12a7 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2020-6fe1b505a5 has been pushed to the Fedora 31 testing repository. In short time you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2020-6fe1b505a5` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2020-6fe1b505a5 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-EPEL-2020-72907017c2 has been pushed to the Fedora EPEL 7 stable repository. If problem still persists, please make note of it in this bug report.
FEDORA-EPEL-2020-1790461e43 has been pushed to the Fedora EPEL 8 testing repository. You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2020-1790461e43 See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2020-2d994b986d has been pushed to the Fedora 33 testing repository. In short time you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2020-2d994b986d` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2020-2d994b986d See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2020-aea86f913e has been pushed to the Fedora 31 testing repository. In short time you'll be able to install the update with the following command: `sudo dnf upgrade --enablerepo=updates-testing --advisory=FEDORA-2020-aea86f913e` You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-2020-aea86f913e See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.
FEDORA-2020-2d994b986d has been pushed to the Fedora 33 stable repository. If problem still persists, please make note of it in this bug report.
FEDORA-2020-aea86f913e has been pushed to the Fedora 31 stable repository. If problem still persists, please make note of it in this bug report.
FEDORA-EPEL-2020-1790461e43 has been pushed to the Fedora EPEL 8 stable repository. If problem still persists, please make note of it in this bug report.