Package Details: google-chrome 54.0.2840.71-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: 1393
Popularity: 42.804236
First Submitted: 2010-05-25 20:25
Last Updated: 2016-10-21 11:01

Required by (17)

Sources (4)

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

WoefulDerelict commented on 2016-10-21 16:51

Unfortunately the random segfaults persist on some systems running the recently promoted update to the stable 54.x family, 54.0.2840.71. I have not managed to sus out what changed after the 53.x series to introduce this behaviour as it does not seem to affect every system. It appears that Chrome has been sending out crash reports since I started running into this issue in 54.0.2840.59 so hopefully the team is not entirely unaware of this issue even tho I don't see a proper bug report for it.

Det commented on 2016-10-20 15:43

53.x is available in many places:

E: Does seem, btw, like there's a pattern with whenever Stable and Beta channels get bumped to be in sync there's always some segfault issues. It's not as prevalent when each channel's got its own major version.

Pandoras_Fox commented on 2016-10-20 15:42

Starting with Chrome 54.x, I'm getting some pretty regular segfaults. I tried going farther up the branches to beta/dev/chromium builds and they're still present there as well, so make sure you still have your 53.x package available to reinstall if this hits you.

I'm still poking through the coredumps to try and figure this out. Sometimes it happens on idle, sometimes it happens while typing, but there doesn't appear to be an upstream bug report yet, so I'll work on getting that on their radar.

Det commented on 2016-10-18 15:58

The hell it is.

proof commented on 2016-10-18 14:35

Bad checksum, bad pkgver in build.

lonaowna commented on 2016-10-17 08:37

The update function in the .install file is no longer needed. It's function is already handled by /usr/share/libalpm/hooks/{update-desktop-database.hook,gtk-update-icon-cache.hook}

lsiudut commented on 2016-10-15 08:16

I can also confirm that 54.0.2840.59-1 is crashing very often. For me it happens mostly on complex sites like Facebook, eg. sending messages on chat is crashing browser immediately.

amrit commented on 2016-10-14 21:55

I am getting Segmentation fault too. Happens randomly every 2-10 minutes. It's really annoying.

DrDoctor commented on 2016-10-14 04:38

After updating, I have gotten several random segfaults.

Program terminated with signal SIGSEGV, Segmentation fault.
#0 0x0000562e00214583 in ?? ()
[Current thread is 1 (Thread 0x7f63bc24a700 (LWP 3025))]
(gdb) bt
#0 0x0000562e00214583 in ()
#1 0x00007f63bc249501 in ()
#2 0x0100000000000000 in ()
#3 0x000032827b536210 in ()
#4 0x0000000000000000 in ()

This has happened five times in the span of 4 hours.

keysona commented on 2016-10-11 02:28

ok, I have solved my problem.

"A changes in your account that requires you sign in again."

If you use gnome, you can go to Setting and add Google account in Online Account.

From this:

All comments