Package Details: google-chrome 130.0.6723.116-1

Git Clone URL: https://aur.archlinux.org/google-chrome.git (read-only, click to copy)
Package Base: google-chrome
Description: The popular web browser by Google (Stable Channel)
Upstream URL: https://www.google.com/chrome
Keywords: chromium
Licenses: custom:chrome
Submitter: None
Maintainer: gromit
Last Packager: gromit
Votes: 2243
Popularity: 7.15
First Submitted: 2010-05-25 20:25 (UTC)
Last Updated: 2024-11-05 19:02 (UTC)

Dependencies (12)

Sources (3)

Pinned Comments

gromit commented on 2023-04-15 08:22 (UTC) (edited on 2023-05-08 21:42 (UTC) by gromit)

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.

Latest Comments

« First ‹ Previous 1 .. 32 33 34 35 36 37 38 39 40 41 42 .. 157 Next › Last »

Det commented on 2019-12-01 17:09 (UTC) (edited on 2019-12-01 17:10 (UTC) by Det)

@kirk, no they not required if they optional.

Not sure what u mean? KDE has KDE stuff, GNOME has GNOME stuff.

kirk commented on 2019-12-01 17:08 (UTC)

Can someone clarify why the following optional dependencies are are required, especially taken into account that not all users are using the same window managers or environments?

optdepends=('kdialog: for file dialogs in KDE' 'gnome-keyring: for storing passwords in GNOME keyring' 'kwallet: for storing passwords in KWallet' 'gtk3-print-backends: for printing' 'libunity: for download progress on KDE' 'ttf-liberation: fix fonts for some PDFs (CRBug #369991)' 'xdg-utils')

Lot's of kde stuff here and keyring software, are those even necessary at all?

luzifer commented on 2019-11-24 13:11 (UTC)

@rsevero the message you've posted looks to me like a broken package file… Just try to build the package again. (If you're using makepkg just delete the tar.xz file and rebuild)

rsevero commented on 2019-11-24 10:00 (UTC)

Having trouble updating to version 78.0.3904.108-1. After tons of warnings I get the following error:

(1/1) reinstalling google-chrome [########################################################] 100% error: could not extract /opt/google/chrome/chrome (Lzma library error: No progress is possible) error: problem occurred while upgrading google-chrome ==> NOTE: Custom flags should be put directly in: ~/.config/chrome-flags.conf ==> NOTE: The launcher is called: 'google-chrome-stable' error: could not commit transaction error: failed to commit transaction (transaction aborted) Errors occurred, no packages were upgraded.

And the worse is that now I have no Chrome at all as apparently the previous version was uninstalled.

Any ideas on how to get Chrome back?

chrisu commented on 2019-11-23 15:57 (UTC)

I have managed to resolve the issue with version 78 by deleting the contents of ~/.config/google-chrome and restarting. It appears to be a chrome bug and not specific to Arch.

luzifer commented on 2019-11-16 14:34 (UTC)

@quite hmm I'm not sure this should be done. In the end the packages requiring chromium are expecting to find a Chromium browser while this package contains a Chrome browser. It doesn't listen on the same binary (and to prevent collisions it shouldn't do so) and it behaves differently… So I think I'll refrain from adding this as basically Chrome is not Chromium…

quite commented on 2019-11-16 09:58 (UTC) (edited on 2019-11-16 09:58 (UTC) by quite)

@luzifer, would you consider provides=('chromium')? Or is that mad? It would help pkgs that work with any chromium-based browser.

C_Schmidpeter commented on 2019-11-14 11:09 (UTC)

I tried to update from v72 to v78, but I got the following error message:

error: could not extract /opt/google/chrome/nacl_helper (Lzma library error: No progress is possible) error: problem occurred while installing google-chrome

chrisu commented on 2019-11-12 22:27 (UTC)

The update to chrome 78 has also broken it for me. Running chrome starts a number of chrome processes, but no window appears and it hangs. Neither --disable-gpu, nor --disable-software-rasterizer worked.

As NeonCloud noted, sudo google-chrome-stable --no-sandbox allows Chrome to load and display, but it's far from ideal.

Unfortunately, I am unable to downgrade to version 77 as only 78 is available to download from Google. I have installed Chromium, which at the time of install was version 77, and I am able to use that for now.

Det commented on 2019-11-07 12:31 (UTC)

@NeonCLoud, did you try clean profile or Chromium that's actually built for Arch?