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: 2258
Popularity: 8.52
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 .. 91 92 93 94 95 96 97 98 99 100 101 .. 157 Next › Last »

Det commented on 2014-12-09 19:34 (UTC)

The servers still offer .71 for Linux: http://googlechromereleases.blogspot.com/2014/12/stable-channel-update.html

Det commented on 2014-11-28 17:45 (UTC)

Yes, it works on a fresh install. About the wrong source, you're probably using a poor AUR tool, or the system really is 64-bit: $ uname -m $ grep CARCH /etc/makepkg.conf

Av4t4r commented on 2014-11-28 17:40 (UTC)

I just did a fresh install with no permission issues. However, I did it on a 32bit system and I had to edit the PKGBUILD because it would otherwise only fetch the 64 bit package. I edited _arch=i386 and updated the MD5 to md5sums=('cc7c7cfcbd9982307b25989814739486' 'b7e752f549b215ac77f284b6486794b6') Thanks for the package tho, hopefully this will get fixed soon.

Det commented on 2014-11-27 13:33 (UTC)

No, that's not the issue at all, aren't you getting the permission message after the upgrade? E.g.: [...] (1/1) upgrading google-chrome [#####################] 100% warning: directory permissions differ on /usr/share/doc/google-chrome-stable/ filesystem: 700 package: 755 It means the existing permissions can't be changed without a manual intervention or a reinstall (uninstall/install).

nullptr_t commented on 2014-11-27 13:01 (UTC)

I know, you are fixing the permissions of the doc directory in PKGBUILD with msg2 "Fixing permissions of documentation folder" chmod 755 "$pkgdir"/usr/share/doc/google-chrome-$_channel/ but as of 39.0.2171.71-1 the problem still remains the same: # ll -d /usr/share/doc/google-chrome-stable/ drwx------ 2 root root 4.0K Nov 27 13:46 /usr/share/doc/google-chrome-stable/ Don't know, what's the problem with "google-chrome-$_channel/", but maybe "$_channel" or ${_channel} (like in the sources-line) would help to clarify it as substring

jazztickets commented on 2014-11-26 03:19 (UTC)

google-chrome-stable_39.0.2171.65_amd64.deb ... FAILED ERROR: One or more files did not pass the validity check!

rafaelff commented on 2014-11-13 18:10 (UTC)

I'm getting http error 404 on downloading the sources tarball.

Det commented on 2014-11-03 18:43 (UTC)

Apparently a pretty old bug. Couldn't reproduce with Beta or Dev channels: https://code.google.com/p/chromium/issues/detail?id=354571

CarstenG commented on 2014-11-03 18:28 (UTC)

Please update the permissions of the doc directory, because unprivileged users can't access the content. # ll -d /usr/share/doc/google-chrome-stable drwx------ 2 root root 25 31. Okt 17:42 /usr/share/doc/google-chrome-stable Thanks, Carsten

« First ‹ Previous 1 .. 91 92 93 94 95 96 97 98 99 100 101 .. 157 Next › Last »