desktop-packages team mailing list archive
-
desktop-packages team
-
Mailing list archive
-
Message #125396
[Bug 1463598] Re: Chromium 43 fails to use hardware acceleration
Same for me on nouveau:
Graphics Feature Status
Canvas: Software only, hardware acceleration unavailable
Flash: Software only, hardware acceleration unavailable
Flash Stage3D: Software only, hardware acceleration unavailable
Flash Stage3D Baseline profile: Software only, hardware acceleration unavailable
Compositing: Software only, hardware acceleration unavailable
Multiple Raster Threads: Unavailable
Rasterization: Software only, hardware acceleration unavailable
Threaded Rasterization: Unavailable
Video Decode: Software only, hardware acceleration unavailable
Video Encode: Software only, hardware acceleration unavailable
WebGL: Unavailable
Driver Bug Workarounds
clear_uniforms_before_first_program_use
count_all_in_varyings_packing
disable_post_sub_buffers_for_onscreen_surfaces
init_gl_position_in_vertex_shader
init_vertex_attributes
scalarize_vec_and_mat_constructor_args
use_current_program_after_successful_link
Problems Detected
GPU process was unable to boot: GPU access is disabled in chrome://settings.
Disabled Features: all
Always call glUseProgram after a successful link to avoid a driver bug: 349137
Applied Workarounds: use_current_program_after_successful_link
Program link fails in NVIDIA Linux if gl_Position is not set: 286468
Applied Workarounds: init_gl_position_in_vertex_shader
Clear uniforms before first program use on all platforms: 124764, 349137
Applied Workarounds: clear_uniforms_before_first_program_use
Mesa drivers in Linux handle varyings without static use incorrectly: 333885
Applied Workarounds: count_all_in_varyings_packing
Linux NVIDIA drivers don't have the correct defaults for vertex attributes: 351528
Applied Workarounds: init_vertex_attributes
Disable partial swaps on linux drivers: 339493
Applied Workarounds: disable_post_sub_buffers_for_onscreen_surfaces
Always rewrite vec/mat constructors to be consistent: 398694
Applied Workarounds: scalarize_vec_and_mat_constructor_args
Version Information
Data exported 6/20/2015, 10:20:04 AM
Chrome version Chrome/43.0.2357.81
Operating system Linux 3.19.0-18-generic
Software rendering list version 0
Driver bug list version 8.06
ANGLE commit id unknown hash
2D graphics backend Skia
Command Line Args --enable-strict-site-isolation --ignore-gpu-blacklist --no-default-browser-check --disk-cache-dir=/run/shm/user/chromium --enable-tab-audio-muting --enable-overlay-scrollbar --enable-pinch --flag-switches-begin --ignore-gpu-blacklist --flag-switches-end
Driver Information
Initialization time 0
Sandboxed false
GPU0 VENDOR = 0x10de, DEVICE= 0x0dfa
Optimus false
AMD switchable false
Driver vendor Mesa
Driver version 10.5.2
Driver date
Pixel shader version
Vertex shader version
Machine model name
Machine model version
GL_VENDOR nouveau
GL_RENDERER Gallium 0.4 on NVC1
GL_VERSION 3.0 Mesa 10.5.2
GL_EXTENSIONS
Window system binding vendor
Window system binding version
Window system binding extensions
Window manager Compiz
XDG_CURRENT_DESKTOP Unity
GDMSESSION ubuntu
Compositing manager Yes
Direct rendering Yes
Reset notification strategy 0x0000
GPU process crash count 0
Before that everything worked fine. Now watching videos sucks, because of the tearing. Simply put: the browser is unusable for me.
Like comment #12 said: It seems the gpu flag was deliberately disabled by the ubuntu maintainer, a step that renders the browser unusable for me.
Everything worked fine without crashes before for me.
--
You received this bug notification because you are a member of Desktop
Packages, which is subscribed to chromium-browser in Ubuntu.
https://bugs.launchpad.net/bugs/1463598
Title:
Chromium 43 fails to use hardware acceleration
Status in chromium-browser package in Ubuntu:
Confirmed
Bug description:
After installing package chromium-browser 43.0.2357.81-0ubuntu0.14.04.1.1089 hardware acceleration becomes disabled.
I had no problem with previous chromium version.
Console output:
jose@jose:~$ chromium-browser
[3150:3191:0609/190556:ERROR:browser_gpu_channel_host_factory.cc(134)] Failed to launch GPU process.
[3150:3150:0609/190556:ERROR:url_pattern_set.cc(240)] Invalid url pattern: chrome://print/*
[3150:3191:0609/190556:ERROR:browser_gpu_channel_host_factory.cc(134)] Failed to launch GPU process.
[3150:3191:0609/190556:ERROR:browser_gpu_channel_host_factory.cc(134)] Failed to launch GPU process.
chrome://gpu:
Graphics Feature Status
Canvas: Software only, hardware acceleration unavailable
Flash: Software only, hardware acceleration unavailable
Flash Stage3D: Software only, hardware acceleration unavailable
Flash Stage3D Baseline profile: Software only, hardware acceleration unavailable
Compositing: Software only, hardware acceleration unavailable
Multiple Raster Threads: Unavailable
Rasterization: Software only, hardware acceleration unavailable
Threaded Rasterization: Unavailable
Video Decode: Software only, hardware acceleration unavailable
Video Encode: Software only, hardware acceleration unavailable
WebGL: Unavailable
Driver Bug Workarounds
clear_uniforms_before_first_program_use
count_all_in_varyings_packing
disable_chromium_framebuffer_multisample
disable_ext_occlusion_query
disable_post_sub_buffers_for_onscreen_surfaces
scalarize_vec_and_mat_constructor_args
Problems Detected
GPU process was unable to boot: GPU access is disabled in chrome://settings.
Disabled Features: all
- - -
Actually GPU access is *not* disabled from settings.
Workarounds like "--disable-gpu-sandbox" or "LIBGL_DRI3_DISABLE=1"
didn't helped at all.
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/chromium-browser/+bug/1463598/+subscriptions
References