Arch Linux User Repository

When reporting this package as outdated make sure there is indeed a new version for Linux Desktop. You can have a look at the "Stable updates" tag in Release blog for this.

You can also run this command to obtain the version string for the latest chrome version:

$ curl -sSf https://dl.google.com/linux/chrome/deb/dists/stable/main/binary-amd64/Packages | \
     grep -A1 "Package: google-chrome-stable" | \
     awk '/Version/{print $2}' | \
     cut -d '-' -f1

Do not report updates for ChromeOS, Android or other platforms stable versions as updates here.

just updated my google-chrome to:

Google itself tells me: Version 75.0.3770.100 (Offizieller Build) (64-Bit)

but yay tells me it installed ok: google-chrome-75.0.3770.142-1

i used yay -Su

Google works ok, but are these two version different??

info: CPU: Quad Core Intel Core i5-6400 (-MCP-) speed/min/max: 800/800/3300 MHz Kernel: 5.1.16-1-MANJARO x86_64 Up: 26m Mem: 4018.2/15986.4 MiB (25.1%) Storage: 3.18 TiB (11.3% used) Procs: 234 Shell: bash 5.0.7 inxi: 3.0.34

Pamac refused to install: database locked

How to enable dark mode? I'm using Arch Linux and KDE plasma. GTK "Prefer Dark theme" is enabled but my google chrome still not in dark mode.

I've installed dark theme but I want dark mode. Address bar still white.

Help me. lol

Flash not present on Chrome-Browser-Stable.

The flash bug has been accepted by Chromium: https://bugs.chromium.org/p/chromium/issues/detail?id=949312

By the way, it's quite strange that Chromium still works with flash while Chrome does not.

+1 flash not work. Temporary solution is to use

google-chrome-stable --no-sandbox

But you may get an ugly warning and may be not safe?

Flash cannot be used after the last version update

The launcher script /usr/bin/google-chrome-stable in this package mangles flags that contain spaces or quotes. I fixed this but don't know where to submit the fix. Here is a gist with my adjustments:

https://gist.githubusercontent.com/bparsons/eedfebb01b7836f754eba88d36efe5ba/raw/4ea8792910ec8552f70c686ec3bdc675aaa7e2ce/google-chrome-stable

@kronikpillow like @Det already commented and pinned: In those cases just flag the package outdated...

==> Validating source files with sha512sums... google-chrome-stable_73.0.3683.86_amd64.deb ... FAILED eula_text.html ... Passed google-chrome-stable.sh ... Passed ==> ERROR: One or more files did not pass the validity check!

@wingsuit, it's a binary pacakge, and hence mostly why. It was very much voted "trusted", and has +50% usage share in the world, but sure - not in the official repo. Just in Arch it's/used to be crashy, so Chromium, built for Arch, is better.

@jfcandidofilho, it was something like googling the "chrome deb/rpm repo" and prob also the URL in the /etc/cron.daily/ job that gets cleaned up from the package thru the line at the end of the PKGBUILD, which @luz also kept. I quit Arch & Linux, so my memory's a bit fading on these.

Did ctrl+wheel zoom on websites stop working for anybody else along the way? It only works in PDF.js and other resource views now. Since I haven't used Chrome in a long time, I can't determine when the problem was introduced.

Perhaps it's just my configuration? kwin + x11 + synaptics driver.

Is anyone have a strange download issue with v73.0.3683.75?

When I try to download a file bigger than ~100mb It just stops at 100% and nothing is happening, no matter how long I wait.

I tried in incognito, I restarted all Chrome settings, removed all extensions - nothing.

The only solution for me is to downgrade to v72.

Anyone?

"The popular web browser by Google (Stable Channel)"

I think we can all agree this software isn't trusted. It would be in the official repositories if it was.

@Det it's a bit unrelated to everything but where did you find those links for checksum and releases? I was googling about the checksum not working and if it weren't for you, I would fail to find a file with the checksum.

Of course, I could always direct myself towards the AUR but I sincerely couldn't find this info. I might just be blind...

Edit: I'm not well versed in packages functionality but we need an SHA512 and the file provides only SHA256, SHA1 and MD5sum. Is there a way to use MD5sum for that deb file only?

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.

Thanks for the information on the site. https://fivenights-at-freddys.com > Five Nights at Freddy's

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

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

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.

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/132139.267497:ERROR:sandbox_linux.cc(364)] 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/132524.832368:ERROR:sandbox_linux.cc(364)] InitializeSandbox() called with multiple threads in process gpu-process.

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

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?

@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.

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.

@Alad, poll's over, bro.

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

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?

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

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

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

@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.

@bluedreamer I just tried to reproduce your error and wasn't able to. makepkg created exactly that package your makepkg is complaining about and installing it was successful… - I've no clue what went wrong between build and install in your output…

Any idea why makepkg is failing?

user@kobold:~/code/google-chrome]$ makepkg -i ==> Making package: google-chrome 71.0.3578.98-1 (Tue 18 Dec 2018 08:17:36 AM MST) ==> Checking runtime dependencies... ==> Checking buildtime dependencies... ==> Retrieving sources... -> Found google-chrome-stable_71.0.3578.98_amd64.deb -> Found eula_text.html -> Found google-chrome-stable.sh ==> Validating source files with sha512sums... google-chrome-stable_71.0.3578.98_amd64.deb ... Passed eula_text.html ... Passed google-chrome-stable.sh ... Passed ==> Extracting sources... -> Extracting google-chrome-stable_71.0.3578.98_amd64.deb with bsdtar ==> Removing existing $pkgdir/ directory... ==> Entering fakeroot environment... ==> Finished making: google-chrome 71.0.3578.98-1 (Tue 18 Dec 2018 08:17:36 AM MST) ==> Installing package google-chrome with pacman -U... loading packages... error: '/home/user/code/google-chrome/google-chrome-71.0.3578.98-1-x86_64.pkg.tar.xz': could not find or read package ==> WARNING: Failed to install built package(s).

Good-bye, friends.

I've left Arch a long time ago, and now I'm leaving these too.

To you.

Don't work Widevine plugin in latest version, example: netflix video crash.

I have error: [2399:2399:1112/180141.800601:ERROR:input_method_base.cc(146)] Not implemented reached in virtual ui::InputMethodKeyboardController *ui::InputMethodBase::GetInputMethodKeyboardController()Using InputMethodKeyboardControllerStub

Error shows up when i interact with chrome ui and it lags for a second (opening menu or typing to address bar).

The Problem is gone again. lol

@spsf64 The problem appears again.

@spsf64 Installed with yaourt -S ice-ssb, it has solved my issue. Thanks.