Package Details: google-chrome 131.0.6778.69-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: 2244
Popularity: 7.52
First Submitted: 2010-05-25 20:25 (UTC)
Last Updated: 2024-11-12 20: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 .. 114 115 116 117 118 119 120 121 122 123 124 .. 157 Next › Last »

Commander commented on 2013-11-14 22:43 (UTC)

New version out: http://googlechromereleases.blogspot.se/ 31.0.1650.57

dmoebius commented on 2013-11-14 09:36 (UTC)

eula changed again. The new md5 sum is '6d57da7476a4b1b7a81821d9c036425c'.

ruario commented on 2013-10-23 08:19 (UTC)

@SysGhost: You have misunderstood. The checksum is not wrong for 30.0.1599.101. The reason it doesn't match the download is that the current stable Chrome is now 30.0.1599.114 (notice the higher stabilization branch number '114'). The problem is simply that the PKGBUILD is out of date, resulting in the version number and both the 32 and 64 bit checksums no longer matching. P.S. Read the PKGBUILD comments to understand how to check what the current version number is.

SysGhost commented on 2013-10-23 08:07 (UTC)

This PKGBUILD includes a 64 bit version of google-chrome too (Should be included in the "sources" section of this page) However, the md5sum in the PKGBUILD for the amd64 version "google-chrome-stable_30.0.1599.101_amd64.deb" is not correct. The correct md5sum should be: 7ff0eed996de3015683e0159b87d4d6e Replace the line that reads: [ "$CARCH" = 'x86_64' ] && md5sums[0]='9abdef7ee0422f7dabb16941453551cc' ...with: [ "$CARCH" = 'x86_64' ] && md5sums[0]='7ff0eed996de3015683e0159b87d4d6e'

Det commented on 2013-10-18 19:25 (UTC)

+1 yeah :D. If nothing else, glad to see new users acquainting themselves with PKGBUILDs.

petko10 commented on 2013-10-17 21:33 (UTC)

+1 for the a3a49767c80e92cca63b7a33aadfb2af for eula . I put that hash as the second md5sum (above the line [ "$CARCH" = 'x86_64' ] && md5sums[0]='e4ab342703de87ec117cfea3951acce8' ) , and the package installed normally.

grimsbain commented on 2013-10-17 17:28 (UTC)

After having an install error I downloaded the eula and checked the md5sum and it came back a3a49767c80e92cca63b7a33aadfb2af same as Cameri.

ichramm commented on 2013-10-17 16:28 (UTC)

Weird, just updated google-chrome and eula's MD5 is 7ae235c61533ba1108b03d42c49e00bd /cc @Cameri

Cameri commented on 2013-10-17 13:54 (UTC)

The eula changed. New md5sum: a3a49767c80e92cca63b7a33aadfb2af

beststone commented on 2013-10-17 07:40 (UTC)

I have same error. So I temporarily upgraded with "packer" command. $ packer -S --skipinteg google-chrome-beta Later fixed this package, it will upgraded normally.

« First ‹ Previous 1 .. 114 115 116 117 118 119 120 121 122 123 124 .. 157 Next › Last »