Package Details: google-chrome 77.0.3865.90-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: 1837
Popularity: 12.796864
First Submitted: 2010-05-25 20:25
Last Updated: 2019-09-18 18:10

Dependencies (13)

Required by (26)

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 sha512sums 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

« First ‹ Previous 1 2 3 4 5 6 7 8 9 ... Next › Last »

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.

Alad commented on 2019-01-06 00:32

I came for the spammers and stayed for the pointless polls.

diogobaeder commented on 2018-12-26 07:01

I'm getting an error with version 71.0.3578.98-1 when trying to enable fullscreen videos (e.g. YouTube or Vimeo): "TypeError: fullscreen error" - it seems to be related to this other error: "Failed to execute 'requestFullscreen' on 'Element': API can only be initiated by a user gesture."

It doesn't seem to be related to my DE, though, since fullscreen works fine in both Firefox and Chromium (version 71.0.3578.98-2).

Is anybody else affected by this?

Det commented on 2018-12-22 13:48

@voot, it's built for Arch, not Ubuntu, which helps.

E: I can say that now because I don't maintain it. ( ͡° ͜ʖ ͡°)

voot commented on 2018-12-22 12:59

I used this for a year and half, though had an issue where no window would appear on startup though the chrome process was clearly present.

I'm going to try chromium which does not have this issue whatsoever.

(btw I start xfce with exec startxfce4 on every boot..., not sure if that was part of the issue, but whatever the case chromium runs fine)

Chromium really isn't that different than this after all...

Det commented on 2018-12-19 02:17

@bluedreamer, perhaps it's got a different compression or exported elsewhere as per makepkg.conf.

Should still find the package, but I don't even recall how that works.