Package Details: google-chrome-beta 63.0.3239.90-1

Git Clone URL: (read-only)
Package Base: google-chrome-beta
Description: The popular and trusted web browser by Google (Beta Channel)
Upstream URL:
Keywords: chromium
Licenses: custom:chrome
Provides: google-chrome
Submitter: None
Maintainer: Det
Last Packager: Det
Votes: 334
Popularity: 2.686070
First Submitted: 2009-12-08 19:09
Last Updated: 2017-12-11 22:19

Dependencies (14)

Required by (14)

Sources (3)

Pinned Comments

Det commented on 2016-03-09 05:02

✔ NOTE If the md5sums don't match, don't post the makepkg output. Simply flag the package.

You can check for new Linux releases in:, or use: $ curl -s | gzip -df | awk -F\" '/pkgid/{ sub(".*-","",$4); print $4": "$10 }'

Latest Comments

Det commented on 2017-10-26 19:13

'xed in

funn commented on 2017-10-26 19:01

Build fails with the following message:
gzip: /home/det/.cache/pacaur/google-chrome-beta/pkg/google-chrome-beta/usr/share/man/man1/google-chrome-beta.1: No such file or directory

Det commented on 2017-08-05 06:16

Yes, seems they added and on top of those in /opt/google/chrome-beta/swiftshader/.

chetgurevitch commented on 2017-08-04 22:59

Package size just jumped from 265mb to 345mb for me (using PKGEXT=.pkg.tar). From diffing the v60 and v61 tarballs it seems like the gl and widevine libs increased drastically in size, commonly doubling. Notably opt/google/chrome-beta/ seems to be over 150 times its previous size.

I don't see anything that needs to be addressed in the packaging, just putting this out there for anyone else wondering.

Edit: seems like it's only a difference of 12mb compressed.

Det commented on 2016-10-06 15:02



Scimmia commented on 2016-10-06 14:55

Ping? Provides array is wrong.

Scimmia commented on 2016-09-21 05:47

This no longer provides pepper-flash, does it?

jshap70 commented on 2016-09-12 05:49

build 54.0.2840.16-2 has begun to segfault on me at seemingly random intervals. Sometimes it will go for 30 minutes and sometimes it only lasts 5. It doesn't look like there's a log it's leaving behind either, so I'm not even sure how to debug it or if it is even chrome or some other dependency. Anyone else having similar problems?

Brottweiler commented on 2016-09-09 14:08

Yep, it's fixed. thanks.

Det commented on 2016-09-09 13:05

Should be fixed in -2.

All comments