Package Details: google-chrome-beta 75.0.3770.51-1

Git Clone URL: https://aur.archlinux.org/google-chrome-beta.git (read-only)
Package Base: google-chrome-beta
Description: The popular and trusted web browser by Google (Beta Channel)
Upstream URL: https://www.google.com/chrome
Keywords: chromium
Licenses: custom:chrome
Provides: google-chrome
Submitter: None
Maintainer: luzifer
Last Packager: luzifer
Votes: 343
Popularity: 0.210503
First Submitted: 2009-12-08 19:09
Last Updated: 2019-05-22 18:51

Dependencies (13)

Required by (24)

Sources (3)

Pinned Comments

Det commented on 2016-03-09 05:02

✔ NOTE. If the sha512sums don't match, there's a new version. Simply flag the package.

You can check for new Linux releases in: http://googlechromereleases.blogspot.com/search/label/Stable%20updates, or use:

$ curl -sL https://dl.google.com/linux/chrome/rpm/stable/x86_64/repodata/other.xml.gz | gzip -df | tr ' ' '\n' | grep -e name= -e ver= | cut -d '"' -f2 | sed 'N;s/\n/ /'

For new MD5: $ curl -sL https://dl.google.com/linux/chrome/deb/dists/stable/main/binary-amd64/Packages | sed -n '16p'

Latest Comments

« First ‹ Previous 1 2 3 4 5 6 7 8 9 10 11 ... Next › Last »

Det commented on 2015-09-18 09:07

Ok, don't yell(?!) about the font, it's a virtual dependency, provided by any font package you have. It means you need some of them.

Did you try with a clean profile or debugging the app? If you haven't replaced the dependencies with AUR versions that might not work, try renaming the folders ~/.config/google-chrome-beta and ~/.cache/google-chrome-beta.

schultzter commented on 2015-09-18 03:25

Also noticed this package depends on ttf-font, which doesn't seem to exist any more?!

schultzter commented on 2015-09-18 01:41

Am I the only one? I tried completely removing and re-installing. It happened with the 46.0.2490.22-1 version as well. I'm running stable now and it's working fine (so are Firefox, Chromium, and Vivaldi). Nothing in the forums.

[user@host ~]$ google-chrome-beta
Illegal instruction (core dumped)

[user@host ~]$ pacman -Qi google-chrome-beta
Name : google-chrome-beta
Version : 46.0.2490.33-1
Architecture : x86_64

Det commented on 2015-09-17 17:09

That's always the reason.

j3zz4h commented on 2015-09-02 21:41

The reason the checksum fails is because there is a new beta release.

(line 8)
--pkgver=45.0.2454.78
++pkgver=46.0.2490.13
(line 29)
--md5sums_i686=('86f89b18f0a4cff0243d5ba21e76ff17')
++md5sums_i686=('2bbaa53750bd6174af9e9a3fc6ace238')
(line 30)
--md5sums_x86_64=('3c9119aa02d2f550e29cfb959b116690')
++md5sums_x86_64=('37f75ae7b618a6cf1f48d20e8e1ddde1')

Det commented on 2015-08-27 12:02

Yeah it does. There's a new one up. Check the link, it's static.

dflt commented on 2015-08-27 10:06

# Check for new Linux releases in: http://googlechromereleases.blogspot.com/search/label/Beta%20updates
# or use: $ curl -s https://dl.google.com/linux/chrome/rpm/stable/x86_64/repodata/other.xml.gz | gzip -df | awk -F\" '/pkgid/{ sub(".*-","",$4); print $4": "$10 }'

@Det this really doesn't say why the checksum fails :)

Det commented on 2015-08-27 09:24

No, read the top of the PKGBUILD.

greyltc commented on 2015-08-27 08:58

Is the checksum correct?
I'm getting:

==> Validating source files with md5sums...
google-chrome-beta_45.0.2454.46_amd64.deb ... FAILED
==> ERROR: One or more files did not pass the validity check!

Det commented on 2015-08-26 17:49

Flags are now read directly from ~/.config/chrome-beta-flags.conf, while $CHROMIUM_USER_FLAGS is unsupported. Didn't bump the pkgrel.