Package Details: google-chrome 58.0.3029.81-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: 1512
Popularity: 31.825167
First Submitted: 2010-05-25 20:25
Last Updated: 2017-04-19 18:21

Dependencies (10)

Required by (17)

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

ppc52776 commented on 2017-04-21 01:54

if you have CompositorTileW problem, try to increase the font size by ctrl + '+'
[ 1402.814324] CompositorTileW[6608]: segfault at 39 ip 00005609d8ce6af0 sp 00007f2ec1f19068 error 6 in chrome[5609d81ba000+6a81000]
[ 1424.090013] CompositorTileW[6989]: segfault at 39 ip 00005609d8ce6af0 sp 00007f2ec1718068 error 6 in chrome[5609d81ba000+6a81000]
[ 1494.299058] CompositorTileW[7361]: segfault at 39 ip 00005609d8ce6af0 sp 00007f2ec1718068 error 6 in chrome[5609d81ba000+6a81000]
[ 1494.319679] CompositorTileW[7360]: segfault at 90 ip 00005609d8cf1c80 sp 00007f2ec1f19130 error 4 in chrome[5609d81ba000+6a81000]
[ 1503.438023] CompositorTileW[7405]: segfault at 90 ip 00005609d8cf1c80 sp 00007f2ec1f191c0 error 4 in chrome[5609d81ba000+6a81000]
[ 1782.250281] CompositorTileW[7798]: segfault at 39 ip 00005609d8ce6af0 sp 00007f2ec1717fd8 error 6 in chrome[5609d81ba000+6a81000]
[ 1787.740639] CompositorTileW[7894]: segfault at 39 ip 00005609d8ce6af0 sp 00007f2ec1718068 error 6 in chrome[5609d81ba000+6a81000]

Det commented on 2017-04-07 12:10

I dunno? Rename your settings dirs (~/.cache/google-chrome/, ~/.config/google-chrome/), start in incognito, swap between the /usr/bin launcher and the one from /opt/google/chrome/ directly, extract the .deb and put the extension there, or try copying *all* the contents to /opt/google/chrome/, use "--enable-logging --v=1" (, etc.

DescartesHorse commented on 2017-04-07 11:48

@Det - yeah, it does work on other distro's like this. I dropped it in on a fresh Ubuntu with fresh Google Chrome installed, into /opt/google/chrome/extensions, and as soon as I opened up Chrome it appeared :( Went through that FAQ, and still in the same position. Any other ideas as to what may be going on, or how I can dig deeper to see where Chrome may be looking?

Det commented on 2017-03-31 07:03

Easy way to check is for example to put an "exit" on line 51 and go to the pkg/opt/google/chrome/cron/ directory yourself (or Ctrl+C anytime after extraction and before that line):

It basically seems to create and re-enable the Chrome repo for Debian/Ubuntu, which we don't need, since we don't have APT.

evilrob commented on 2017-03-31 03:09

Please excuse my noob question, but I'm trying to understand all these PKGBUILD files that I'm supposed to audit before letting them loose on my system. ;) What is the purpose of the Debian Cron jobs that Google has in their deb, and why are they removed in the PKGBUILD file?

Det commented on 2017-03-23 16:11

Should work like that, yes, dunno why not, because not a whole lot is changed in the packaging. Does it work on some other distro's Chrome?

Maybe have a look at the "What are some common mistakes when installing with the preferences file?" in the FAQ?:

DescartesHorse commented on 2017-03-23 05:25

Hey, I've got a custom extension internally to our company (extension ID.json with update URL). Based on Google Chrome's documentation at I should be able to plop this in either /opt/google/chrome/extensions/ or /usr/share/google-chrome/extensions/ and have Google Chrome pick this up. This is not happening - wondering if this package is looking for extensions in another place? If so, where is that? :)

Det commented on 2017-03-19 10:23

@solus667, check first also, if it's updated.

Det commented on 2017-03-17 04:16

Anyone else who would not like to bother themselves with the Pinned Comments?

Musikolo commented on 2017-03-17 03:16

@Det, I'm getting the following validation error:

[musikolo@MyPc google-chrome]$ makepkg -rs
==> Making package: google-chrome 57.0.2987.98-1 (jue mar 16 22:12:57 CDT 2017)
==> Checking runtime dependencies...
==> Checking buildtime dependencies...
==> Retrieving sources...
-> Downloading google-chrome-stable_57.0.2987.98_amd64.deb...
--2017-03-16 22:12:57--
Loaded CA certificate '/etc/ssl/certs/ca-certificates.crt'
Resolving,,, ...
Connecting to||:443... connected.
HTTP request sent, awaiting response... 200 OK
Length: 47312644 (45M) [application/x-debian-package]
Saving to: ‘google-chrome-stable_57.0.2987.98_amd64.deb.part’

google-chrome-stable_57.0.2987.98_amd64.deb.part 100%[=========>] 45,12M 13,6MB/s in 3,4s

2017-03-16 22:13:01 (13,3 MB/s) - ‘google-chrome-stable_57.0.2987.98_amd64.deb.part’ saved [47312644/47312644]

-> Found eula_text.html
-> Found
==> Validating source files with md5sums...
google-chrome-stable_57.0.2987.98_amd64.deb ... FAILED
eula_text.html ... Skipped ... Passed
==> ERROR: One or more files did not pass the validity check!

I've deleted the file and repeated the process a few times. Very weird the checksum doesn't match up!

Could you please review to confirm what's wrong?

Thank you!

All comments