search

flathub / com.brave.Browser

https://flathub.org/apps/details/com.brave.Browser
Mozilla Public License 2.0
42 stars 17 forks source link

Widevine not detected even though Widevine is Enabled in settings #357

Open shakeelansari63 opened 1 year ago

shakeelansari63 commented 1 year ago

I have widevine enabled in setting, still Netflix and other video streaming sites complain for DRM.

Widevine is Enabled - image

I have tried to Update widevine from brave://components image

But still getting Protected Content error on Netflix image

This is version of Brave installed from Flathub image

Let me know if you need any more detail

shakeelansari63 commented 1 year ago

Ran Brave from terminal and I see this error - image

May help you debugging the issue.

rany2 commented 1 year ago

This seems like a Zypak issue to me, does it work if you run with --disable-sandbox?

shakeelansari63 commented 1 year ago

Nope, --disable-sandbox option does not help. Same error

archerallstars commented 3 months ago

This issue is still happening on Brave v1.65.126, with Widevine Content Decryption Module v4.10.2710.0.

rany2 commented 3 months ago

BTW, I was mistaken; the flag is now --no-sandbox. Please try that instead

archerallstars commented 3 months ago

@rany2 Widevine works with --no-sandbox flag. I tested with Prime Video.

rany2 commented 3 months ago

@refi64 can you take a look, it seems like Zypak is broken with Widevine again. I'm setting ExposeWidevine to true in cobalt so I think it should be working?

archerallstars commented 3 months ago

What I found as a workaround is to allow filesystem=host-os, as shown in the screenshot below:

ss

But I don't know what's the security impact of allowing this. Does this make it less secure than the non-Flatpak version? But this should be more secure than the --no-sandbox flag, right?

rany2 commented 3 months ago

@archerallstars It's for sure more secure than --no-sandbox