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.00
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 .. 78 79 80 81 82 83 84 85 86 87 88 .. 157 Next › Last »

gideonite commented on 2015-07-24 18:31 (UTC)

I'm getting some very strange behavior since my last update. I have trouble starting google-chrome-stable --- it will randomly fail. Finally, after trying a number of times, it sort of "catches on" and is fine after that. When I run strace the program halts consistently at a read command. Here are the last few lines of strace's output: http://sprunge.us/cePj. Also worth mentioning is that each time I run google-chrome-stable and no browser window shows up, chrome processes are kicked off (I can see them using `ps aux`). Any ideas?

Paviluf commented on 2015-07-15 00:17 (UTC)

It's the first time I try to install Google Chrome and I misunderstood your previous comment. I thought you won't update it anymore. Sorry ;)

Det commented on 2015-07-15 00:12 (UTC)

No.. I've had the habit of keeping this up-to-date since 2013, you just have to give me more than 4 hours, when updating is impossible.

Paviluf commented on 2015-07-15 00:04 (UTC)

Hello Det, Do you plan to keep the PKGBUILD up to date after each Google Chrome release or do we need to update Chrome manually ? Thank you.

Det commented on 2015-07-14 21:29 (UTC)

Absolutely no need, when you can just do: $ makepkg -si --skipinteg

toppy commented on 2015-07-14 21:29 (UTC)

Edit PKGBUILD and replace md5 checksums with the following ... (generated from 'makepkg -g') md5sums=('b7e752f549b215ac77f284b6486794b6') md5sums_i686=('9a806fa944c59ce398b13c8c79bca123') md5sums_x86_64=('b26558f6be7834d36a58e70348082203') Package builds ok for me

Det commented on 2015-07-14 20:13 (UTC)

@tmoore, 1) I know, this was flagged (see top of PKGBUILD), and 2) see: https://wiki.archlinux.org/index.php/PKGBUILD#Integrity

<deleted-account> commented on 2015-07-14 14:06 (UTC)

Updates to v. 43.0.2357.134

darkxsun commented on 2015-06-22 16:02 (UTC)

Flagging out-of-date is good enough...