libwidevincdm.so not detected chromium
Reported by
alf...@gmail.com,
Dec 7
|
||||
Issue descriptionUserAgent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:63.0) Gecko/20100101 Firefox/63.0 Example URL: sites that shows drm content Steps to reproduce the problem: 1. get the libwidevinecdm.so from same version of chrome 2. move the libwidevinecdm.so into the folder /usr/lib/chromium 3. what ever you do, it will not be detected by chromium What is the expected behavior? well, should it not be detected? What went wrong? Well sites that shows drm content will not work Does it occur on multiple sites: Yes Is it a problem with a plugin? Yes libwidevincdm.so Did this work before? Yes version 69 of chromium Does this work in other browsers? Yes Chrome version: Version 71.0.3578.80 Channel: dev OS Version: Debian Buster/Sid Flash Version: non
,
Dec 11
alfton@ Thanks for the issue. Request you to provide a sample file/URL, where this issue can be reproduced, which will help in further triaging. Thanks..
,
Dec 11
https://bitmovin.com/demos/drm nice place to check, this page show you if the plugin is activated
,
Dec 17
,
Dec 17
Widevine CDM is not officially supported in Chromium. Please consider to use Google Chrome or other supported browsers to get Widevine CDM support.
,
Dec 21
Does it mean it was intentionally made not to work? Or you'll accept fixes if provided even if you won't work on it? I have no interest in using Google Chrome, as Google Chrome is not built with VAAPI support on Linux and thus cannot be efficiently used for video decoding/encoding. So the choice you leave me is either use Google Chrome with Widevine but not hardware accelerated VAAPI decoding/encoding, or Chromium with VAAPI but no Widevine. Pardon me, but it sounds eerily like intentionally breaking undesirable OSS functionality in the style of Microsoft circa 1990s. I really hope it's not. I really hope it's just an issue with f170c737755811ca5d7ded0700d8aa17ec310024 where Widevine build flags were changed. ``` - Add ENABLE_WIDEVINE buildflag - Check BUILDFLAG(ENABLE_WIDEVINE) instead of defined(WIDEVINE_CDM_AVAILABLE) - Since WIDEVINE_CDM_AVAILABLE is not needed, remove a lot of dependencies on widevine_cdm_version.h - widevine_cdm_version.h is still needed to get WIDEVINE_CDM_VERSION_STRING and WIDEVINE_CDM_MIN_GLIBC_VERSION. - Some BUILD.gn cleanup to use "enable_widevine". Previously this wasn't possible since WIDEVINE_CDM_AVAILABLE is a define. - Remove third_party/widevine/cdm/stub/, whose sole purpose was to define WIDEVINE_CDM_AVAILABLE when "enable_widevine" is enabled. ```
,
Dec 21
We do not usually accept patches for features that are not enabled by default, since it can be a significant maintenance burden. You are free to build your own patched versions of Chromium, and to use those builds if you have the appropriate licenses to do so in your jurisdiction.
,
Dec 22
@OP The issue has been "fixed" in Chromium VAAPI in Fedora distro if you're interested. Relevant patches: https://pkgs.rpmfusion.org/cgit/free/chromium-vaapi.git/commit/?h=f29&id=bf8d2ade7d78d817705b2b6cd42567b22c2e68d3 |
||||
►
Sign in to add a comment |
||||
Comment 1 by gov...@chromium.org
, Dec 7