Netflix says no WidevineCDM, but it's there |
|||||||||||||
Issue description55.0.2841.0 (Official Build) canary (64-bit) Netfix used to work fine, now it doesn't. In an attempt to fix it, I deleted the WidevineCDM dir from user data, relaunched, visited chrome://components/, and hit the update button. It now says: Widevine Content Decryption Module - Version: 1.4.8.903 Status - Component updated But Netflix insists: Whoops, something went wrong... Missing Component We cannot find all the required components to play Netflix on this device. Please visit chrome://components, locate the WidevineCdm component, and click the "Check for update" button.
,
Aug 29 2016
I can repro (on Windows canary). I see Widevine CDM in chrome://plugins and chrome://components, just like Greg. I also see the "Register Widevine CDM with Chrome" message in chrome's log, so I don't think this is a component delivery issue - it looks like the component is present and healthy. Could it be an issue with Netflix or with Widevine 1.4.8.903? Is there a secondary site we can test this on?
,
Aug 29 2016
,
Aug 29 2016
OK, on a Surface Pro 3 running win10, M54.0.2840.0+CDM903, I cannot repro this. I then updated to CDM 55.0.2843.0, and it still works (even after clearing all licenses). On my corp'd system, M55.0.2843 doesn't work on : 1) NFLX 2) AIV (same failure to resolve keysystem com.widevine.alpha) 3) shaka demo app (same issue/root cause as above) however, it does work for YT premium content.
,
Aug 29 2016
I wondered if this was a bit9 issue and checked again on a machine with a bit9 exception; content still did not load. However, while doing so I noticed that Chrome was notifying me that JavaScript was blocked on the netflix page. As far as I can tell, I have no JavaScript blocking set up in the browser, and I don't see what policy Chrome might be under to cause that, but I suspect that is the root cause here.
,
Aug 29 2016
Jrummell@ is building debug build of CHrome for windows now to dig into this further. assigning to him. I've not been able to repro this issue at all on any non-corp machines running canary M55.0.2843.0. yet I can easily repro on NFLX on corp systems running same build. NOTE: jscript seems to be enabled/Allowed per settings chrome://settings/siteSettings/javascript, yet I still get omnibox prompt saying it's disabled. separate issue w/jscript being enabled per settings, but disabled per omnibox prompt.
,
Aug 29 2016
,
Aug 30 2016
ChromeContentRendererClient::OverrideCreatePlugin [1] calls PluginInfoMessageFilter::Context::DecidePluginStatus (via ChromeViewHostMsg_GetPluginInfo), and then calls ChromeContentRendererClient::CreatePlugin(). DecidePluginStatus() [2] does: 1) Calls GetSecurityStatus(), which returns 2=REQUIRES_AUTHORIZATION 2) Calls GetPluginContentSetting(), which returns 3=ASK 3) Calls PluginsFieldTrial::EffectiveContentSetting(), which returns 2=BLOCK So BLOCK is returned and passed to CreatePlugin() ddorwin@ mentioned ShouldUseJavaScriptSettingForPlugin(), which is supposed to use the JavaScript permission rather than the plugin permissions. However, the only place this value is used is to call DidBlockContentType(), after the plugin has been rejected. [1] https://cs.chromium.org/chromium/src/chrome/renderer/chrome_content_renderer_client.cc?l=571 [2] https://cs.chromium.org/chromium/src/chrome/browser/plugins/plugin_info_message_filter.cc?l=300
,
Aug 30 2016
Breakage introduced by: https://chromium.googlesource.com/chromium/src/+/c56e1750274cbd7efb5cba947421ec7c36379f3a
,
Aug 30 2016
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/ff96ea580802bcc6910c930d636a3d6edb82de9a commit ff96ea580802bcc6910c930d636a3d6edb82de9a Author: tommycli <tommycli@chromium.org> Date: Tue Aug 30 17:44:39 2016 [HBD] Fix Widevine breakage introduced by prior patch Breakage introduced by prior patch here: https://codereview.chromium.org/2208463002 We had split off GetPluginContentSetting into a utils file, but forgot to add the widevine header file include. This means that WIDEVINE_CDM_AVAILABLE is never defined, and the Widevine-treated-as-JavaScript for content settings clause is never activated, breaking Widevine on Corp machines. BUG= 641706 Review-Url: https://codereview.chromium.org/2295563002 Cr-Commit-Position: refs/heads/master@{#415339} [modify] https://crrev.com/ff96ea580802bcc6910c930d636a3d6edb82de9a/chrome/browser/plugins/plugin_filter_utils.cc
,
Aug 30 2016
,
Aug 30 2016
w00t! Changing milestone to M-54 since that's where the regression snuck in. Please request a merge once this is verified in a canary build. Thanks.
,
Aug 30 2016
Sounds good! Will wait for verification.
,
Aug 31 2016
55.0.2845.0 (Official Build) canary (64-bit) is working for me on my corp MBP.
,
Aug 31 2016
grt: Thanks. I added the merge request for 54.
,
Aug 31 2016
Your change meets the bar and is auto-approved for M54 (branch: 2840)
,
Aug 31 2016
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/b72492925daed3c67251162f73837be963d6ef1f commit b72492925daed3c67251162f73837be963d6ef1f Author: Tommy C. Li <tommycli@chromium.org> Date: Wed Aug 31 20:41:04 2016 [HBD] Fix Widevine breakage introduced by prior patch Breakage introduced by prior patch here: https://codereview.chromium.org/2208463002 We had split off GetPluginContentSetting into a utils file, but forgot to add the widevine header file include. This means that WIDEVINE_CDM_AVAILABLE is never defined, and the Widevine-treated-as-JavaScript for content settings clause is never activated, breaking Widevine on Corp machines. BUG= 641706 Review-Url: https://codereview.chromium.org/2295563002 Cr-Commit-Position: refs/heads/master@{#415339} (cherry picked from commit ff96ea580802bcc6910c930d636a3d6edb82de9a) Review URL: https://codereview.chromium.org/2298393002 . Cr-Commit-Position: refs/branch-heads/2840@{#79} Cr-Branched-From: 1ae106dbab4bddd85132d5b75c670794311f4c57-refs/heads/master@{#414607} [modify] https://crrev.com/b72492925daed3c67251162f73837be963d6ef1f/chrome/browser/plugins/plugin_filter_utils.cc
,
Aug 31 2016
Thank you grt & jrummell for diagnosis & verification. Closing.
,
Sep 1 2016
Verified the issue on Windows 10 and Mac 10.11.6 using 54.0.2840.8, its working fine now.Attached screen casts for reference. Hence added respective TE-Verified labels for the same.
,
Oct 27 2016
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/b72492925daed3c67251162f73837be963d6ef1f commit b72492925daed3c67251162f73837be963d6ef1f Author: Tommy C. Li <tommycli@chromium.org> Date: Wed Aug 31 20:41:04 2016 [HBD] Fix Widevine breakage introduced by prior patch Breakage introduced by prior patch here: https://codereview.chromium.org/2208463002 We had split off GetPluginContentSetting into a utils file, but forgot to add the widevine header file include. This means that WIDEVINE_CDM_AVAILABLE is never defined, and the Widevine-treated-as-JavaScript for content settings clause is never activated, breaking Widevine on Corp machines. BUG= 641706 Review-Url: https://codereview.chromium.org/2295563002 Cr-Commit-Position: refs/heads/master@{#415339} (cherry picked from commit ff96ea580802bcc6910c930d636a3d6edb82de9a) Review URL: https://codereview.chromium.org/2298393002 . Cr-Commit-Position: refs/branch-heads/2840@{#79} Cr-Branched-From: 1ae106dbab4bddd85132d5b75c670794311f4c57-refs/heads/master@{#414607} [modify] https://crrev.com/b72492925daed3c67251162f73837be963d6ef1f/chrome/browser/plugins/plugin_filter_utils.cc
,
Jan 21 2017
if you are trying to watch Netflix videos there just might be another way. You can just change the playback setting in your account and that can solve the problem with out content decryption module. You may use the article below it lays out step by step how to fix the error by changing the playback setting. article url http://edgtech.com/2017/01/12/how-to-fix-the-netflix-error-with-widevine-content-decryption-module/ |
|||||||||||||
►
Sign in to add a comment |
|||||||||||||
Comment 1 by grt@chromium.org
, Aug 27 2016