Package Details: google-chrome 64.0.3282.167-1

Git Clone URL: (read-only)
Package Base: google-chrome
Description: The popular and trusted web browser by Google (Stable Channel)
Upstream URL:
Keywords: chromium
Licenses: custom:chrome
Submitter: None
Maintainer: Det
Last Packager: Det
Votes: 1658
Popularity: 34.697012
First Submitted: 2010-05-25 20:25
Last Updated: 2018-02-13 23:23

Dependencies (14)

Required by (15)

Sources (3)

Pinned Comments

Det commented on 2017-10-01 00:35

The final vote. “What should be the pkgdesc of AUR/google-chrome?” With 82 votes:

● "One fast, simple, and secure browser for all your devices (Stable Channel)" - 17 votes (21%)
● "The popular and trusted web browser by Google (Stable Channel)" - 65 votes (79%)

Now, my deciding vote of 49 votes will be cast and the winner is...
, I’m kidding, I’m kidding. Pkgdesc changed. ^^

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

Latest Comments

Det commented on 2018-02-06 12:46


I just use pkill.

beoldhin commented on 2018-02-06 09:51

Added a Github page describing the shutdown problems observed with chrome and chromium (includes fix to "Chrome didn't shutdown correctly"):

rakotomandimby commented on 2018-02-05 19:05

You're right, the synchronization screws it all. If I dont sync, it restarts all right. If I ever sign in, it syncs then I cant relaunch it unless I remove config.

Workaround it to stay signed out for the moment. But that's weird.

I'll configure synchronization one by one and tell.

Det commented on 2018-02-05 18:59

Probably you're not closing it right. Or it happens after syncing extensions, etc.

I'd go step by step.

rakotomandimby commented on 2018-02-05 18:44

But it only works 1 launch after the remove of the directory: if I close Chrome and relaunch again, it fails.

rakotomandimby commented on 2018-02-05 18:41

"rm -rf ~/.config/google-chrome ; rm -rf ~/.cache/google-chrome" made it works for me...

Det commented on 2018-02-03 13:21

What else is there besides the sums?

MarcinWieczorek commented on 2018-02-03 09:40

Please retire md5 and switch to sha256 at least for checksums :)

Det commented on 2018-02-02 03:13

@belochub: for the differences between those, see:

The other two are:,

fuan_k commented on 2018-01-23 19:16

@clepi: from my experience, it's Chrome populating its History information or something. You can see it read a lot of things from disk and load it in memory. Can be databases generated by some extensions too, mostly related to history and cache usually.

All comments