Package Details: google-chrome 59.0.3071.115-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:
Keywords: browser chromium web
Licenses: custom:chrome
Submitter: None
Maintainer: Det
Last Packager: Det
Votes: 1559
Popularity: 25.232235
First Submitted: 2010-05-25 20:25
Last Updated: 2017-06-27 02:24

Dependencies (13)

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

voot commented on 2017-07-19 02:33

Noting here for others: I had an issue where manually installed microsoft fonts were causing 'aw snap' crashes.

It seems like the crashes only started with 59 as I didn't have the same crashes before that. Also, the 'aw snap' crashes occurred independent of my using stable/beta/dev channels installed via aur.

ppc52776 commented on 2017-06-18 18:48

If you have CompositorTileW problem, try to remove font 'opendesktop-fonts'.
[ 1402.814324] CompositorTileW[6608]: segfault at 39 ip 00005609d8ce6af0 sp 00007f2ec1f19068 error 6 in chrome[5609d81ba000+6a81000]

fuan_k commented on 2017-06-17 17:46

@TID91: isolate which versions are breaking, and report to the Chromium project?
I doubt that has anything to do with the way Chrome is packaged for Arch (but I could be wrong).

TiD91 commented on 2017-06-16 20:36

Hello, I'm experiencing a problem with Chrome: while uploading a fair amount of photos on Google Photos (over 1000 photos) or videos (45 videos), after two or three files processed Google Chrome gets stuck and the popup "Page unrensposive" comes out and I need to kill chrome.

I tried with Chromium on the official repositories and I have no problem with it.

Any idea why? Do you have any suggestion on how to debug this?

valandil commented on 2017-06-10 18:27

@Det I do, but after resigning it I had lost my Session Manager info.

I'll try with google-chrome-beta to see if it repopulates that info.

Det commented on 2017-06-10 08:00

@valandil, don't you sync your profiles with your Google account? commented on 2017-06-10 05:43

At the first start it is absolutely always chrome crashes, absolutely always. Such problems began with this version

valandil commented on 2017-06-10 01:03

@Det: Indeed, this works. I'll try to seek some help in the Chrome help forums, as I'd rather not lose my profile info.


Det commented on 2017-06-09 19:07

Can't say. Someone in there also had an i7-3770. If Beta Channel works (60.x), then maybe you just need to stick to that branch, until Stable syncs up.

Beta Channel also has its own settings dir, so maybe try a clean new profile by renaming ~/.config/google-chrome/ and ~/.cache/google-chrome/?

valandil commented on 2017-06-09 18:12

Have you ever seen this error?

I've come accross this in old bugs (, but I think they all pointed to the use of old processors that didn't support SSE2. I'm on an Intel Core i7 which definitely supports SSE2, and still have this mistake.

google-chrome-beta starts up just fine.

All comments