Hardware GPU Compositing not working, missing libGLESV2.so in snap package
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
| chromium-browser (Ubuntu) |
High
|
Olivier Tilloy |
Bug Description
chrome://gpu/
Graphics Feature Status
Canvas: Software only, hardware acceleration unavailable
Flash: Software only. Hardware acceleration disabled
Flash Stage3D: Software only. Hardware acceleration disabled
Flash Stage3D Baseline profile: Software only. Hardware acceleration disabled
Compositing: Software only. Hardware acceleration disabled
Multiple Raster Threads: Enabled
Out-of-process Rasterization: Disabled
OpenGL: Disabled
Hardware Protected Video Decode: Disabled
Rasterization: Software only. Hardware acceleration disabled
Skia Renderer: Enabled
Video Decode: Software only. Hardware acceleration disabled
Vulkan: Disabled
WebGL: Software only, hardware acceleration unavailable
WebGL2: Software only, hardware acceleration unavailable
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
Version Information
Data exported 2020-08-
Chrome version Chrome/85.0.4183.83
Operating system Linux 5.4.0-42-generic
Software rendering list URL https:/
Driver bug list URL https:/
ANGLE commit id unknown hash
2D graphics backend Skia/85 8ae885386e910cf
Command Line /snap/chromium/
[truncated]
Problems Detected for Hardware GPU
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
Log Messages
[31619:
[31619:
GpuProcessHost: The GPU process exited normally. Everything is okay.
[31627:
[31627:
[31627:
Launchpad Janitor (janitor) wrote : | #1 |
Changed in chromium-browser (Ubuntu): | |
status: | New → Confirmed |
Jose Mico (jose-mico) wrote : | #2 |
The bug was introduced in rev 1275 (85.0.4183.83).
Previous rev 1269 (84.0.4147.135) was working fine.
Olivier Tilloy (osomon) wrote : | #3 |
And this is fixed in revision 1279 (now in the stable channel).
The corresponding commit is https:/
Changed in chromium-browser (Ubuntu): | |
status: | Confirmed → Fix Released |
assignee: | nobody → Olivier Tilloy (osomon) |
importance: | Undecided → High |
Simon (sbentl) wrote : | #4 |
Thanks everyone, just updated on my machine and it is now working as expected.
Olivier Tilloy (osomon) wrote : | #5 |
For future reference, here is the corresponding upstream commit: https:/
Status changed to 'Confirmed' because the bug affects multiple users.