Package Details: google-chrome 72.0.3626.119-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: luzifer
Last Packager: luzifer
Votes: 1788
Popularity: 15.467979
First Submitted: 2010-05-25 20:25
Last Updated: 2019-02-21 20:46

Dependencies (13)

Required by (19)

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, there's a new version. Simply flag the package.

You can check for new Linux releases in:, or use:

$ curl -sL | gzip -df | tr ' ' '\n' | grep -e name= -e ver= | cut -d '"' -f2 | sed 'N;s/\n/ /'

For new MD5: $ curl -sL | sed -n '35p'

Latest Comments

1 2 3 4 5 6 ... Next › Last »

joelk commented on 2019-02-21 16:31

So, I uninstalled gnome-keyring and google-chrome-beta continued to work correctly. It loads and exits normally. Next I installed google-chrome-stable, tested to see that it worked correctly, then turned on Google Sync, and it crashed again just as it did before. I could get it to run by deleting .config/google-chrome but as soon as I turned on Sync again it crashed. Finally, I uninstalled libgnome-keyring (to do this I had to uninstall gksu, which I suppose I should have done anyway), started google-chrome-stable, turned on Sync and now it works correctly.

So to summarize, google-chrome seems to require that NEITHER gnome-keyring NOR libgnome-keyring be installed, or alternatively if libgnome-keyring is installed then gnome-keyring is needed temporarily when turning on Sync and it can subsequently be uninstalled. I have no explanation, but there it is.

leopicasso commented on 2019-02-21 09:26

Thanks for the information on the site. > Five Nights at Freddy's

luzifer commented on 2019-02-21 09:26

No XFCE, nothing containing gnome in the name. Using i3 as a window manager, avoiding packages belonging to Gnome or KDE.

joelk commented on 2019-02-21 03:30

Do you use xfce on any of them? Do you have libgnome-keyring (needed by gksu) on any of them?

luzifer commented on 2019-02-20 22:45

I do have neither gnome-keyring nor kwallet and all three variants of google-chrome do run quite fine on multiple machines of mine having turned on Google Sync on all of them. So there is no default dependency to those two packages.

joelk commented on 2019-02-20 22:04

I guess I can boil it down to a few key lines. I apologize if I'm spamming the board. I was able to run and close the program multiple times without starting google sync. But after I logged into a google account and started sync and then closed the browser, I could not re-open it. Each time that it ran successfully, the first 3 lines of terminal output were like these: mkdir: cannot create directory ‘/home/testuser/.local/share/applications’: File exists touch: cannot touch '/home/testuser/.local/share/applications/mimeapps.list': Not a directory Gkr-Message: 13:21:39.239: secret service operation failed: The name org.freedesktop.secrets was not provided by any .service files [17060:17060:0219/] InitializeSandbox() called with multiple threads in process gpu-process.

The last time (when it crashed) the org.freedesktop.secrets message was missing. The ONLY output was: mkdir: cannot create directory ‘/home/testuser/.local/share/applications’: File exists touch: cannot touch '/home/testuser/.local/share/applications/mimeapps.list': Not a directory [18518:18518:0219/] InitializeSandbox() called with multiple threads in process gpu-process.

Maybe the option is that it requires EITHER gnome-keyring or kwallet.

joelk commented on 2019-02-20 18:25

The crashes occurred yesterday, before I installed gnome-keyring. Now it's running fine -- I can load it and close it repeatedly without crashing. When it crashed, I didn't find any crash reports or any logs that seemed useful and afterwards I deleted the entire google-chrome directory. Then I installed google-chrome-beta and I did save a set of terminal outputs documenting several runs from initial installation until it crashed. The outputs appeared to be exactly the same as with the stable version. But it seems like a lot to post in these comments. I'd post it in the ArchLinux Forum, but when I tried posting just a small part of that yesterday the admin threw it in the dustbin because I wasn't "asking for support". Where do you suggest posting it?

Pryka commented on 2019-02-20 08:22

@joelk Chrome should work without any kind of keyring installed on the system. So it is perfectly fine to have kwallet or keyring as an opt deps.

Run it via terminal and post some logs of this crash.

joelk commented on 2019-02-19 23:09

I think gnome-keyring should be a required, not optional, dependency. Without it, google-chrome crashes during start-up after sync has been turned on.

Det commented on 2019-01-06 11:26

@Alad, poll's over, bro.