Package Details: google-chrome 129.0.6668.58-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: 2237
Popularity: 8.05
First Submitted: 2010-05-25 20:25 (UTC)
Last Updated: 2024-09-17 21:41 (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 .. 58 59 60 61 62 63 64 65 66 67 68 .. 157 Next › Last »

Det commented on 2017-03-31 07:03 (UTC) (edited on 2017-03-31 07:05 (UTC) by Det)

Easy way to check is for example to put an "exit" on line 51 and go to the pkg/opt/google/chrome/cron/ directory yourself (or Ctrl+C anytime after extraction and before that line): https://aur.archlinux.org/cgit/aur.git/tree/PKGBUILD?h=google-chrome#n51 It basically seems to create and re-enable the Chrome repo for Debian/Ubuntu, which we don't need, since we don't have APT.

evilrob commented on 2017-03-31 03:09 (UTC)

Please excuse my noob question, but I'm trying to understand all these PKGBUILD files that I'm supposed to audit before letting them loose on my system. ;) What is the purpose of the Debian Cron jobs that Google has in their deb, and why are they removed in the PKGBUILD file?

Det commented on 2017-03-23 16:11 (UTC)

Should work like that, yes, dunno why not, because not a whole lot is changed in the packaging. Does it work on some other distro's Chrome? Maybe have a look at the "What are some common mistakes when installing with the preferences file?" in the FAQ?: https://developer.chrome.com/extensions/external_extensions#faq

DescartesHorse commented on 2017-03-23 05:25 (UTC)

Hey, I've got a custom extension internally to our company (extension ID.json with update URL). Based on Google Chrome's documentation at https://developer.chrome.com/extensions/external_extensions I should be able to plop this in either /opt/google/chrome/extensions/ or /usr/share/google-chrome/extensions/ and have Google Chrome pick this up. This is not happening - wondering if this package is looking for extensions in another place? If so, where is that? :)

Det commented on 2017-03-19 10:23 (UTC)

@solus667, check first also, if it's updated.

Det commented on 2017-03-17 04:16 (UTC)

Anyone else who would not like to bother themselves with the Pinned Comments?

Musikolo commented on 2017-03-17 03:16 (UTC)

@Det, I'm getting the following validation error: [musikolo@MyPc google-chrome]$ makepkg -rs ==> Making package: google-chrome 57.0.2987.98-1 (jue mar 16 22:12:57 CDT 2017) ==> Checking runtime dependencies... ==> Checking buildtime dependencies... ==> Retrieving sources... -> Downloading google-chrome-stable_57.0.2987.98_amd64.deb... --2017-03-16 22:12:57-- https://dl.google.com/linux/direct/google-chrome-stable_current_amd64.deb Loaded CA certificate '/etc/ssl/certs/ca-certificates.crt' Resolving dl.google.com... 173.194.219.93, 173.194.219.91, 173.194.219.190, ... Connecting to dl.google.com|173.194.219.93|:443... connected. HTTP request sent, awaiting response... 200 OK Length: 47312644 (45M) [application/x-debian-package] Saving to: ‘google-chrome-stable_57.0.2987.98_amd64.deb.part’ google-chrome-stable_57.0.2987.98_amd64.deb.part 100%[=========>] 45,12M 13,6MB/s in 3,4s 2017-03-16 22:13:01 (13,3 MB/s) - ‘google-chrome-stable_57.0.2987.98_amd64.deb.part’ saved [47312644/47312644] -> Found eula_text.html -> Found google-chrome-stable.sh ==> Validating source files with md5sums... google-chrome-stable_57.0.2987.98_amd64.deb ... FAILED eula_text.html ... Skipped google-chrome-stable.sh ... Passed ==> ERROR: One or more files did not pass the validity check! I've deleted the file and repeated the process a few times. Very weird the checksum doesn't match up! Could you please review to confirm what's wrong? Thank you!

guilherme.rialli commented on 2017-03-17 02:23 (UTC)

In the last update of the package had this error: Validating source files with md5sums ... Google-chrome-stable_57.0.2987.98_amd64.deb ... FAILED Eula_text.html ... Skipped Google-chrome-stable.sh ... Passed ==> ERROR: One or more files did not pass the validity check! ==> ERROR: Makepkg was unable to build google-chrome. Solution:$ makepkg -g >> PKGBUILD

lowsky commented on 2017-03-17 01:45 (UTC) (edited on 2017-03-17 01:46 (UTC) by lowsky)

Anyone having this issue? Validating source files with md5sums... google-chrome-stable_57.0.2987.98_amd64.deb ... FAILED eula_text.html ... Skipped google-chrome-stable.sh ... Passed ==> ERROR: One or more files did not pass the validity check! ==> ERROR: Makepkg was unable to build google-chrome.

fuan_k commented on 2017-03-14 11:59 (UTC) (edited on 2017-03-14 12:08 (UTC) by fuan_k)

Anyone got an issue loading their user profile after latest update? :( Edit: nevermind, after starting chrome with --disable-extensions, then without again, it loaded fine again. Weird.

« First ‹ Previous 1 .. 58 59 60 61 62 63 64 65 66 67 68 .. 157 Next › Last »