Package Details: google-chrome 132.0.6834.159-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: 2259
Popularity: 9.32
First Submitted: 2010-05-25 20:25 (UTC)
Last Updated: 2025-01-28 23:25 (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 »

jheuel commented on 2020-01-08 16:24 (UTC)

The segfaults from last version seem to be fixed. At least I got a full day without crashes.

jamezrin commented on 2019-12-19 23:27 (UTC)

Latest version segfaults randomly. I cleared its data folder and will see if that fixes it. Doesn't happen with chromium though. Just like @Serial I'm using deepin DE.

Serial commented on 2019-12-14 19:11 (UTC)

The new version 79.0.3945.79-1 of google-Chrome is closing the browser by itself.

I already disabled all extensions and still keeps closing alone.

Note: Chromium (chromium) 79.0.3945.79-1 is doing the same thing. Browser closes by itself, even though it has disabled all extensions.

The software version is Arcolinuxb-deppin version 19.11.3

thankful

Serial

Angaziwa commented on 2019-12-03 02:12 (UTC)

why the password can't be synced from other devices?and even click save websites' password,there still is empty?

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…

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