|
Bugzilla – Full Text Bug Listing |
| Summary: | WebGL and hardware acceleration not available in Chromium | ||
|---|---|---|---|
| Product: | [openSUSE] openSUSE Distribution | Reporter: | Deleted Name <deleted> |
| Component: | X11 Applications | Assignee: | Forgotten User sM9JzehKpy <forgotten_sM9JzehKpy> |
| Status: | RESOLVED FIXED | QA Contact: | E-mail List <qa-bugs> |
| Severity: | Major | ||
| Priority: | P5 - None | CC: | astieger, forgotten_sM9JzehKpy, wbauer |
| Version: | Leap 42.1 | ||
| Target Milestone: | --- | ||
| Hardware: | x86-64 | ||
| OS: | openSUSE 42.1 | ||
| Whiteboard: | |||
| Found By: | --- | Services Priority: | |
| Business Priority: | Blocker: | --- | |
| Marketing QA Status: | --- | IT Deployment: | --- |
| Bug Depends on: | |||
| Bug Blocks: | 966788 | ||
| Attachments: | Google Chrome and Chromium outputs of chrome://gpu | ||
|
Description
Deleted Name
2016-02-08 08:45:46 UTC
Just tested with Chromium version 48.0.2564.103 from http://download.opensuse.org/repositories/network:/chromium/openSUSE_Leap_42.1/ The issue remains. It seems I am again being sent back from code.google.com to here: https://code.google.com/p/chromium/issues/detail?id=585046#c6 They say "We don't provide support for those - please file a bug with your distribution, or reproduce the issue with your own build." (In reply to Name Deleted from comment #2) > It seems I am again being sent back from code.google.com to here: > > https://code.google.com/p/chromium/issues/detail?id=585046#c6 > > They say "We don't provide support for those - please file a bug with your > distribution, or reproduce the issue with your own build." Looks like the same issue as in Bug#966082. Btw, do you have vdpau-video installed? Try to remove that as a test. *** This bug has been marked as a duplicate of bug 966082 *** (In reply to Wolfgang Bauer from comment #3) > Looks like the same issue as in Bug#966082. I am not so sure. That bug is marked as fixed but it seems it is not. > Btw, do you have vdpau-video installed? Try to remove that as a test. I didn't have it installed. But I installed it after I read your reply. It didn't change anything. With or without it - the issue remains. (In reply to Name Deleted from comment #4) > (In reply to Wolfgang Bauer from comment #3) > > Looks like the same issue as in Bug#966082. > > I am not so sure. That bug is marked as fixed but it seems it is not. That bug has only been fixed for 13.2 by not patching chromium to use libva any more on 13.2. But you are using Leap 42.1, no? The stacktrace is exactly the same... I suppose it happens because libva fails to open the driver: libva info: VA-API version 0.38.0 libva info: va_getDriverName() returns 0 libva info: Trying to open /usr/lib64/dri/nvidia_drv_video.so libva info: va_openDriver() returns -1 (In reply to Wolfgang Bauer from comment #5) > That bug has only been fixed for 13.2 by not patching chromium to use libva > any more on 13.2. > But you are using Leap 42.1, no? Thanks for explaining. Yes, I am using Leap 42.1. I hope you can fix this :) (In reply to Name Deleted from comment #6) > Yes, I am using Leap 42.1. I hope you can fix this :) I'm not a chromium maintainer. But it seems like it would be a good idea to remove libva support completely again. I hope someone else can do it then. Thanks. Ok. I removed the libva patch completely. I wasn't really happy with this patch in the first place, but the submitter indicated that it wouldn't do any harm and that he tested, etc. Unfortunately it seems that this might be true on Tumbleweed, but for the older builds this is definitely not the case. Also I know already that future chromium builds will no longer build with this patch, so it was just a matter of time before it got disabled. As soon as the build in network:chromium is finished, I will push it out as a maintenance update. (In reply to Raymond Wooninck from comment #9) > As soon as the build in network:chromium is finished, I will push it out as > a maintenance update. Sounds great Raymond! Thanks a lot. Looking forward to it. (In reply to Raymond Wooninck from comment #9) > Unfortunately it seems that this might be true on Tumbleweed, but for the > older builds this is definitely not the case. Well, it might also depend on the actual graphics card/driver that's being used, I suppose... In my particular case it is GTX680 with latest drivers from nVidia. But I suppose this is visible on the screenshots. I have just upgraded to chromium-48.0.2564.103-830.2.x86_64 Visiting chrome://gpu now shows that hardware acceleration is working. Thanks! In section "Problem Detected" there are these: Problems Detected 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 Linux NVIDIA drivers don't have the correct defaults for vertex attributes: 351528 Applied Workarounds: init_vertex_attributes Always rewrite vec/mat constructors to be consistent: 398694 Applied Workarounds: scalarize_vec_and_mat_constructor_args MakeCurrent is slow on Linux with NVIDIA drivers Applied Workarounds: use_virtualized_gl_contexts NVIDIA fails glReadPixels from incomplete cube map texture: 518889 Applied Workarounds: force_cube_complete Is that normal? Or is there anything more to fix? This is an autogenerated message for OBS integration: This bug (965566) was mentioned in https://build.opensuse.org/request/show/359487 13.1 / chromium I think this latest update created another bug which I reported separately: https://bugzilla.suse.com/show_bug.cgi?id=966788 releasing update (In reply to Andreas Stieger from comment #16) > releasing update Thank you. openSUSE-SU-2016:0491-1: An update that fixes 6 vulnerabilities is now available. Category: security (moderate) Bug References: 965566,965738,965999,966082 CVE References: CVE-2016-1622,CVE-2016-1623,CVE-2016-1624,CVE-2016-1625,CVE-2016-1626,CVE-2016-1627 Sources used: SUSE Package Hub for SUSE Linux Enterprise 12 (src): chromium-48.0.2564.109-49.1 openSUSE-SU-2016:0518-1: An update that fixes 6 vulnerabilities is now available. Category: security (moderate) Bug References: 965566,965738,965999,966082 CVE References: CVE-2016-1622,CVE-2016-1623,CVE-2016-1624,CVE-2016-1625,CVE-2016-1626,CVE-2016-1627 Sources used: openSUSE 13.1 (src): chromium-48.0.2564.109-125.1 |