Do more on the web, with a fast and secure browser!

Download Opera browser with:

  • built-in ad blocker
  • battery saver
  • free VPN
Download Opera
  • @maydin95 said in Widevine and Opera:

    @macfly1987 I read it from a Vivaldi developer in Vivaldi forum, he said there needs to be a manifest file but I have no what to do.

    You can try asking Ruari. He deals with Linux for Vivaldi and has written all those libffmpeg and widewine scripts for Vivaldi. He used to work for Opera too. If it's something that can be fixed outside Opera with the manifest thing, he probably knows how to do it.

  • @zekemx said in Widevine and Opera:

    In conclusion.. Opera doesn't work with widevine anymore (As of today), I hope the Opera Developers would explain why, but probably they don't care about linux users anymore.

    @ zekemx:- That's it in a nutshell. I read somewhere, not many days ago, that Opera has been bought out by one of the 'big boys'. Expect many more annoying changes like this over the next few releases; these people have made it crystal-clear that they are only going to support Windows exclusively.....because that's where the money is.

    Everybody else can go whistle. So; it looks like I, too, will be returning to Chrome again.

    Bloody annoying.....but at least Big Brother doesn't give you quite this many hoops to jump through for an overall 'experience'. And everything does work, with relatively little 'pain'.

    Mike. 😠

  • Hi guys, I have some good news ;-)
    I just checked it, and the problem looks to be solved in the latest developer version
    (68.0.3602.0 - "DNA-84335 [Linux] Widevine is not working due to changed path of"),
    when you provide proper path to Widevine's folder in the "widevine_config.json" file, for example "/usr/lib/chromium-browser/WidevineCdm".

  • Widewine works again in developer version (Version:68.0.3602.0). It seems that they have changed the format of widevine_config.json and now instead of poinitng to the library file, the addresses point to the WidevineCdm directory containing manifest.json file and _platform_specific directory. This would be by default /opt/google/chrome/WidevineCdm

  • The setup I did for Opera Stable (66) for libffmpeg and Widevine on Linux Mint 19.3 XFCE is this:

    • Install Google Chrome and Opera.

    • Create "/usr/lib/x86_64-linux-gnu/opera/lib_extra"

    • Place for Chromium 79 in the "lib_extra" folder. Got it from

    • Copy "opt/google/chrome/WidevineCdm" to the "lib_extra" folder.

    • Edit "/usr/lib/x86_64-linux-gnu/opera/resources/ffmpeg_preload_config.json" to be:

    • Edit "/usr/lib/x86_64-linux-gnu/opera/resources/widevine_config.json" to be:

               "preload": "/usr/lib/x86_64-linux-gnu/opera/lib_extra/WidevineCdm"
    • Uninstall Chrome and delete "/usr/lib/chromium-browser" for good measure.

    In testing, unlike "lib_extra" for ffmpeg, Opera does not not search for the Widevine lib or the Widevine folder in any other place besides what's in widevine_config.json. It doesn't even search in "~/.config/opera/WidevineCdm".

    (See (my reply/question to @jimunderscorep) for why I edited the config files so Opera only searches for its own copies of libffmpeg and widevine.)

  • Here's how I'm getting Widevine for Opera Stable without installing Chrome. It's based on

    wdm=$( cat versions.txt | tail -n1 )
    unzip $
    mkdir WidevineCdm
    mv manifest.json WidevineCdm
    mkdir "WidevineCdm/_platform_specific"
    mkdir "WidevineCdm/_platform_specific/linux_x64"
    mv "WidevineCdm/_platform_specific/linux_x64"

    Then, put the WidevineCdm folder in a spot Opera is looking for like /opt/google/chrome:

    sudo mkdir /opt
    sudo mkdir /opt/google
    sudo mkdir /opt/google/chrome
    sudo mv WidevineCdm /opt/google/chrome


    cat /usr/lib/x86_64-linux-gnu/opera/resources/widevine_config.json

    and make sure the first preload is exactly:

    "preload" : "/opt/google/chrome/WidevineCdm"

    If not, fix it.

  • Hi guys, the Widevine is fixed now also in the latest Opera stable for Linux.

  • @l33t4opera still you need to add file under lib_extra directory.

  • Hi @igitqara, yes, because the Opera itself doesn't provide H.264 codec in its "" lib in the package.

    Regarding the "lib_extra", the lib can be placed also in any custom folder. You can change the path to it in ffmpeg_preload_config.json file, which is located in the /path/to/opera's-install-root/resources folder.

  • I can confirm that widevine is working again on stable 66 🙂

    Have somebody figured out how to use widevine with snap version of Opera? It appears, that only reason it is not working, is that snaps don't have access to /opt/google/chrome. If devs provide alternative location for storing widevine, fe somewhere in /home folder snaps should also plays nicely with widevine.