Note: This is a public test instance of Red Hat Bugzilla. The data contained within is a snapshot of the live data so any changes you make will not be reflected in the production Bugzilla. Email is disabled so feel free to test any aspect of the site that you want. File any problems you find or give feedback at bugzilla.redhat.com.
Bug 1877268 - [REGRESSION] HW acceleration disabled
Summary: [REGRESSION] HW acceleration disabled
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora
Classification: Fedora
Component: chromium
Version: 32
Hardware: x86_64
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Tom "spot" Callaway
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
: 1878916 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2020-09-09 09:07 UTC by Stefan Becker
Modified: 2020-10-10 21:11 UTC (History)
5 users (show)

Fixed In Version: chromium-85.0.4183.102-1.fc32 chromium-85.0.4183.121-1.el7 chromium-85.0.4183.121-1.fc33 chromium-85.0.4183.121-1.fc31 chromium-85.0.4183.121-1.el8
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-09-19 22:39:29 UTC
Type: Bug
Embargoed:

Attachments (Terms of Use)

Description Stefan Becker 2020-09-09 09:07:13 UTC 
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.
Comment 1 Tom "spot" Callaway 2020-09-09 16:48:25 UTC 
Yup. Looks like chromium has two different copies of those files now. Looks like an easy fix (we just need to package both copies).
Comment 2 Stefan Becker 2020-09-11 05:54:06 UTC 
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.
Comment 3 Stefan Becker 2020-09-11 06:09:20 UTC 
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.
Comment 4 Tom "spot" Callaway 2020-09-14 22:07:46 UTC 
*** Bug 1878916 has been marked as a duplicate of this bug. ***
Comment 5 Fedora Update System 2020-09-18 18:18:01 UTC 
FEDORA-2020-59d3a84267 has been submitted as an update to Fedora 33. https://bodhi.fedoraproject.org/updates/FEDORA-2020-59d3a84267
Comment 6 Fedora Update System 2020-09-18 18:18:08 UTC 
FEDORA-2020-6fe1b505a5 has been submitted as an update to Fedora 31. https://bodhi.fedoraproject.org/updates/FEDORA-2020-6fe1b505a5
Comment 7 Fedora Update System 2020-09-18 18:18:15 UTC 
FEDORA-2020-9b9e8e5306 has been submitted as an update to Fedora 32. https://bodhi.fedoraproject.org/updates/FEDORA-2020-9b9e8e5306
Comment 8 Fedora Update System 2020-09-18 18:19:26 UTC 
FEDORA-EPEL-2020-dec199d5a2 has been submitted as an update to Fedora EPEL 7. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2020-dec199d5a2
Comment 9 Fedora Update System 2020-09-18 18:19:28 UTC 
FEDORA-EPEL-2020-b65eda12a7 has been submitted as an update to Fedora EPEL 8. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2020-b65eda12a7
Comment 10 Fedora Update System 2020-09-19 19:56:26 UTC 
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.
Comment 11 Fedora Update System 2020-09-19 22:39:29 UTC 
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.
Comment 12 Fedora Update System 2020-09-19 22:43:28 UTC 
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.
Comment 13 Fedora Update System 2020-09-19 22:58:47 UTC 
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.
Comment 14 Fedora Update System 2020-09-19 23:23:29 UTC 
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.
Comment 15 Fedora Update System 2020-09-25 16:34:50 UTC 
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.
Comment 16 Fedora Update System 2020-09-25 17:49:35 UTC 
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.
Comment 17 Fedora Update System 2020-09-25 18:12:26 UTC 
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.
Comment 18 Fedora Update System 2020-09-25 18:39:03 UTC 
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.
Comment 19 Fedora Update System 2020-10-01 00:16:17 UTC 
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.
Comment 20 Fedora Update System 2020-10-03 01:54:04 UTC 
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.
Comment 21 Fedora Update System 2020-10-10 21:11:27 UTC 
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.
Note You need to log in before you can comment on or make changes to this bug.