Package Details: chromium-widevine 1:4.10.2449.0-1

Git Clone URL: (read-only, click to copy)
Package Base: chromium-widevine
Description: A browser plugin designed for the viewing of premium video content
Upstream URL:
Keywords: amazon chrome netflix prime webengine
Licenses: custom
Submitter: Scimmia
Maintainer: Scimmia
Last Packager: Scimmia
Votes: 420
Popularity: 1.58
First Submitted: 2015-04-17 05:05 (UTC)
Last Updated: 2022-05-10 20:41 (UTC)

Pinned Comments

Scimmia commented on 2020-05-18 23:20 (UTC)


This package is no longer needed for Chromium, it can download the component itself. With Chromium 81, you can either use this or let it download the component, but when Chromium 83 is updated in the Arch repos, it will ignore this package all together.

I'll maintain this package for a while for the other systems that use it.

Latest Comments

latisullivan commented on 2021-12-17 16:10 (UTC)

Thank god this package is still updated! Not sure if it's this one that did the trick or "qt5-webplugin-widevine". I installed both but I think this is the one that works.

I use Edge, and under Edge://flags, widevine is still unrecognized as a thing just like hardware encode/decode and video hardware acceleration ("unavailable on your platform"). Install this package and then just get to Netflix. No need to enable any flag or anything. Just restart the browser, maybe even the computer just in case (though not needed).

brody commented on 2021-07-16 08:32 (UTC)

If you increase the _chrome_ver and the pkgver is the same then you should also increase pkgrel.

josete commented on 2021-05-23 16:25 (UTC)

Done! Thanks a lot!

lucasgta95 commented on 2021-05-23 16:01 (UTC)

it's working on ungoogled chromium, just follow mlody_salceson comment after install...

josete commented on 2021-05-10 07:56 (UTC)

I have installed chromium-snapshot-bin but I have no idea how to enable the viewing of premium video content. I'm a newbie and my English knowledge is also limited. What must I do to enable this? Thanks!

bkb commented on 2021-03-22 09:24 (UTC)

Does it permit to use Netflix in 4K?

JstKddng commented on 2020-08-29 19:24 (UTC)

hey @Scimmia, I could take over and maintain this package if you are no longer interested or use it. Me and other people that use ungoogled-chromium still need this since ungoogled-chromium can't download this component. I also maintain ungoogled-chromium and I wouldn't mind maintaining this package as well.

LoganDark commented on 2020-08-28 02:19 (UTC)

Some sort of cp error currently prevents the build from working for me.

==> Making package: chromium-widevine 1:4.10.1679.0-1 (Thu 27 Aug 2020 06:53:08 PM PDT)
==> Checking runtime dependencies...
==> Checking buildtime dependencies...
==> Retrieving sources...
  -> Downloading google-chrome-stable_85.0.4183.83-1_amd64.deb...
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100 66.9M  100 66.9M    0     0  5702k      0  0:00:12  0:00:12 --:--:-- 7242k
==> Validating source files with sha256sums...
    google-chrome-stable_85.0.4183.83-1_amd64.deb ... Passed
==> Extracting sources...
  -> Extracting google-chrome-stable_85.0.4183.83-1_amd64.deb with bsdtar
==> Starting prepare()...
==> Starting pkgver()...
==> Entering fakeroot environment...
==> Starting package()...
cp: failed to preserve ownership for '/home/logandark/.cache/rua/build/chromium-widevine/pkg/chromium-widevine/usr/lib/chromium/WidevineCdm/_platform_specific/linux_x64': Invalid argument
cp: failed to preserve ownership for '/home/logandark/.cache/rua/build/chromium-widevine/pkg/chromium-widevine/usr/lib/chromium/WidevineCdm/_platform_specific': Invalid argument
cp: failed to preserve ownership for '/home/logandark/.cache/rua/build/chromium-widevine/pkg/chromium-widevine/usr/lib/chromium/WidevineCdm': Invalid argument
==> ERROR: A failure occurred in package().
Build failed with exit code 4 in /home/logandark/.cache/rua/build/chromium-widevine

here is a diff that fixes it:

diff --git a/PKGBUILD b/PKGBUILD
index acc2b43..ec9dcd7 100644
@@ -27,7 +27,7 @@ package() {
   depends=('gcc-libs' 'glib2' 'glibc' 'nspr' 'nss')

   install -dm755 "$pkgdir/usr/lib/"chromium{,-dev}/
-  cp -a WidevineCdm "$pkgdir/usr/lib/chromium/"
+  cp -R WidevineCdm "$pkgdir/usr/lib/chromium/"
   ln -s ../chromium/WidevineCdm "$pkgdir/usr/lib/chromium-dev/WidevineCdm"
   install -Dm644 WidevineCdm/LICENSE -t "$pkgdir/usr/share/licenses/$pkgname/"
 # backward compatibility

Perhaps this does not preserve the original intent of the command, but it works for me rather than failing with "invalid argument".

mlody_salceson commented on 2020-08-26 04:22 (UTC)

Hello, I am using ungoogled-chromium, but plugin didn't work for me. I have discovered it was lacking execute permissions on my system. After "sudo chmod a+x /usr/lib/chromium/WidevineCdm/_platform_specific/linux_x64/" the plugin loaded and worked fine. Thanks for maintaining the package!

Scimmia commented on 2020-08-23 13:57 (UTC)

I never said I would delete it, I just shouldn't be maintaining something long-term that I don't use.

AndyRTR, that would work if upstream didn't delete the packages when a new minor version was released.

AndyRTR commented on 2020-08-23 07:31 (UTC)

Please keep the package also for use with mellowplayer. No need to update at each minor chromium release. It should be sufficient to update only when the plugin gets a bump.

redfish commented on 2020-08-23 02:36 (UTC)

@Scimmia: please don't delete this package, it is the only way to have Widevine working in Opera browser. For extra details, see this bug report:

Scimmia commented on 2020-05-18 23:20 (UTC)


This package is no longer needed for Chromium, it can download the component itself. With Chromium 81, you can either use this or let it download the component, but when Chromium 83 is updated in the Arch repos, it will ignore this package all together.

I'll maintain this package for a while for the other systems that use it.

usuariopolivalen commented on 2020-04-20 17:07 (UTC)

plmosqueda commented on 2020-04-04 11:58 (UTC)

Tested today with lts kernel and Gnome desktop. Works good. Installed with a crappy AUR helper XDD

chrisco23 commented on 2020-01-17 12:20 (UTC)

At some point Netflix stopped working in my Chromium even with this AUR package. Everything I google just points me back to this package (installed and has been for a long time). Tired of running Firefox (or Chrome) for this sole purpose. Anybody have any ideas? Thanks.

Vrakfall commented on 2019-10-29 16:15 (UTC)

Ah you're right, thanks.

(Tho, said AUR helper is made by a TU :x )

Scimmia commented on 2019-10-29 14:56 (UTC)

Sounds like a crappy AUR helper. Works fine with makepkg.

Vrakfall commented on 2019-10-29 14:26 (UTC)

I've got these errors now if I try to build:

==> ERROR: pkgver is not allowed to contain colons, forward slashes, hyphens or whitespace.
==> ERROR: pkgver() generated an invalid version: ==> Starting pkgver()...

Scimmia commented on 2019-10-20 18:00 (UTC)

Looks like that change was made in chrome 78, which should be released in a matter of days. I think we'll wait for that and switch it all at once.

sl1pkn07 commented on 2019-10-20 13:23 (UTC) (edited on 2019-10-20 13:24 (UTC) by sl1pkn07)


please add also the new widevine structure comes with the chrome unstable (+79) until the stable merge it

diff --git a/PKGBUILD b/PKGBUILD
index 3a6b542..2564ea2 100644
@@ -17,13 +17,21 @@ conflicts=('chromium-widevine-dev')
+        ""
+            '9582f71c706d2de597fd9ca3e689e904cf43163911a8b3d81eb071eb27b1dff4'
+           'google-chrome-unstable_79.0.3938.0-1_amd64.deb')

 prepare() {
+  bsdtar -x -f google-chrome-unstable_79.0.3938.0-1_amd64.deb data.tar.xz
+  bsdtar -x --strip-components 4 -f data.tar.xz opt/google/chrome-unstable/WidevineCdm
+  bsdtar -x -f "google-chrome-stable_${_chrome_ver}-1_amd64.deb" data.tar.xz
   bsdtar -x --strip-components 4 -f data.tar.xz opt/google/chrome/
   gcc get_cdm_version.c -o get_cdm_version -ldl

@@ -33,7 +41,6 @@ pkgver() {

 package() {
   install -Dm644 -t "$pkgdir/usr/lib/chromium/"
-  install -d "$pkgdir/usr/lib/chromium-dev/"
-  ln -s ../chromium/ "$pkgdir/usr/lib/chromium-dev/"
+  for i in $(find WidevineCdm -type f); do install -Dm644 "${i}" "$pkgdir/usr/lib/chromium-dev/${i}"; done
   install -Dm644 chrome-eula_text-$_license_date.html "$pkgdir/usr/share/licenses/$pkgname/eula_text.html"

dqnh commented on 2019-10-18 18:59 (UTC)

If you really want to verify the contents of chrome-eula_text you could use something like sed 's/nonce=\".*\"//' but I don't think there is any point doing that since this is just a harmless EULA. Besides, you still would have to SKIP it and put the check elsewhere.

Vrakfall commented on 2019-10-18 14:37 (UTC)

Which seems to have been changed again? Or am I hallucinating?

Scimmia commented on 2019-10-18 14:00 (UTC)

Yes, nonce is going to be a real problem. I really don't like using SKIP for files, but I'm not seeing a good alternative in this case.

Segaja commented on 2019-10-18 13:41 (UTC)

From a security standpoint it makes no sense to calculate the checksum of a file that was just downloaded. IF the upstream server was compromised you would never know because you use the hash you just calculated from a corrupt file.

If you don't care about the hash (because it is an EULA file which is only in the package for legal reasons) you would be better of using just "SKIP" in the place of the checksum in the sha256sums array.

xuanruiqi commented on 2019-10-18 11:05 (UTC)

It wouldn't hurt to make the checksum 'SKIP'...

dari-it commented on 2019-10-18 10:33 (UTC) (edited on 2019-10-18 14:02 (UTC) by dari-it)

I changed the sha256sums-array in PKGBUILD:

sha256sums=( $(sha256sum chrome-eula_text-$_license_date.html | cut -d ' ' -f 1) '07abdccd7c15f5abe68765c1162f2ab666b6478a4d578aa6351d5667cd983a48' '3fda44a5b8b222434530f27923568de1fda1eb0caa8621b56a8b2a6a2a2e3d5d' )

The first entry calculates the hash now directly from downloaded eula-file... installation works.

UPDATE: Segaja is right. Generally it is a bad idea to recalculate the hash value of a downloaded file. But it's just an EULA file in this case, so I see no problem.

I didn't know you could insert 'SKIP'... This would be also a solution, of course.

p4c0m3yp4b3b3 commented on 2019-10-18 10:16 (UTC)

To avoid errors in checksums do this: yay -S --mflags --skipinteg chromium-widevine

nightuser commented on 2019-10-18 10:15 (UTC)

Same error here. I think this nonce value should be stripped of the package in order for the package to be reproducible.

xuanruiqi commented on 2019-10-18 10:03 (UTC)

Getting an error with checksums:

==> Validating source files with sha256sums...
chrome-eula_text-20191018.html ... FAILED
google-chrome-stable_77.0.3865.120-1_amd64.deb ... Passed
get_cdm_version.c ... Passed
==> ERROR: One or more files did not pass the validity check!

compguy284 commented on 2019-10-18 07:07 (UTC) (edited on 2019-10-18 07:32 (UTC) by compguy284)

The sha256sum for chrome-eula_text will keep changing now since it now has random nonce values generated by the server.

--- chrome-eula_text-20191017.html  2019-10-17 22:00:00.000000000 -0400
+++ chrome-eula_text-20191017a.html 2019-10-17 22:00:00.000000000 -0400
@@ -19,7 +19,7 @@
 <title>Google Chrome Terms of Service</title>
 <link href="" rel="icon" type="image/ico">
 <link href="" rel="canonical"> <!--[if (gte IE 10)|!(IE)]><!-->
-            <script nonce="B3sWAT0dO7y-QPVInYo8Nw">
+            <script nonce="LJJDTqDbWmaxs7XFm-my7A">
     (i[r].q=i[r].q||[]).push(arguments)},i[r].l=1*new Date();a=s.createElement(o),
@@ -32,7 +32,7 @@
     linkSelector: 'a:not([ga-on])',
-            <script async src="" nonce="B3sWAT0dO7y-QPVInYo8Nw"></script> <!--<![endif]--><!--[if lte IE 9]>
+            <script async src="" nonce="LJJDTqDbWmaxs7XFm-my7A"></script> <!--<![endif]--><!--[if lte IE 9]>
             <script src="//"></script>
             <script> = new{
@@ -40,12 +40,12 @@
     cookiePath: '/chrome/'
 </script> <![endif]--><!-- Google Tag Manager -->
-            <script nonce="B3sWAT0dO7y-QPVInYo8Nw">(function(w,d,s,l,i){w[l]=w[l]||[];w[l].push({'gtm.start':
+            <script nonce="LJJDTqDbWmaxs7XFm-my7A">(function(w,d,s,l,i){w[l]=w[l]||[];w[l].push({'gtm.start':
 new Date().getTime(),event:'gtm.js'});var f=d.getElementsByTagName(s)[0],
 })(window,document,'script','dataLayer','GTM-PZ6TRJB');</script><!-- End Google Tag Manager -->
-<link rel="stylesheet" href="/chrome/static/css/main.v2.min.css" nonce="B3sWAT0dO7y-QPVInYo8Nw">
+<link rel="stylesheet" href="/chrome/static/css/main.v2.min.css" nonce="LJJDTqDbWmaxs7XFm-my7A">

j.taala commented on 2019-10-18 06:49 (UTC) (edited on 2019-10-18 06:59 (UTC) by j.taala)

sha256 for the first file that is sourced (chrome-eula_text-20191018.html) should be 08d31de581547c896cce01a4aea70cc87696410635a8516d58d171e0fdc82fba

Looks like google updated the eula (now at 20191018), which in the PKGBUILD is found by the last modified date but (of course) the sha256 in the PKGBUILD (for the first file) is now incorrect.

I've updated on my local repo and have tested - installed fine after the corrected sha256.

kouros17 commented on 2019-10-18 06:24 (UTC) (edited on 2019-10-18 06:26 (UTC) by kouros17)

I tried to install 1:4.10.1503.4-2 but:

"ERROR: One or more files did not pass the validity check!"

Musikolo commented on 2019-09-22 04:50 (UTC) (edited on 2019-09-22 04:57 (UTC) by Musikolo)

@Scimmia, I'm sorry for the confusion, but I didn't expect anybody to delete the repo immediately afterwards. If I had known that was the intention, I would have done some more tests to fully confirm. This said, I'll restore the repo, although as you said, all votes and comments will be gone.

Thank you.

Scimmia commented on 2019-09-21 23:14 (UTC) (edited on 2019-09-21 23:38 (UTC) by Scimmia)

You specifically said that you didn't need vivaldi-widevine if you had chromium-widevine installed. Now you're saying that's not the case? A previous comment from someone else had said that it worked, too :(.

The git repo for vivaldi-widevine would still exist, so remaking it is simple, but the votes and comments are gone. It should remove chromium-widevine from the conflicts, too, in that case (it never actually conflicted).

It looks like vivaldi comes with an update-widevine program, where does it put it? If it really has to be in /opt/google/chrome/, what would you think of just having a symlink in a separate package, so we aren't duplicating effort? I'm not willing to make this conflict with google-chrome.

Musikolo commented on 2019-09-21 23:07 (UTC)

@Scimmia, I think I might make a mistake in my previous answer. To the point I've been able to find out, Vivaldi is only able to find out widevine plugin under /opt/google/chrome/. So, using chromium-widevine as a replacement of vivaldi-widevine doesn't work currently. The reason is that chromium-widevine places the plugin under /usr/lib/chromium/. However, by just creating a symlink -> /usr/lib/chromium/ under /opt/google/chrome/ solves the problem. Without it, it simply doesn't work to me.


Musikolo commented on 2019-09-21 03:34 (UTC)

@Scimmia, that's the reason why this package conflicts with chromium-widevine and google-chrome packages. In other words, if you have already one of these, you don't need vivaldi-widevine.

Thank you.

Scimmia commented on 2019-09-20 04:47 (UTC)

So vivaldi finds the plugin in /usr/lib/chromium/? This is now just a duplicate of chromium-widevine?

Musikolo commented on 2019-09-20 02:17 (UTC)

Updated to version 4.10.1503.4.


Scimmia commented on 2019-07-20 02:51 (UTC)

That's going to differ from this PKGBUILD in pretty much every way. Not really something that's doable in this package.

Musikolo commented on 2019-07-20 02:26 (UTC)

@manuel-192, although _chrome_ver doesn't have the latest version, it still contains the very same version of widevine plugin. So, the same binary is packaged regardless. Because of this, I'll reset the out-of-date flag.

Thank you.

nikost74 commented on 2019-07-19 21:03 (UTC)

I've edited my previous comment.

Scimmia commented on 2019-07-19 20:07 (UTC)

Based on what upstream binary?

nikost74 commented on 2019-07-19 19:32 (UTC) (edited on 2019-07-19 21:03 (UTC) by nikost74)

Is there any possibility to adding more architectures for this package? I am trying to find a way to install widevine in an armv7l raspberry pi 3 device.

Based on

Working version for rpi3 at the time of writing:

name=HP Chromebook 11 G1 version=11316.165.0 desc= channel=stable-channel hwidmatch=^SPRING .* hwid= md5=782b70f5d4ba26c5f3b6488a8c875626 sha1=55b62ce5ae1e3f646c42b92f30e21c976873ac9d zipfilesize=589868247 file=chromeos_11316.165.0_daisy-spring_recovery_stable-channel_spring-mp-v3.bin filesize=1526751232 url=

Scimmia commented on 2019-07-17 19:58 (UTC)

bennypr0fane, sl1pkn07 doesn't have anything to do with this, and '@' doesn't do anything, anyway. No idea what yay is doing, does it work with makepkg? If so, talk to the yay people.

bennypr0fane commented on 2019-07-17 16:21 (UTC)

@sl1pkn07 Upgrading this package with yay, there's an error downloading chrome-eula_text-20190626.html: it finds "chrome-eula_text-.html" instead

Musikolo commented on 2019-06-21 01:46 (UTC)

Updated to version 4.10.1440.18.


zerophase commented on 2019-06-04 18:25 (UTC)

So, it looks like you cannot remove this plugin through the Chromium / Brave UI. Should installing this package, and then uninstalling it remove the unremovable WideVine install if done through a Chromium based browser?

Scimmia commented on 2019-04-09 12:36 (UTC)

Doesn't really answer the question, though.

sl1pkn07 commented on 2019-04-09 09:43 (UTC)

This package is autoupgradeable when is reinstalled. The only thing is the eula checksum, can will fail. I can bump if you think is a problem


Scimmia commented on 2019-04-09 05:21 (UTC) (edited on 2019-04-09 05:22 (UTC) by Scimmia)

This doesn't seem to ship a different version anymore, and without the adapter, it's not tied to a specific version of chromium. Is there any reason for this to be separate from chromium-widevine? If a symlink would do the job, i could ship that.

Musikolo commented on 2019-03-28 02:03 (UTC)

Updated to version 4.10.1303.2.


Musikolo commented on 2019-02-14 02:59 (UTC)

@bartus, thanks for your head up. I've reviewed and updated the depends array. Please, try the following steps and let me know if you find any additional issues:

wget && \
tar xvfz vivaldi-widevine.tar.gz && \
cd vivaldi-widevine && \
makepkg -crsi


bartus commented on 2019-02-13 08:13 (UTC) (edited on 2019-02-13 08:17 (UTC) by bartus)

==> Making package: vivaldi-widevine 1:4.10.1303.0-3 (Wed 13 Feb 2019 09:04:52 AM CET)
==> Checking runtime dependencies...
==> Installing missing dependencies...
resolving dependencies...
looking for conflicting packages...

Packages (1) vivaldi-ffmpeg-codecs-71.0.3578.98-1

Total Installed Size:  3.41 MiB

:: Proceed with installation? [Y/n]
warning: couldn't find or create package cache, using /tmp/ instead
(1/1) checking keys in keyring                                                                                                                  [########################################################################################] 100%
(1/1) checking package integrity                                                                                                                [########################################################################################] 100%
(1/1) loading package files                                                                                                                     [########################################################################################] 100%
(1/1) checking for file conflicts                                                                                                               [########################################################################################] 100%
:: Processing package changes...
(1/1) installing vivaldi-ffmpeg-codecs                                                                                                          [########################################################################################] 100%
==> Checking buildtime dependencies...
==> Retrieving sources...
  -> Found chrome-eula_text.html
  -> Found google-chrome-stable_72.0.3626.81-1_amd64.deb
  -> Found get_cdm_version.c
==> WARNING: Skipping all source file integrity checks.
==> Extracting sources...
  -> Extracting google-chrome-stable_72.0.3626.81-1_amd64.deb with bsdtar
==> Starting prepare()...
==> Starting pkgver()...
==> ERROR: pkgver is not allowed to contain colons, forward slashes, hyphens or whitespace.
==> ERROR: pkgver() generated an invalid version: cannot open shared object file: No such file or directory
==> Removing chroot copy [/tmp/x86_64/bartus-32480]...done
==> ERROR: Build failed

Build process desn't pull vivladi as deps so it's not present during pgkver invocation - in result producing after mentioned error.

Musikolo commented on 2019-02-12 02:36 (UTC)

@Joel, the issue should be fixed. Thanks for the heads up!

Regarding your last comment, this package conflicts with chromium-widevine and google-chrome due to the fact they also ships widevine codec files. So, either this or any of the conflicting packages is required.

Thank you!

Musikolo commented on 2019-02-12 02:25 (UTC)

@bartus, nss is required by vivaldi. This said, can you please share the error log you get exactly?

Thank you.

Joel commented on 2019-02-11 15:13 (UTC)

sha256sum fails for chrome-eula_text.html

pheerai is right, I removed vivaldi-widevine package and vivaldi uses my chromium plugin to play the content.

bartus commented on 2019-02-11 11:09 (UTC)

Won't build in a clean chroot: requires nss for pkgver to work.

Bryanpwo commented on 2019-02-07 08:11 (UTC)

@Musikolo Thank you!

Musikolo commented on 2019-02-07 04:20 (UTC)

@Mimicking, thanks for the heads up. The issue should be fixed now.

Thank you!

Mimicking commented on 2019-02-07 04:09 (UTC)

install: cannot stat 'opt/google/chrome/': No such file or directory

Musikolo commented on 2019-02-07 02:44 (UTC)

Updated to version 4.10.1303.0.


Bryanpwo commented on 2019-02-06 10:41 (UTC)

This package can't be installed, the chrome eula didn't pass validation.

Scimmia commented on 2019-01-06 18:20 (UTC)

We've tried the direct download before, it ended up very, very rarely being updated.

oxalin commented on 2019-01-06 06:34 (UTC)

May I suggest to use the following link to download widevine only instead of the full Chrome package:

The 4.10.1196.0 should be updated to use the latest version available though.

This trick was taken from a script used by Vivaldi. See:

Scimmia commented on 2018-12-20 18:46 (UTC)

Deps can't be runtime-only now that we're dlopening the lib. Should be fixed now.

bartus commented on 2018-12-20 18:19 (UTC)

Won't build in chroot.

requires makedepends=('nss')

wooque commented on 2018-12-15 22:26 (UTC)

@fourtelis Thanks works great

Musikolo commented on 2018-12-14 02:57 (UTC)

@blonade24, according to Vivaldi changelog, it shouldn't be needed anymore. However, after removing vivaldi-widevine package, I cannot reproduce DRM videos anymore. I tried using this link ( and Netflix. None worked for me without this package. As soon as I installed it back, everything worked again. So, I'll try in the future again, and as soon as I'm able to make it work without out this package, I'll let everyone know and disown it.

Thank you!

bionade24 commented on 2018-12-13 15:23 (UTC)

Is this needed for any purpose after Vivaldi 2.2 ships widevine with it?

foutrelis commented on 2018-12-05 21:57 (UTC)

Possibly an overkill but works nicely:

Scimmia commented on 2018-12-05 19:01 (UTC)

They've changed the version information in the plugin included in chrome 71. Not sure how I'm going to deal with it yet, just searching for the numerical pattern doesn't seem like a good idea. For now, I've flagged it out of date while I figure out how to handle it.

Honer08 commented on 2018-11-29 09:47 (UTC)

These instructions in the following URL to use this Package, worked great for me.

Musikolo commented on 2018-11-27 02:17 (UTC)

@bkuri, the integrity check of the file chrome-eula_text.html was removed intentionally due constant changes. You can see when this was done at

I don't think it's worth restoring the integrity check of this file, since it's just a text file (not a binary file) and it's more a burden than anything truly beneficial. We might review this in the future though.

Thank you!

bkuri commented on 2018-11-27 01:15 (UTC)

@Musikolo here's the latest sha256sum for chrome-eula_text.html: e93c01576427cad9099f2cf0df0be70d0a2cc0a3a66c743318b2138aa7c4ed93

RainmakerRaw commented on 2018-11-24 21:18 (UTC)

@Musikolo Thank you, for the speedy and efficient maintenance of the package!

Musikolo commented on 2018-11-24 16:43 (UTC)

@RainmakerRaw, thanks for the heads up.

The issue should be solved now.

Thank you!

RainmakerRaw commented on 2018-11-24 13:20 (UTC)

Latest version is failing integrity check.

==> Validating source files with sha256sums... chrome-eula_text.html ... Skipped google-chrome-_4.10.1196.0_amd64.deb ... FAILED ==> ERROR: One or more files did not pass the validity check! ==> ERROR: Makepkg was unable to build vivaldi-widevine.

Musikolo commented on 2018-11-14 04:28 (UTC)

Updated to version 4.10.1196.0.


gugu2077 commented on 2018-10-14 00:19 (UTC) (edited on 2018-10-14 00:33 (UTC) by gugu2077)

==> Validating source files with sha1sums...
eula_text.html ... FAILED
google-chrome-unstable-71.0.3573.0-1.x86_64.rpm ... Passed
==> ERROR: One or more files did not pass the validity check!

yay -S chromium-widevine-dev --mflags "--skipchecksums"

==> Removing existing $srcdir/ directory...
==> Extracting sources...
==> Starting prepare()...
==> Starting pkgver()...
==> ERROR: pkgver is not allowed to be empty.
==> ERROR: pkgver() generated an invalid version:
Error making: chromium-widevine-dev

commented on 2018-10-07 17:02 (UTC)

Yes it is fixed. Thanks for the quick response and maintenance of this package.

Musikolo commented on 2018-10-07 14:52 (UTC)

@erikduboi, the issue should be fixed now. I've decided to skip the integrity check of eula_text.html file due to constant changes.

commented on 2018-10-07 13:15 (UTC)

There is a wrong checksum. This works.

Musikolo commented on 2018-09-28 01:47 (UTC)

Updated to version 4.10.1192.0.


Musikolo commented on 2018-09-19 00:35 (UTC)

@hades0299, if you want to get notified when a comment is made, please make sure you click on the "Enable notifications" link available in the "Package Actions" box above on the right.

I hope it helps! ;-)

hades0299 commented on 2018-09-18 11:11 (UTC) (edited on 2018-09-18 11:12 (UTC) by hades0299)

@Musikolo: sry for the late reply (why is there no automatic notification-email for comments after oneself comments?), but it works now. Thanks you :)

Musikolo commented on 2018-09-08 23:24 (UTC)

@Nazushvel / @hades0299, I've just added the temporary link provided below. Checksum for license changes due to an update, while it remains the same for the deb binary file.

Please, let me know if anything else is needed.

Thank you!

Nazushvel commented on 2018-09-07 06:42 (UTC)

Found it: passed the checks however the eula also needs then sha updated. I just used the one from the chromium-widevine.

Installation finished without any other issues.

Musikolo commented on 2018-09-07 04:31 (UTC)

@hades0299, yes, unfortunately current version is no longer available. I don't know about any other location where the same file can be downloaded from. If anybody knows, I could update the package accordingly.

I'm sorry for the inconveniences, but I'm afraid we'll have to wait for Vivaldi 16 to come out which should be compatible with the latest version of widevine.

Thank you.

hades0299 commented on 2018-09-05 09:25 (UTC)

It seems that the download-link for the .deb returns a 404, so installation is not possible.

compgamer89 commented on 2018-09-03 11:24 (UTC) (edited on 2018-09-03 11:35 (UTC) by compgamer89)

Suggested change:

Don't use the "live" EULA on the Google website. It contains analytics (privacy concern?) and may change unpredictably. Better to use the static EULA from the version matching the binary blob (which also contains the same EULA, but compiled into an internationalized .pak file).

As a secondary benefit, doing so removes need for web access other than source download phase. This is useful because fakeroot and curl don't work well together (DNS resolution breaks under fakeroot).

diff --git a/PKGBUILD b/PKGBUILD
index 767cef8..7db5f78 100644
@@ -4,18 +4,16 @@ pkgname=chromium-widevine
 pkgdesc='A browser plugin designed for the viewing of premium video content'
-_license_date=$(curl -sI | awk '/^last-modified/ {print $3" "$4" "$5}' | date +"%Y%m%d" -f -)
-        "${_chrome_ver}-1_amd64.deb")
-            'b2dd6af541bf4f44b65d487f7b208ee5ae922c78800d6d21786098c055156534')
+        "chrome-eula_text-${_chrome_ver}.html::${_chrome_ver}/components/resources/terms/terms_en.html")
+            'ac69df44067135997f7efe3af46279962690dba5a3c1154054c1e1c06b5228f8')

 prepare() {
   bsdtar -x --strip-components 4 -f data.tar.xz opt/google/chrome/
@@ -29,5 +27,5 @@ package() {
   depends=('chromium' 'gcc-libs' 'glib2' 'glibc' 'nspr' 'nss')

   install -Dm644 -t "$pkgdir/usr/lib/chromium/"
-  install -Dm644 chrome-eula_text-$_license_date.html "$pkgdir/usr/share/licenses/$pkgname/eula_text.html"
+  install -Dm644 chrome-eula_text-${_chrome_ver}.html "$pkgdir/usr/share/licenses/$pkgname/eula_text.html"

Musikolo commented on 2018-08-28 03:03 (UTC)

@Scimmia, yes, I see know. Sorry for the confusion.

I've googled a bit about it, and I've found this: -

I hope it's helpful!

Scimmia commented on 2018-08-28 02:42 (UTC)

You missed my point. The pinned comment says that vivaldi will find and use the plugin installed by google-chrome, that doesn't appear to be true at this time if it can't use the current version.

As for chromium-widevine, check who the submitter and maintainer is on that.

Musikolo commented on 2018-08-28 01:32 (UTC)

@Scimmia, Google Chrome comes with this plugin embedded, so there is no need of external plugin installation. In addition, this package is only for Vivaldi browser. If you need it for Chromium, you should use instead.

I hope this clarifies everything.

Thank you!

Scimmia commented on 2018-08-27 04:43 (UTC)

So a google-chrome install will no longer work, either. I hope this is just a one-time change in how the plugin is handled upstream and not an ongoing problem.

Musikolo commented on 2018-08-27 03:34 (UTC)

@Scimmia, version 4.10.1146.0 requires Chromium 68 which is not shipped in Vivaldi yet. I tried that version of widevine some weeks ago, and it didn't work for me. As soon as a Vivaldi-compatible version is released, I'll update widevine.

Thank you!

xuiqzy commented on 2018-08-16 10:06 (UTC)

Please change the source url from google to TLS encrypted https variant, tested it and works! Thanks :)

But there is a checksum error:

==> Validating source files with sha1sums... eula_text.html ... FAILED google-chrome-unstable-70.0.3521.2-1.x86_64.rpm ... Passed ==> ERROR: One or more files did not pass the validity check!

Musikolo commented on 2018-08-11 02:09 (UTC)

@yuu-syss, thanks for the heads up. The issue is fixed.

I don't know what's going on with the Google guys changing the EULA license every other day...

Thank you!

yuu-syss commented on 2018-08-11 00:42 (UTC)

Still having issues. Isn't the eula sha256sum f6aa8b7920d20c874deabc745517e0486e88fe9de667ad3d5fe6f61665ec725c instead of 8a0e9057c2a27bfcc74e210b848e6824e3c6c8f41232ca034362bcddfb95acbd ?

gaboflowers commented on 2018-08-10 03:25 (UTC)

I modified both the eula_text.html name in the source and install script, and the source web path, achieving nothing.

I ended up deleting the eula lines and hash entirely from the PKGBUILD.

Musikolo commented on 2018-08-09 01:49 (UTC)

@ot8, thanks for the heads up. The issue should be solved!

Thank you!

ot8 commented on 2018-08-08 14:32 (UTC)

Still broken for me ==> Validating source files with sha256sums...
chrome-eula_text.html ... FAILED

jmoya commented on 2018-08-03 16:18 (UTC)

Para corregir el error sha256sum solo hay que modificar el PKGBUILD

sha256sums=('8a0e9057c2a27bfcc74e210b848e6824e3c6c8f41232ca034362bcddfb95acbd' '570a397d6ae062393a04554f0e371cf2209d7eee176fc8dc0bdfb43c6a38f2be')

Plexcon commented on 2018-08-02 15:49 (UTC)

==> Validating source files with sha256sums ...      chrome-eula_text.html ... HAS FAILED      google-chrome-stable_68.0.3440.84-1_amd64.deb ... Approved ==> ERROR: One or more files did not pass the validation control!

artemis_clyde commented on 2018-08-02 08:57 (UTC) (edited on 2018-08-02 08:57 (UTC) by artemis_clyde)

I solved it for now by manually checking and altering the sha256 sum of the current eula_text.html in the PKGBUILD.

juliohm commented on 2018-07-29 02:22 (UTC)

Today when I tried to watch Netflix, I got this missing component error, it was working before:

Error Code: M7702-1003

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.

I am on Chromium instead and this package from AUR was working nicely. Any update recently that may have broken things?

bradsk88 commented on 2018-07-28 15:18 (UTC)

Seems like the old Chromium eula file gets left behind and the installer tries to keep using it.

I ended up fixing this by running pacaur -Sc to remove untracked files.

MonsterMannen commented on 2018-07-27 15:05 (UTC)

Validity check fails at every update when using aurman.

itaton commented on 2018-07-25 07:10 (UTC) (edited on 2018-07-25 07:15 (UTC) by itaton)

I don't think it's the helper's fault: I'm using yay.

I had to do the same change as mapolidori (the browser subdirectory was already removed - so I only had to change chrome-eula_text.html:: to eula_text.html::) and additionally I obviously had to change the last line from install -Dm644 chrome-eula_text.html [...] to install -Dm644 eula_text.html [...]

After that the update went perfectly fine

Scimmia commented on 2018-07-18 01:54 (UTC)

Whatever helper you two are using is doing totally idiotic things. The changes mapolidori mentions wouldn't even result in a functioning PKGBUILD.

mapolidori commented on 2018-07-18 01:50 (UTC) (edited on 2018-07-18 13:13 (UTC) by mapolidori)

EDIT: I'm using pacaur 4.7.90

I was having the same failed validity check issue. As ixil commented, I had to remove 'browser' from the link. I also had to remove 'chrome-' from 'chrome-eula_text.html'.

I changed source=('chrome-eula_text.html::<>'

to source=('eula_text.html::<>'

The update worked perfectly after that.

ixil commented on 2018-07-15 22:26 (UTC)

The eula has moved if you / your aur helper doesn't follow the 302, change the source to: <>

Note the removal of 'browser'. The checksum is correct, or use the --location --fail flags if manually getting it with curl

Musikolo commented on 2018-07-14 03:50 (UTC) (edited on 2018-07-14 03:53 (UTC) by Musikolo)

@zacky, the issue was fixed:

[musikolo@MyPC vivaldi-widevine]$ makepkg
==> Making package: vivaldi-widevine 1: (Fri Jul 13 22:47:41 2018)
==> Checking runtime dependencies...
==> Checking buildtime dependencies...
==> Retrieving sources...
  -> Downloading chrome-eula_text.html...
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100   257  100   257    0     0   1647      0 --:--:-- --:--:-- --:--:--  1647
100 47707    0 47707    0     0   203k      0 --:--:-- --:--:-- --:--:--  203k
  -> Downloading google-chrome-stable_67.0.3396.99-1_amd64.deb...
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
100 50.0M  100 50.0M    0     0  21.2M      0  0:00:02  0:00:02 --:--:-- 21.3M
==> Validating source files with sha256sums...
    chrome-eula_text.html ... Passed
    google-chrome-stable_67.0.3396.99-1_amd64.deb ... Passed
==> Extracting sources...
  -> Extracting google-chrome-stable_67.0.3396.99-1_amd64.deb with bsdtar
==> Starting prepare()...
==> Starting pkgver()...
==> Entering fakeroot environment...
==> Starting package()...
==> Tidying install...
  -> Removing libtool files...
  -> Purging unwanted files...
  -> Removing static library files...
  -> Compressing man and info pages...
==> Checking for packaging issues...
==> Creating package "vivaldi-widevine"...
  -> Generating .PKGINFO file...
  -> Generating .BUILDINFO file...
  -> Generating .MTREE file...
  -> Compressing package...
==> Leaving fakeroot environment.
==> Finished making: vivaldi-widevine 1: (Fri Jul 13 22:47:51 2018)
[musikolo@MyPC vivaldi-widevine]$ 

Please, make sure you get the latest version I pushed a while ago.

Thank you!

zacky commented on 2018-07-14 02:46 (UTC) (edited on 2018-07-14 03:44 (UTC) by zacky)

@Musikolo, I'm afraid it's not fixed yet. I tried and got:

==> Validating source files with sha256sums...
    chrome-eula_text.html ... FAILED
    google-chrome-stable_67.0.3396.99-1_amd64.deb ... Passed
==> ERROR: One or more files did not pass the validity check!

Musikolo commented on 2018-07-14 02:09 (UTC)

@awillson, thanks for the heads up.

Please try again, it should be fixed.

Thank you!

awillson commented on 2018-07-14 01:24 (UTC)

I tried compiling today and the checksum for the eula did not match.

AlexWayfer commented on 2018-07-13 21:13 (UTC)

==> Making package: chromium-widevine 1: (Sat 14 Jul 2018 00:13:28 MSK)
==> Retrieving sources...
  -> Found chrome-eula_text.html
  -> Found google-chrome-stable_67.0.3396.99-1_amd64.deb
==> Validating source files with sha256sums...
    chrome-eula_text.html ... FAILED
    google-chrome-stable_67.0.3396.99-1_amd64.deb ... Passed
==> ERROR: One or more files did not pass the validity check!
Error downloading sources: chromium-widevine

Failed. :(

Scimmia commented on 2018-07-12 01:32 (UTC)

The license has indeed been updated this time. This is totally separate from the comments last month.

teiesti commented on 2018-07-12 01:13 (UTC) (edited on 2018-07-12 01:31 (UTC) by teiesti)

The checksum for chrome-eula_text.html is really broken. It is fdabe95fea54cac48582fe8872cd7c1a5b3fbb38d0c0a9acc90ab91f8fbceeaf but the PKGBUILD says it must be cbfb7bc8d48ffc2dc6a86721c00b1662337bf72e7e63bffde783497cf36a43fa. I've tried several possibilities.

For those left without a possibility to install chromium-widevine: Just edit the PKGBUILD file in line 15. Replace the old checksum with the new one.

Scimmia commented on 2018-07-06 14:17 (UTC)

What package? The only ones I see are just the adapter lib, not the actual CDM.

Raansu commented on 2018-07-06 09:40 (UTC)

Is there a reason why we can't pull the latest from debian's chromium-widevine package?

I also see that debian has ARM packages for chromium-widevine. Can you add ARM support for widevine here?

Scimmia commented on 2018-06-22 09:31 (UTC)

It also seems to be rarely updated. We tried that download before and it was months out of date.

glitsj16 commented on 2018-06-22 09:22 (UTC) (edited on 2018-06-22 09:23 (UTC) by glitsj16)

An attempt at a 'lightweight' PKGBUILD. No need to download a full .deb. No checksum trouble for the chrome-eula_text.html as a bonus (although I'm not sure this covers all legalistics).

thieh commented on 2018-06-10 06:40 (UTC) (edited on 2018-06-10 06:41 (UTC) by thieh)

For the chrome-eula_text.html issue, it works fine for me, but I end up deleting everything and re-clone into the git repo. If you use an AUR helper like yaourt or pacaur, please consult your AUR helper documentation of what to delete.

jklaise commented on 2018-06-09 21:46 (UTC)

Same issue, can't update due to authentication not passing. Uninstalling didn't work, now left without a way to reinstall.

Musikolo commented on 2018-06-09 02:37 (UTC)

Updated to version


Scimmia commented on 2018-06-08 23:49 (UTC)

That just means the package is out of date. See chromium-widevine for details.

obelix1502 commented on 2018-06-08 21:12 (UTC)

Hello, My problem is that link "" is no more available : error 404. I've tried with the new one, but I know that your script was wrote with the first one. So, what can I do to resole it ?

Scimmia commented on 2018-06-03 14:01 (UTC)

It's not. Try deleting it and redownloading it.

bjo commented on 2018-06-03 13:58 (UTC) (edited on 2018-06-03 13:59 (UTC) by bjo)

It is:

:: Checking chromium-widevine integrity...
==> Making package: chromium-widevine 1: (Sun Jun  3 15:58:15 2018)
==> Retrieving sources...
  -> Found chrome-eula_text.html
  -> Found google-chrome-stable_67.0.3396.62-1_amd64.deb
==> Validating source files with sha256sums...
    chrome-eula_text.html ... FAILED
    google-chrome-stable_67.0.3396.62-1_amd64.deb ... Passed
==> ERROR: One or more files did not pass the validity check!
:: Preparing chromium-widevine...
==> Making package: chromium-widevine 1: (Sun Jun  3 15:58:16 2018)
==> WARNING: Skipping dependency checks.
==> Retrieving sources...
  -> Found chrome-eula_text.html
  -> Found google-chrome-stable_67.0.3396.62-1_amd64.deb

Scimmia commented on 2018-06-03 13:50 (UTC)

It's not broken.

bjo commented on 2018-06-03 10:48 (UTC) (edited on 2018-06-03 10:49 (UTC) by bjo)

Could you please fix the broken chrome-eula checksum? Thanks!

Scimmia commented on 2018-06-01 14:44 (UTC)

anatolik, the tree you linked to hasn't been updated in nearly 3 years.

TingPing commented on 2018-05-31 23:01 (UTC)

Maybe we can make this plugin part of the official Arch package?

It isn't redistributable.

anatolik commented on 2018-05-31 22:56 (UTC)

It makes sense to use the plugin binary from the official source tree.

Maybe we can make this plugin part of the official Arch package?

je-vv commented on 2018-05-30 06:21 (UTC)

Wouldn't it be better to SKIP the eula checksum? Happens again with Today's upgrade:

+++ chrome-eula_text.html ... FAILED google-chrome-stable_67.0.3396.62-1_amd64.deb ... Passed ==> ERROR: One or more files did not pass the validity check! +++

cookiewhispers commented on 2018-05-06 16:24 (UTC)

@undu Update your yay. The issue is fixed:

Musikolo commented on 2018-05-02 01:30 (UTC)

Updated to version


malnvenshorn commented on 2018-05-01 12:42 (UTC)

Checksum verification of chrome-eula_text.html fails.

FlashDaggerX commented on 2018-04-29 14:14 (UTC) (edited on 2018-04-29 14:15 (UTC) by FlashDaggerX)

For the checksum error that everyone is getting...

Receive the new sha256sum using:

curl <> | sha256sum

The terminal will print out a new sum at the bottom. I got:


Edit the PKGBUILD with the new SHA256SUM. Change the first sum. At the end, it should look like this:


ricardofunke commented on 2018-04-27 17:56 (UTC)

Got checksum failed for chrome-eula_text.html

Scimmia commented on 2018-04-23 03:32 (UTC)

So yet another AUR helper doing unbelievably stupid things. Is anyone surprised?

Musikolo commented on 2018-04-22 05:08 (UTC)

Updated to version


phiresky commented on 2018-04-21 15:14 (UTC)

Never mind, that's not actually the issue. Looks like it's because prepare() is not run before pkgver by yay.

phiresky commented on 2018-04-21 15:10 (UTC)

Same issue as @undu for me. Looks like you're assuming that $PWD is $srcdir? That assumption is incorrect for me when using yay.

Scimmia commented on 2018-04-19 15:34 (UTC)

I don't know what you're doing, but it works fine with makepkg

undu commented on 2018-04-19 15:30 (UTC)

Latest version (1: fails to build the package:

==> Starting pkgver()...
awk: fatal: cannot open file `' for reading (No such file or directory)

sl1pkn07 commented on 2018-03-25 13:18 (UTC)

No in makepkg

laenco commented on 2018-03-25 11:12 (UTC)

It looks like pkgver is executed before prepare:

strings: «opt/google/chrome-unstable/»: No such file or directory

sl1pkn07 commented on 2018-03-24 21:39 (UTC)


prazola commented on 2018-03-24 21:16 (UTC) (edited on 2018-03-24 21:16 (UTC) by prazola)

==> Starting pkgver()...

==> ERROR: pkgver is not allowed to be empty.

==> ERROR: pkgver() generated an invalid version:

==> ERROR: Makepkg was unable to build chromium-widevine-dev.

jonny999 commented on 2018-03-10 17:41 (UTC)

Wow, installed, restarted chromium and amazon video works again!! Thanks so much :)

AlesonMedeiros commented on 2018-03-03 16:46 (UTC)

Obrigado! funcionou perfeitamente

Scimmia commented on 2018-02-07 23:28 (UTC)

Not as far as I'm aware

nagual commented on 2018-02-07 11:44 (UTC)

Suporte for armv7 (raspberry) ?

erikburton commented on 2018-02-02 07:59 (UTC)

Made an account to say thanks!

pheerai commented on 2018-01-29 08:37 (UTC)

@hekel:This package primarily aims for users of the non-snapshot version of vivaldi. The dependency on vivaldi-ffmpeg-codecs is not unnecessary for them.

Also, please note that there ARE actually request in the vivaldi-snapshot-ffmpeg-codecs package to add a provides=(vivaldi-ffmpeg-codecs), which would solve your problem but hasn't yet been incorporated by the respective maintainer.

Tjuh commented on 2018-01-29 08:31 (UTC) (edited on 2018-01-29 08:32 (UTC) by Tjuh)

I have that same problem, but its easily fixed tho, if you already have vivaldi-snapshot-ffmpeg-codecs installed, just change vivaldi-ffmpeg-codecs to vivaldi-snapshot-ffmpeg-codecs on the depends() line in the PKGBUILD file.

hekel commented on 2018-01-29 02:47 (UTC)

This unnecessarily pulls in 'vivaldi-ffmpeg-codecs' which is particularly obnoxious because I only use 'vivaldi-snapshot' and already have 'vivaldi-snapshot-ffmpeg-codecs' installed.

pheerai commented on 2017-12-18 07:31 (UTC)

@nuario: The direct download approach has already been tried a few weeks ago, but unfortunately it seems as if google does not update their WV-repo as regularly as they update their chrome (read: Their current 'latest' build is, shipped with chrome is

ruario commented on 2017-12-15 13:34 (UTC) (edited on 2017-12-15 13:34 (UTC) by ruario)

Why pull down the entire Google?

Just get the lib directly:

$ WV_VERISON=$(wget -qO-

$ wget$

pheerai commented on 2017-11-28 09:30 (UTC)

@Rulatir: I'll try to figure out what could be wrong, but in the meantime could you please answer me the following questions? - What versions of Vivaldi and Chrome are installed? - Is the file `/opt/google/chrome/` available and readable? - How did you elaborate that Vivaldi does not pick up widevine? Is it "just" amazon or netflix not working, or have you also tried watching the video linked in the pinned comment? Thanks in advance.

Rulatir commented on 2017-11-28 01:03 (UTC)

I have google-chrome installed and Vivaldi does NOT pick up widevine.

Scimmia commented on 2017-11-01 13:52 (UTC)

Google doesn't seem to be keeping the direct download up to date. If it isn't updated, I'll have to switch this back to extracting it from Chrome. :(

enihcam commented on 2017-09-10 04:18 (UTC)

curl: (22) The requested URL returned error: 404

Ruddeck commented on 2017-08-16 18:40 (UTC)

Thanks. You help-me a lot.

Scimmia commented on 2017-08-14 17:25 (UTC)

I don't think the optdep on vivaldi-ffmpeg-codecs would be necessary. vivaldi already optionally depends on it, a second optional dep won't do much. Go ahead and test whatever you need. If it works, I can add the provides/replaces and we should be in good shape.

pheerai commented on 2017-08-14 16:23 (UTC)

Scimmia: Me, too, already played with that thought, also it would create a lot of optional dependencies in the background (you'd need an optdepends on `vivaldi-ffmpeg-codecs from my side, for example). Plus, I need some more testing on the browsers behaviour with the `.so` not lying in `/opt/google/chrome` with some special pages - my usual amazon access provider is on vacation. I'll drop you a mail once this is done, to discuss the future procedure with you outside of package comments, if that is ok?

Scimmia commented on 2017-08-14 14:30 (UTC)

pheeral, sounds like I should just remove the chromium dep in chromium-widevine and packages could be combined.

pheerai commented on 2017-08-14 08:33 (UTC) (edited on 2018-03-09 18:56 (UTC) by pheerai)

Please note that you won't need this package if you have google-chrome installed, vivaldi will find the plugin from that package as well.

You can check if you need this package here: If the video plays, you're already set regarding widevine, even though you might still need the vivaldi-ffmpeg-codecs.

pheerai commented on 2017-08-14 08:26 (UTC)

Ok, now I've got it. The conflicting package was chromium-widevine, not google-chrome, and that one somehow got lost during transition. Sorry. (I'm switching from directly modifying Scimmias chromium-widevine PKGBUILD to automatically generating one when needed) As the vivaldi-package itself creates a link to `/opt/google/chrome`, I will move the plugin back there, and re-add all the needed conflicts. Note that vivaldi now detects the widevine-plugin from the `chromium-widevine`- and `google-chrome`-package as well, so if you've got one of those installed you won't need this package. Thanks for your help, aoz and atnanasi. A new version will follow soon.

aoz commented on 2017-08-14 07:47 (UTC)

Upgrading to newest version causes conflict, though doing --force works (though it's kind of a bad idea to do so):

Scimmia commented on 2017-08-13 21:24 (UTC)

Any command line switch. For flash, it's --ppapi-flash-path. If they end up doing something similar for Widevine, we could put this in a more generic path and just let everything use it. I'm asking if they're moving that direction, since I don't follow Chromium development that much and the separate download seems to indicate they might be.

sl1pkn07 commented on 2017-08-13 19:55 (UTC) (edited on 2017-08-13 20:03 (UTC) by sl1pkn07)

what command line switch? i only put the library into /usr/lib/chromium-dev i'm not sure if upstream maked something about the widevine as pepperflash does

pheerai commented on 2017-08-13 18:47 (UTC) (edited on 2017-08-13 19:24 (UTC) by pheerai)

@atnanasi: That's what I call fast feedback. I will add it (I don't have google chrome installed), resp. try to check if chromium-widevine works now as well. I'll get back to you soon. EDIT: The most current version (1: does not conflict with google-chrome, I can install both of them simultaneously. Please be shure that you have the correct version installed And yes, I must admit that the previous version did in fact conflict, due to the fact that I was not aware of the naming change from chrome to google-chrome.

rokoucha commented on 2017-08-13 18:44 (UTC)

This package conflicts with google-chrome. Why don't you add conflict packages in PKGBUILD?

Scimmia commented on 2017-08-13 13:44 (UTC)

sl1pkn07, does chromium-dev use a command line switch for widevine now? With a separate download available, including a manifest.json, I'm wondering if they're going to handle it like they do the ppapi flash plugin. If they are, we can get support added to the wrapper and combine most/all of the widevine packages.

aoz commented on 2017-08-13 10:46 (UTC)

Scimmia: Ah, I didn't notice that, thanks for pointing that out.

sl1pkn07 commented on 2017-08-13 07:31 (UTC) (edited on 2017-08-13 20:04 (UTC) by sl1pkn07)

seems widevine provided by chromium dev channel is the same └───╼ sha256sum /usr/lib/chromium{,-dev}/ b713d924f429bbee515d9f8b837e83422f1d95fb619e9325ec6d30bf5fb8710f /usr/lib/chromium/ b713d924f429bbee515d9f8b837e83422f1d95fb619e9325ec6d30bf5fb8710f /usr/lib/chromium-dev/ can you add support to chromium-dev too?

Scimmia commented on 2017-08-13 01:03 (UTC)

I've just switched this to a direct download of the plugin only, so the current version is available for i686 again.

Scimmia commented on 2017-08-13 00:30 (UTC) (edited on 2017-08-13 01:01 (UTC) by Scimmia)

aoz, that download didn't exist until recently. Notice that the gist you linked to just switched to it 15 days ago. Edit: or rather I should say I wasn't aware of that download, it could have existed and nobody was aware.

pheerai commented on 2017-08-12 17:30 (UTC)

@aoz, this package was just a "quick and dirty hack". It is based on Scimmias package for chromium-widevine, which uses the approach for as long as I can remember. Actually I wasn't aware of a standalone widevine download page. Thanks for that. I'll try to rewrite the PKGBUILD as soon as possible, but please don't expect any near-time solution, as I'm currently writing my master's thesis, which has a marginally higher priority ;-)

aoz commented on 2017-08-12 17:22 (UTC)

Why doesn't this package just download the most recent widevine binaries from google like does?

Scimmia commented on 2017-06-23 02:52 (UTC)

The source has to be updated because the old source isn't available anymore. Same plugin, same resulting package, no pkgver or pkgrel bump. This isn't a "point of view" this is standard packaging.

Musikolo commented on 2017-06-23 02:38 (UTC) (edited on 2017-06-23 02:39 (UTC) by Musikolo)

@Scimmia, I understand what you mean, but I don't completely share your point of view. According to the changelog available at , the google-chrome-stable source package was updated from version '59.0.3071.86-1' to '59.0.3071.104-1'. It could be the case in which both sources contain the same version of the widevine plugin. If this is the case, either there was no need of updating the source or the release version of vivaldi-widevine should have been bumped. To my knowledge, making changes in a package and keeping the same version, even if the resultant binary is the same, is a bad practice.

Scimmia commented on 2017-06-23 01:31 (UTC)

Musikolo, the source doesn't matter at all. The version of the plugin didn't change, there's no reason to rebuild.

Musikolo commented on 2017-06-23 00:53 (UTC)

@pheerai, in your last update I think you forgot to change the version of the vivaldi-widevine package or bump the release number. Since the source changed, the version of vivaldi-widevine cannot be kept same as it was. Otherwise, pacman won't upgrade it, since it considers old package same as the new one. Thank you!

blx32 commented on 2017-06-01 05:07 (UTC)

Muito obrigado.

Scimmia commented on 2017-05-03 06:01 (UTC) (edited on 2017-05-03 06:05 (UTC) by Scimmia)

There was no increment in pkgrel because there was no change in the plugin. No reason to rebuild the package if you already have that version of the plugin.

RemoteAdmin commented on 2017-05-03 05:58 (UTC)

@Scimmia The last update was missing an increment in pkgrel. Therefore package managers won't show a package update. Would be nice if you increment it when the pkgver stays unchanged.

salm commented on 2017-03-27 15:04 (UTC)

Can someone be so kind and respond to my previous question? I'm stuck here.

salm commented on 2017-03-24 13:35 (UTC) (edited on 2017-03-24 16:17 (UTC) by salm)

Scimmia, 'google-chrome' cannot be installed on armv7 but I've installed Ubuntu with chromium on my armv7 device and it supports Widevnie. Would that help? can I re-purpose the '' file that I see in the Ubuntu installation onto my arch-linux build? Thanks very much

Scimmia commented on 2017-03-23 03:07 (UTC)

Does it work on Chrome on ARMv7? If not, there's nothing we can do.

salm commented on 2017-03-23 02:54 (UTC) (edited on 2017-03-23 02:55 (UTC) by salm)

polyzen, I tried that first but this didn't work. It seemed as if it wouldn't download the binaries. I see that the Debian distro has widevine for armhf: Is there any way I can utilze that? I see that in the Debian package there's only a file. No file.

polyzen commented on 2017-03-23 01:06 (UTC)

If it already works with ARMv7, you could build the package with this option:

salm commented on 2017-03-23 00:58 (UTC)

Do you have any plans for adding support for ARMv7? If not, how can I go about doing this myself? Thanks

digitalone commented on 2017-02-20 09:05 (UTC)

That's awesome! I can see Premium Play on Linux with this plugin. I wanted this for years. Thanks a lot!

pheerai commented on 2017-02-08 06:41 (UTC)

@Soukyuu: Unfortunately, basing dependencies upon already installed packages is not possible with AUR and pacman (and I'm not aware of any package management system that can do this). For your request to work, there are two possibilities: - Support @ninian s request to BlackIkeEagle to add a 'provides' statement to vivaldi-snapshot-ffmpeg-codecs. This would clearly be the better option. - Create a vivaldi-snapshot-widevine package that modifies this PKGBUILD. Unfortunately, I don't have the time to do so and maintain it.

ninian commented on 2017-02-07 20:53 (UTC)

@Soukyuu Please see my comment at: for another view of the problem

Soukyuu commented on 2017-02-07 20:48 (UTC)

Shouldn't this one look for vivaldi-snapshot-ffmpeg-codecs if vivaldi-snapshot is used? Else I have to install both packages just to make this one happy.

Scimmia commented on 2017-02-02 04:11 (UTC)

In the nearly 2 years this package has existed, the license has changed twice. That's it. Putting the chromever on it so that people potentially have dozens of copies of the same thing sitting around makes no sense to me. I wouldn't think cleaning the cache once a year would be such an issue.

bulletmark commented on 2017-02-01 00:47 (UTC)

@Scimmia did not reply to my query so perhaps I was not clear. The chrome-eula_test.html file sometimes changes between versions but since pacaur caches the file it does not download it again and then it fails the sha256 check when we do a regular update of our AUR packages, as @tkei reports below. This problem can be avoided if the source download name is changed in the PKGBUILD to chrome-eula_text-${_chrome_ver}.html.

bulletmark commented on 2017-01-27 22:07 (UTC)

@Scimmia, perhaps in the PKGBUILD you should tack _chrome_ver on the downloaded chrome-eula_text.html file name because pacaur caches this file and so doing a regular update fails with a checksum error, as @tkei reports below and as I have experienced this time and previous times. We have to delete the pacaur cache so the update can work (or use yaourt!).

Scimmia commented on 2017-01-26 23:50 (UTC)

Delete it and redownload it. Checksum is correct.

tkel commented on 2017-01-26 21:04 (UTC) (edited on 2017-01-26 21:04 (UTC) by tkel)

==> Validating source files with sha256sums... chrome-eula_text.html ... FAILED Since 2017-1-25.

Scimmia commented on 2016-12-21 13:17 (UTC)

Trilby, this used to ship the adapter lib, but the adapter was tied to a specific major version of chromium making things a bit complex (there's a whole lot of complaining in previous comments). The maintainer of chromium decided to build the adapter as part of the chromium package to simplify things here. Maybe you could adapt that patch to either qt5-webengine or qutebrowser to build the adapter?

commented on 2016-12-21 12:55 (UTC)

Thanks leonardof, I've come to similar conclusions. I've also realized I can make a "proper" qt5-webengine version that installs the so files to a qt5-webengine specific path. This is much cleaner, but does necessitate a separate package. I just always prefer to be cautious when creating new AUR packages to ensure that we don't get more needless duplication. In this case though it does seem needed. Doug, feel free to disregard my previous question - but thanks for this package, it made an excellent template for the qt5-webengine version.

leonardof commented on 2016-12-21 12:45 (UTC)

I use Chromium to watch Netflix with this plugin, and from reading the gist posted in the forum I understand the this change will make the package incompatible with the chromium one. With this change, not only this package will install "" (which currently is owned by the chromium package at my system) but also (from reading the gist mentioned in the forum) this package will advertise itself as conflicting with the chromium one. As far as I can tell, this means the changes need to go in another package.

commented on 2016-12-21 12:04 (UTC)

Doug, I've been working on getting netflix playing in qutebrowser without also needing chromium installed and have recently found success. I was going to make an AUR package for others with the same goals, but I found we'd be largely duplicating efforts. The changes to the PKGBUILD would make this aur package applicable to a wider audience: -depends=("chromium") - bsdtar -xf data.tar.xz opt/google/chrome/{chrome,} + bsdtar -xf data.tar.xz opt/google/chrome/{chrome,,} + install -Dm644 opt/google/chrome/ -t "$pkgdir/usr/lib/chromium/" Those 2 so files are all that's needed to watch video on sites like netflix in QtWebEngine browsers (e.g., qutebrowser). So for my purposes I've removed the chromium dependency and added the other .so file to the PKGBUILD. The only reason it may still be valuable to have separate AUR packages would be due to the conflict of my modification with the cdmadapter in chromium. I wanted to get your thoughts on whether it'd be worth trying to have a single package that can cover both use cases, or if I'd be better of creating a new qt5-webenegine-widevine package. xref forum post:

pheerai commented on 2016-12-19 08:34 (UTC)

@neognomic Yes, you're right. Seems like this slipped through somehow. I have tried to run Amazon Video without vivaldi-ffmpeg-codecs, this doesn't work, so it seems to be needed at runtime – depends, I fear. As a “better solution”, you could add Herekura‘s Arch Repository as described [here][1], it provides both vivaldi and vivaldi-ffmpeg-codecs as binary packages. I'll change the package and add the dependency. [1]:

neognomic commented on 2016-12-18 22:54 (UTC)

Thank you very much for providing this package. However, it will not work unless the ffmpeg additional package is installed(i.e., the vivaldi-ffmpeg-codecs from AUR). I already had ffmpeg 1:3.2.2-1 and ffmpeg2.8 2.8.9-1 installed. I had "always enable", ...etc. No amount of coaxing would get a (DRM) video to play at Amazon Prime with Vivaldi and this plugin. (BTW, Mozilla and Chromium w/ Widevine work fine ...well, as fine as firefox or chromium can) Built & installed the vivaldi-ffmpeg-codecs, and BAM! I got videoluv. I do not think "optdepends" is sufficient but do not know what is best solution. [ It took 45 min. to download and build the vivaldi-ffmpeg-codecs on this test system(dual Opterons, for 4 cores @2600Mhz) at _full_ load. I shudder at doing that for every update, even with the other newer/faster system. ] Please think about some better solution. In any event Happy Holidays and if I ever get the chance will buy y'all a cup of coffee, ;).

Scimmia commented on 2016-11-12 15:47 (UTC)

dekellum, see previous comments and download a new license.

dekellum commented on 2016-11-12 12:38 (UTC)

I also just got the "chrome-eula_text.html ... FAILED" and had to edit PKGBUILD like so: 7c17 < sha256sums=('e93c01576427cad9099f2cf0df0be70d0a2cc0a3a66c743318b2138aa7c4ed93') --- > sha256sums=('b35811bb330576631e64f7885c66720e0be4ca81afb04328b3a0f288a708e37f')

Scimmia commented on 2016-10-18 23:56 (UTC) (edited on 2016-10-18 23:58 (UTC) by Scimmia)

The update script I use for this package redownloads the license every time, so it's correct at the time of each update. I just checked it, and it's still showing correct for me. Either you guys have an old EULA laying around or google is screwing with us, likely based on region. Edit: The checksum posted is for an old license, so you guys probably just need to redownload it.

squattingmonk commented on 2016-10-18 21:55 (UTC)

@btreecat, that worked for me. Thanks!

btreecat commented on 2016-10-17 14:47 (UTC)

If you are getting this message while upgrading, ==> Validating source files with sha256sums... chrome-eula_text.html ... FAILED ==> ERROR: One or more files did not pass the validity check! :: failed to verify chromium-widevine integrity Try using this sha256 sum b35811bb330576631e64f7885c66720e0be4ca81afb04328b3a0f288a708e37f It seems like the EULA URL might resolve differently in a browser than by script. @scimmia can you please do some testing to verify?

tkel commented on 2016-10-14 01:51 (UTC) (edited on 2016-10-14 01:51 (UTC) by tkel)

==> Validating source files with sha256sums... chrome-eula_text.html ... FAILED ==> ERROR: One or more files did not pass the validity check! :: failed to verify chromium-widevine integrity

kawasakai commented on 2016-10-12 17:41 (UTC)

Can you guys watch Amazon Prime in HD with this?

Scimmia commented on 2016-10-05 00:47 (UTC)

@claytonthompson, the script pulls the version from You can see from the "Previous Version", that's what they put in. Looks like a glitch, already fixed.

claytonthompson commented on 2016-10-04 22:36 (UTC)

It looks like in your recent commit you set the chromium version to a much older one. The previous patch worked for me -

commented on 2016-09-26 22:32 (UTC)

@BigEars431 I think you're running out of space in your temp directory. Use --tmp [~/a_dir] as an argument of your to temporarily use your home directory to download to. Also, you could resize your /tmp directory. Try df -h to inquire.

jmsq commented on 2016-09-25 13:47 (UTC)

==> Validating source files with sha256sums... chrome-eula_text.html ... FAILED ==> ERROR: One or more files did not pass the validity check! :: failed to verify chromium-widevine integrity

BigEars431 commented on 2016-09-23 12:22 (UTC)

Sorry, Arch Linux noob here... I can't seem build the package $ updpkgsums | doesn't fix it =( anybody willing to help a noob out? ==> Retrieving sources... -> Downloading eula_text.html... 09/23 20:20:42 [NOTICE] Downloading 1 item(s) 09/23 20:20:43 [NOTICE] Download complete: /tmp/yaourt-tmp-kylert/aur-chromium-widevine-dev/eula_text.html.part Download Results: gid |stat|avg speed |path/URI ======+====+===========+======================================================= db4dbc|OK | 52KiB/s|/tmp/yaourt-tmp-kylert/aur-chromium-widevine-dev/eula_text.html.part Status Legend: (OK):download completed. -> Downloading google-chrome-unstable-55.0.2859.0-1.x86_64.rpm... 09/23 20:20:43 [NOTICE] Downloading 1 item(s) [#22dfbe 44MiB/45MiB(99%) CN:8 DL:775KiB] 09/23 20:21:29 [NOTICE] Download complete: /tmp/yaourt-tmp-kylert/aur-chromium-widevine-dev/google-chrome-unstable-55.0.2859.0-1.x86_64.rpm.part Download Results: gid |stat|avg speed |path/URI ======+====+===========+======================================================= 22dfbe|OK | 0.9MiB/s|/tmp/yaourt-tmp-kylert/aur-chromium-widevine-dev/google-chrome-unstable-55.0.2859.0-1.x86_64.rpm.part Status Legend: (OK):download completed. ==> Validating source files with sha1sums... eula_text.html ... FAILED google-chrome-unstable-55.0.2859.0-1.x86_64.rpm ... Passed ==> ERROR: One or more files did not pass the validity check! ==> ERROR: Makepkg was unable to build chromium-widevine-dev. ==> Restart building chromium-widevine-dev ? [y/N] ==> ---------------------------------------------- ==>

Scimmia commented on 2016-09-18 15:22 (UTC)

RubenKelevra, it's for Chromium. shadowhand, Chromium already depends on nss.

shadowhand commented on 2016-09-17 15:07 (UTC)

Is it possible that this package also depends on nss?

RubenKelevra commented on 2016-09-15 11:37 (UTC)

Actually this chromium is just google chrome, why does you name it chromium?

Scimmia commented on 2016-08-27 13:26 (UTC)

@Bazon, read the pinned comments.

Bazon commented on 2016-08-27 04:55 (UTC) (edited on 2016-08-27 04:58 (UTC) by Bazon)

I get an infinite install loop for this. Every time I try to update via yaourt -Sau, the same version is installed again: ---------------------------------------- ==> Software upgrade (new version) : aur/chromium-widevine 1: -> 1: (...) ==> Retrieving sources... (...) -> Downloading google-chrome-stable_48.0.2564.116-1_i386.deb... (..) google-chrome-stable_48.0.2564.116-1_i386.deb ... Passed (...) ==> Updated version: chromium-widevine 1: (...) warning: chromium-widevine-1: is up to date -- reinstalling (...) -------------------------------------- I really don't understand what that jump in the packagever triggers though... PS: I think that change of pkgver causes the trouble: pkgver() { awk 'match($0,/\(version: \0?([0-9.]+)/,a) {print a[1];}' opt/google/chrome/chrome }

pheerai commented on 2016-08-24 09:31 (UTC)

@GLTRV If you have Chrome installed you're already set. The point of this package is to provide the widevine-library for those who don't want to install whole chrome. Chromium saves its in another location, whereas vivaldi searches for the one in chrome's path.

GLTRV commented on 2016-08-23 23:35 (UTC)

Why is this package in conflict with Google Chrome? I don't want to remove Google Chrome. chromium-widevine can be installed alongside Google Chrome. Thanks.

Scimmia commented on 2016-06-23 14:06 (UTC)

They don't have to redownload anything. The filename never changes, so they should still have it available. It will also never upgrade and the pkgver is now behind what is listed in the AUR, so they should realize that they're behind. I pinned an announcement about it in the comments for chromium-widevine.

pheerai commented on 2016-06-23 13:56 (UTC)

I initially removed the pkgver() function, because with it the package won't build using bauerbill (I've provided this upstream), but re-added it for now. But I don't know whether pinning just the x86-architecture is the way to go: By doing so, each 32bit user has to redownload the whole chromium every time an update is available, even though nothing changes. Additionaly, they get the impression of a frequently updated software, which it isn't and as which it should not be regarded. After all this is a media extension and definitely has its security flaws, so users should know if there are no more updates. Unfortunately, as of now, I don't have any better idea than slitting the package up or dropping 32bit support, which I don't like, either.

Scimmia commented on 2016-06-23 02:10 (UTC)

Without the pkgver function, the 32-bit version gets the wrong pkgver. It also makes it more difficult to update, as you have to look up the version manually every time you bump the chrome version.

pheerai commented on 2016-06-15 07:49 (UTC)

I completely forgot about the snapshot-package, sorry. I'll upload a new version without dependency as soon as possible.

BlackIkeEagle commented on 2016-06-14 18:38 (UTC)

The package should not have a hard dependency on vivaldi since its also usable for vivaldi-snapshot So I will add an optdepend on vivaldi-widevine in the vivaldi and vivaldi-snapshot packages.

Gruentee commented on 2016-05-14 20:53 (UTC)

The Chrome download link is dead, for all those who need to download the i686 version, replace the download link in the PKGBUILD with the following link: Good luck!

sl1pkn07 commented on 2016-04-27 14:03 (UTC)

@harpsichord done

harpsichord commented on 2016-04-27 00:05 (UTC)

==> Building and installing package ==> Making package: chromium-widevine-dev (Tue Apr 26 19:55:39 EDT 2016) ==> Checking runtime dependencies... ==> Checking buildtime dependencies... ==> Retrieving sources... -> Found eula_text.html -> Found google-chrome-unstable-52.0.2716.0-1.x86_64.rpm ==> Validating source files with sha1sums... eula_text.html ... Passed google-chrome-unstable-52.0.2716.0-1.x86_64.rpm ... Passed ==> Extracting sources... ==> Starting pkgver()... ==> ERROR: pkgver is not allowed to contain colons, hyphens or whitespace. ==> ERROR: pkgver() generated an invalid version: The component updated flash plugin could not be mapped as executable. Attempting to fallback to the bundled or system plugin. ==> ERROR: Makepkg was unable to build chromium-widevine-dev. ==> Restart building chromium-widevine-dev ? [y/N] ==> ----------------------------------------------

Scimmia commented on 2016-04-17 20:27 (UTC)

@woshee, not legally. It wasn't this slow before, they're probably just having issues right now.

woshee commented on 2016-04-17 19:52 (UTC)

I can't download the i686 mirror. It's extremely slow and it always hangs at some point. Would it be possible to only host the widevine plugin somewhere ?

commented on 2016-03-29 04:11 (UTC)

The "FYI" beginning caused me at least to skip it completely..

Scimmia commented on 2016-03-28 23:32 (UTC)

@tommymh, please read the sticky posts.

tommymh commented on 2016-03-28 20:46 (UTC)

I'm getting a 404 with the current source URL's, fixed by manually updating URL and checksum.

Scimmia commented on 2016-03-03 03:12 (UTC)

There are no more 32-bit builds of Chrome on Linux. I've pinned the i686 download to the last version available; currently it is the same plugin as the current package. This could (and likely will) change in the future, and i686 users will be stuck on the current version. While it works, I suggest upgrading to a 64-bit system whenever it's feasible.

Scimmia commented on 2016-02-17 04:27 (UTC)

Install this, then completely shut down and restart Chromium. And make sure it's Chromium from the Extra repo or another one that applies the same patches.

TheStochasticMan commented on 2016-02-17 04:23 (UTC)

This doesn't seem to be working for me. Is there anything I need to do other than simply installing this patch?

aaschmid commented on 2016-02-03 19:53 (UTC) (edited on 2016-02-03 19:57 (UTC) by aaschmid)

Yes, you are right, that helped. Didn't do any intended force update but it obviously was my fault. Removed the comment. Sorry for the effort!

foutrelis commented on 2016-02-03 19:53 (UTC) (edited on 2016-02-03 19:53 (UTC) by foutrelis)

@aaschmid Sounds like you force upgraded chromium and then updated chromium-widevine which would end up removing chromium's You need to remove this plugin, reinstall chromium and finally install chromium-widevine again.

Det commented on 2016-01-21 23:37 (UTC) (edited on 2016-01-21 23:37 (UTC) by Det)

E: Nope, nevermind.

Scimmia commented on 2016-01-21 21:07 (UTC)

1: available. Remember update it BEFORE updating to chromium 48.0.2564.82

Scimmia commented on 2016-01-21 18:58 (UTC)

While we were in Chromium 47, the downgrade didn't matter that much. I was hoping they'd go back to for Chrome 48 and we'd be able to avoid the epoch. That didn't happen and the Chrome 48 package needs to be newer than any of the Chrome 47 packages.

txus commented on 2016-01-21 17:17 (UTC)

But that was a month and a half ago, and applied to chromium ver. 47, AFAIR, which is going to get obsoleted quite soon, right?

Scimmia commented on 2016-01-21 17:05 (UTC)

epoch was necessary because the pkgver went backwards.

txus commented on 2016-01-21 17:02 (UTC)

Why the epoch change and not just a pkgrel bump? Even if this was in an actual repo and not in AUR, where in theory you build your own packages and the version is basically a commodity, you just did a change to the "build" result without changing the version, which is what pkgrel is for. I would recommend reverting the epoch line! For more information, see here:

Roberth commented on 2016-01-21 16:54 (UTC)

This just shows how bad it is to have it in the repos and updating it together with the chromium package.

Scimmia commented on 2016-01-21 16:53 (UTC)

I've been talking with foutrelis, he's going to ship the adapter lib as part of the chromium package. This will simplify things here in that we'll no longer be tied to a specific version of chromium and the versioned dep will go away. Since this will create a file conflict, it will require you to update this package to 1: BEFORE updating to chromium 48.0.2564.82. Alternatively, you could uninstall this package first, do the upgrade, then reinstall. 1: will be available when chromium is updated in the repos.

Det commented on 2016-01-21 16:34 (UTC) (edited on 2016-01-21 16:34 (UTC) by Det)

I think it would be easy enough to have to have two source_i686/source_x86_64 lines (other two commented), so you could switch between and the upstream mirror easily, to avoid breaking it?

Scimmia commented on 2016-01-21 16:33 (UTC)

@Roberth, read previous comments

Roberth commented on 2016-01-21 16:31 (UTC)

Why is this updated to require chromium 48 before chromium 48 is in the official repos?

Scimmia commented on 2016-01-21 08:15 (UTC)

ava1ar, since this includes the "adapter" lib, it does seem to be tied to new major versions. So yes, the versioned dep is necessary. I also can't wait to bump it as the old download was removed so the build was broken.

ava1ar commented on 2016-01-21 04:12 (UTC)

It the chromium>=48 really necessary in the depends - I mean the version? This is stable (without -dev) prefix version of a plugin and I (and I believe lot of other people) use this together with chromium from the extra repository. You just bumped the version, but the chromium is not yet updated to 48, so now when trying to update the system I am getting unsutisfied dependency on chromium... I would suggest for non-dev version of the plugin either not enforce the chromium dependency version (if possible) or just wait to the chromium update in extra. P.S. No complains at all - just putting my 2¢ in order to make your package user's expierence better.

jamesbond007 commented on 2016-01-20 22:58 (UTC)

Is there a new version or something? - I get this: curl: (22) The requested URL returned error: 404 Not Found ==> ERROR: Failure while downloading google-chrome-stable_47.0.2526.111-1_amd64.deb Aborting...

Det commented on 2016-01-16 19:30 (UTC)

Right, that's what I said initially.

Scimmia commented on 2016-01-16 17:47 (UTC)

I've been watching it, it seems that mirror provides only old versions, not the current version. Not much I can do with that.

Det commented on 2016-01-16 05:07 (UTC)

As long as you keep the md5sums intact, it shouldn't be a problem. I've used the same host for a long time as a backup link for the previous version in google-chrome-dev's PKGBUILD, and so far nobody has complained:

sl1pkn07 commented on 2016-01-14 03:12 (UTC)

back to use only with chromium-dev sorry guys

Scimmia commented on 2016-01-14 02:17 (UTC)

Interesting. I'm not sure switching to 3rd party mirrors is a good option, though.

Det commented on 2016-01-14 01:45 (UTC)

By the way, old versions are stocked in other places, like:

darkbasic commented on 2015-11-26 20:17 (UTC)

With chromium-widevine (not dev) it works flawlessly.

darkbasic commented on 2015-11-25 13:04 (UTC)

I can't get it working with chromium, any idea?

Scimmia commented on 2015-11-13 23:05 (UTC)

Since that's an upstream binary package, first you'd have to see if they even built widevine support. If they didn't, there's not much you can do.

sl1pkn07 commented on 2015-11-13 19:58 (UTC)

maybe with symlink?

lesebas commented on 2015-11-13 19:35 (UTC)

same comment of andre.vmatos How to use it in chromium-continuous?

Scimmia commented on 2015-10-25 13:57 (UTC)

@Snoop05, and how would we do that, exactly?

Snoop05 commented on 2015-10-25 13:50 (UTC)

What about -standalone which won't require downloading and unpacking whole chrome deb?

Scimmia commented on 2015-10-14 03:50 (UTC)

When upstream bumps it, I have little choice but to bump this whether or not the Arch repos have been updated. If you can convince Google to allow downloads of old versions, great. If not, it's just something we have to deal with.

weirddan455 commented on 2015-10-14 01:19 (UTC)

Chromium 46 is in [extra] now.

bulletmark commented on 2015-10-13 21:52 (UTC)

There's gotta be a better way :(

justinkb commented on 2015-10-13 21:51 (UTC)

Yeah, PKGBUILD bumped prematurely it seems. Chromium 46 isn't yet packaged (or even released, it seems)

commented on 2015-10-13 21:02 (UTC)

==> dependencias de chromium-widevine: - chromium>=46 (compilando desde AUR) ==> Continuar compilando chromium-widevine? [S/n] ==> --------------------------------------------- ==> ==> Compilando e instalando el paquete ==> Instalar o compilar las dependencias que faltan para chromium-widevine: error: destino no encontrado: chromium>=46 ==> ¿Reiniciar la compilación de chromium-widevine? [s/N] ==> ----------------------------------------------------- ==> ==> ERROR: no se puede actualizar

Scimmia commented on 2015-09-19 02:01 (UTC)

Hmm, my automatic updates seem to have failed. I'll be home tomorrow and take a look at it then.

jryan commented on 2015-09-17 20:35 (UTC)

I just skipped the checks, but thought I'd let you know them seems outdated.

jryan commented on 2015-09-17 20:33 (UTC)

Having issue with the download. ==> Validating source files with sha256sums... google-chrome-stable_45.0.2454.93_amd64.deb ... FAILED ==> ERROR: One or more files did not pass the validity check! :: failed to verify chromium-widevine integrity

Scimmia commented on 2015-09-02 23:11 (UTC)

I'm not understanding what you're saying, I guess. The chromium package doesn't download the file.

bulletmark commented on 2015-09-02 23:03 (UTC)

I mean the chromium package stores the download file somewhere (e.g. /opt/google/) on the user's system from where other packages can extract from. It is obviously legal to download the file, surely it does not have to be deleted?

Scimmia commented on 2015-09-02 23:01 (UTC)

No, it can't keep hte current chrome download somewhere as that's not legal.

bulletmark commented on 2015-09-02 22:34 (UTC)

There's gotta be a better way Doug. This approach causes system updates to fail for anybody using an AUR helper. Ideally this package would be supported/coupled better with the main chromium package. It could keep the current chromium download somewhere for extraction. Please think about it.

Scimmia commented on 2015-09-02 01:31 (UTC)

Odd, but it can't be helped. This downloads Chrome and extracts the necessary files, but old versions of Chrome are not available for download. This means I either wait to update this package causing the build to fail with either a 404 or checksum problem, or I update it and the versioned dep tells you what the problem is. I opted for the latter.

bulletmark commented on 2015-09-02 00:03 (UTC)

@ledati. It just seems odd that this package is dependent on something that is not even in the repos?

ledti commented on 2015-09-01 22:42 (UTC)

@bulletmark, There's a new stable version of chromium, but it hasn't hit the repos yet. Wait 'til you get that upgrade then try again.

bulletmark commented on 2015-09-01 22:14 (UTC)

When I try to install this I get: ==> Building and installing package ==> Install or build missing dependencies for chromium-widevine: error: target not found: chromium>=45

SinOjos commented on 2015-07-21 21:48 (UTC)

I just attempted to install and received this error. ==> Making package: chromium-widevine (Tue Jul 21 14:38:07 MST 2015) ==> Checking runtime dependencies... ==> Checking buildtime dependencies... ==> Retrieving sources... -> Found chrome-eula_text.html -> Found google-chrome-stable_44.0.2403.89_amd64.deb ==> Validating source files with sha256sums... chrome-eula_text.html ... Passed ==> Validating source files with sha256sums... google-chrome-stable_44.0.2403.89_amd64.deb ... FAILED ==> ERROR: One or more files did not pass the validity check! The build failed.

Scimmia commented on 2015-07-07 03:26 (UTC)

I doubt you can. Chromium/Chrome has to be built to interface with widevine:

andre.vmatos commented on 2015-07-06 23:12 (UTC)

How to make it work with chromium-continuous-bin?

andre.vmatos commented on 2015-07-06 22:59 (UTC)

How to make it work with chromium-continuous-bin?

Scimmia commented on 2015-05-21 04:07 (UTC)

I just re-downloaded it and see no change. Are you sure you don't have an old one cached?

WonderWoofy commented on 2015-05-21 03:51 (UTC)

Hi Scimmia! Thanks for maintaining this package! The eula seems to have been updated and now fails the validity check.

Scimmia commented on 2015-05-19 17:07 (UTC)

A whole lot of nothing there, IMO. Adds to the complexity, requires maintenance, and really doesn't do anything useful. I'm not sure that changing the EULA is even legal.

jamesan commented on 2015-05-19 16:58 (UTC)

Is there any want to strip the markup from the EULA file so it contains just the text? I'm unsure as preserving upstream files as close to their source as we can is one of our values, yet of all the over 800 files in my /usr/share/licenses, only 6 files are formats other than plain text (4 HTML files and 2 PDFs for archon, flashplugin, google-chrome-dev, icu, lua-expat, lua52-expat, and pdflib-lite). Here's a prepare() function that can be inserted into the PKGBUILD to extract just the EULA text from the HTML file. It includes a few additional sed statements to "beautify" the document with empty lines for visual clarity: prepare() { # Extract EULA text between these opening and closing div tags. sed -n '/<div class="compact">/','/<\/div>/p' eula_text.html | \ # Remove in-line strong tags and remove other lines with tags. sed 's/<\/\?strong>//g;/>/d;s/^\s*//' | \ # Insert empty line ahead of each numbered list item. sed -r 's/^([0-9]|\([a-z]\)|[a-z]\.)/\n\1/' | \ # Insert empty line after EULA headings. sed -r 's/(Google Chrome)( Additional|)( Terms of Service)/\1\2\3\n/' | # Insert empty line before and after date line between the two TOS. sed -r 's/(August 12, 2010)/\n\1\n/' >| eula_text.txt } Just change the install line in the package() function to use install eula_text.txt instead of eula_text.html.

jamesan commented on 2015-05-19 15:51 (UTC)

The EULA text file check sum seems to have changed. It's value now is: SHA1: 1ffba5152cb749300a016efec909b828eba9a64a eula_text.html MD5: da54da9383ddffa44c5db45513239da2 eula_text.html

Scimmia commented on 2015-05-08 17:55 (UTC)

Still shows up in chrome://plugins and still works here, though.

tmathmeyer commented on 2015-05-08 17:48 (UTC)

latest build doesn't have widevine showing in chrome://components

sl1pkn07 commented on 2015-05-06 17:28 (UTC)

ok then. very thanks

Scimmia commented on 2015-05-06 17:27 (UTC)

Netflix is the only test case I know of.

sl1pkn07 commented on 2015-05-06 17:26 (UTC)

ok. you can provide a test case? (sorry, i'm not netfix user)

Scimmia commented on 2015-05-06 17:25 (UTC)

No, it does not.

sl1pkn07 commented on 2015-05-06 17:24 (UTC) say plug is installed?

Scimmia commented on 2015-05-06 17:23 (UTC)

Yes, chromium in Extra + chromium-widevine works with Netflix. The plugin is already included with Chrome (obviously), so yes, widevine works with Netflix there as well.

sl1pkn07 commented on 2015-05-06 17:18 (UTC)

but with chromium(-dev)? or with chrome

Scimmia commented on 2015-05-06 17:17 (UTC)

I wouldn't say it doesn't work. I can tell you for sure that chromium-widevine works great with Netflix.

sl1pkn07 commented on 2015-05-06 17:10 (UTC)

then I don't know why is frag outdated (without any message aclaration) (yes, I know this not work. but I keep for testing)

Scimmia commented on 2015-05-06 17:07 (UTC)

If it doesn't work in google-chrome{,-beta,-dev}, then it's not going to work here, either.

sl1pkn07 commented on 2015-04-29 20:03 (UTC)

redirect direct to 404 Page Not Found The page you are looking for could not be found. Check the address bar to ensure your URL is spelled correctly. If all else fails, you can visit our home page at the link below. Visit the Home Page

timcowchip commented on 2015-04-29 19:52 (UTC) ?

sl1pkn07 commented on 2015-04-29 19:51 (UTC)

maybe region locked?

sl1pkn07 commented on 2015-04-29 19:50 (UTC)

404 not found

timcowchip commented on 2015-04-29 19:49 (UTC)

that's what I'm saying "it installs fine, it just doesn't run" does this link work for you?

sl1pkn07 commented on 2015-04-29 19:28 (UTC)

@timocowchip. one is install and other is run and

timcowchip commented on 2015-04-29 19:25 (UTC)

I haven't tried the plugin with chromium from [extra] I read "The Widevine Media Optimizer is a browser plugin designed for the viewing of premium video content (only for chromium-dev)" and built chromium-dev (even though it took a long time to build)

sl1pkn07 commented on 2015-04-29 19:18 (UTC)

i mean if run chromium-widevine with chromium from [extra] not work for me

timcowchip commented on 2015-04-29 19:15 (UTC)

the plugin installs fine with chromium-dev and google-chrome-dev, it just doesn't work.

timcowchip commented on 2015-04-29 18:56 (UTC)

re: Your operating system is not supported. Widevine is available for Windows 7 and 8, Mac OS X 10.6 or later (Intel only)

timcowchip commented on 2015-04-29 18:49 (UTC)

re: and with chromium-widevine? my orignial comment was for your chromium-widevine-dev pkgbuild do you have a chromium-widevine pkgbuild?

sl1pkn07 commented on 2015-04-29 18:25 (UTC)

Your operating system is not supported. Widevine is available for Windows 7 and 8, Mac OS X 10.6 or later (Intel only) nothing to do, for the moment

sl1pkn07 commented on 2015-04-29 18:22 (UTC)

and with chromium-widevine?

timcowchip commented on 2015-04-29 17:38 (UTC)

same results with google-chrome-dev

timcowchip commented on 2015-04-28 22:08 (UTC)

shows up in chrome://plugins/ but says "Widevine Video Optimizer is not installed"

Scimmia commented on 2015-04-21 03:02 (UTC) (edited on 2016-02-15 14:58 (UTC) by Scimmia)

FYI, I've got updates for this package set on a timer. When there's a new chrome, this package should be automatically updated within 3 hours at the most. No need to notify me of a 404 download error.

tancrackers commented on 2015-04-20 12:23 (UTC)

This works beautifully on Netflix!

Scimmia commented on 2015-04-17 05:13 (UTC)

I hope you don't mind, I copied part of your pkgver function for a new chromium-widevine package that will work with the next version of chromium in [extra]. If you want credit, let me know how you want it in the PKGBUILD.

sl1pkn07 commented on 2015-02-13 15:34 (UTC)

because in the next release of chromium-dev, need this package for build the launcher for this plugin please wait

tiktak commented on 2015-02-13 15:33 (UTC)

I notice it works with google-chrome-unstable and that it contains an additional file, but after trying to copy it to chromium-dev, same result, still doesn't work.

tiktak commented on 2015-02-13 15:29 (UTC)

I installed chromium-dev then this plugin, but it appears neither in chrome://plugins nor chrome://components. What should I do?