Package Details: google-chrome 56.0.2924.87-1

Git Clone URL: (read-only)
Package Base: google-chrome
Description: An attempt at creating a safer, faster, and more stable browser (Stable Channel)
Upstream URL:
Licenses: custom:chrome
Submitter: None
Maintainer: Det
Last Packager: Det
Votes: 1479
Popularity: 40.206297
First Submitted: 2010-05-25 20:25
Last Updated: 2017-02-03 20:10

Dependencies (10)

Required by (18)

Sources (3)

Pinned Comments

Det commented on 2016-03-09 05:01

✔ 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 }'

Det commented on 2016-03-02 20:53

✔ OBS: 32-bit support for Google Chrome Stable Channel has been dropped as well. Either upgrade to 64-bit, or stick to [extra]/chromium, which will continue to be updated:


Latest Comments

zerophase commented on 2017-02-21 00:54

Don't believe so. Is chrome crashing for you?

yakshaver commented on 2017-02-21 00:47

Is anyone else getting a segfault on every first page load?

Det commented on 2017-02-03 20:11

Aaah, sorry, too careless. Fixed.

Xavion commented on 2017-02-03 19:44

A tiny bit of housekeeping: you've got an extra colon after 'kdialog' in the PKGBUILD (making it "kdialog::"). This prevents 'pacman' from displaying '[installed]' after it. I just went and tried to install 'kdialog', not realising I didn't need to.

Det commented on 2017-01-24 14:40

> wiyarmir [1] added the following comment to google-chrome [2]:
> The build script complained about fakeroot command being missing although not being stated as a dependency


Det commented on 2017-01-23 18:18

> DeadMetaler flagged google-chrome out-of-date on 2017-01-23 for the following reason:

That's Chrome OS.

fuan_k commented on 2017-01-20 17:29

Thanks Det. Found that 55.0.2873.0 (unstable channel) was the version that started breaking. I've updated my bug report. Looks like someone is on the case now.

Det commented on 2017-01-19 15:11

> rborja flagged google-chrome out-of-date on 2017-01-19 for the following reason:
> I get a 404 error when running wget command.

It's not out-of-date..

Det commented on 2017-01-17 18:48

For sure, but I was just trying to help in bisecting.

It's much easier for the devs when you've narrowed down the exact build ("1.14.1 works, 1.14.2 is broken").

fuan_k commented on 2017-01-17 18:11

Thanks Det, but I suspect it's an issue in the chromium code base as the bug didn't occur in 53.0.2785.143, and it occurs in 55.0.2883.87 (as stated in the bug report).
Hopefully they will notice it and fix it eventually.

All comments