Package Details: google-chrome-beta 132.0.6834.15-1

Git Clone URL: https://aur.archlinux.org/google-chrome-beta.git (read-only, click to copy)
Package Base: google-chrome-beta
Description: The popular web browser by Google (Beta Channel)
Upstream URL: https://www.google.com/chrome
Keywords: chromium
Licenses: custom:chrome
Provides: google-chrome
Submitter: None
Maintainer: gromit
Last Packager: gromit
Votes: 357
Popularity: 1.00
First Submitted: 2009-12-08 19:09 (UTC)
Last Updated: 2024-11-20 23:40 (UTC)

Dependencies (12)

Required by (41)

Sources (3)

Pinned Comments

gromit commented on 2023-11-30 17:09 (UTC)

When reporting this package as outdated make sure there is indeed a new version for Linux Desktop. You can have a look at the "Beta updates" tag in Release blog for this.

You can also run this command to obtain the version string for the latest chrome beta version:

$ curl -sSf https://dl.google.com/linux/chrome/deb/dists/stable/main/binary-amd64/Packages | \
     grep -A1 "Package: google-chrome-beta" | \
     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 .. 11 12 13 14 15 16 17 18 19 20 21 .. 27 Next › Last »

bulletmark commented on 2014-01-24 08:28 (UTC)

@SimFox3, yep I found that also. Only the last couple or so versions.

SimFox3 commented on 2014-01-21 18:37 (UTC)

Does latest google-chrome-beta take a super long time to start for anyone else?

Det commented on 2014-01-16 22:14 (UTC)

Yeah, they did that in the 33.x branch. Synced with Dev again.

<deleted-account> commented on 2014-01-16 22:08 (UTC)

Issue: install: impossível obter estado de “/tmp/yaourt-tmp-mateus/aur-google-chrome-beta/pkg/google-chrome-beta/opt/google/chrome/product_logo_16.png”: Arquivo ou diretório não encontrado Reason: There are now two folders inside /opt/google: chrome and chrome-beta. chrome has mostly symlinks and relevant files are now in chrome-beta Fix: Change every reference in the PKGBUILD of /opt/google/chrome to /opt/google/chrome-beta

Det commented on 2014-01-14 09:42 (UTC)

It means there's a new version. We have the *flag* button for that. And it's much easier to just use "- - skipinteg" when updating on your own (might also wanna bump the pkgver).

yourilima commented on 2014-01-14 08:28 (UTC)

see comment below but instead use the following md5sum da45c1f4e87d2edb3d1c208584af9078

SimFox3 commented on 2014-01-08 06:08 (UTC)

If for the x64 version you're gettin ga "One or more files did not pass validity check": 1. Edit the PKGBUILD 2. Change line 33 md5sum (for x86_64) to: a5ecefed3e037fb91584a5baeaa18eb9

Det commented on 2013-12-26 13:53 (UTC)

For those of you who have [testing] enabled: the new libgcrypt.so.20 (provided by: libgcrypt 1.6.0-1) is incompatible with _all_ versions of Chrome. In order to update to the latest libgcrypt you need to rebuild this package, which will now pull the libgcrypt.so.11.8 from [core] (libgcrypt 1.5.3-1) to the install location (/opt/google/chrome/). Alternatively you can just place the correct libgcrypt.so from the package to either /opt/google/chrome/ or /usr/lib/ and rename it as 'libgcrypt.so.11'.

kicka commented on 2013-12-19 15:20 (UTC)

Thanks CharlesAtum! Your suggestion worked!

<deleted-account> commented on 2013-12-19 13:20 (UTC)

Looks like they moved the desktop file from the opt/google/chrome folder to the usr/share/applications folder. Commenting the following lines should allow compilation and, possibly, solve the problem: msg2 "Moving stuff in place" # Desktop mv "$pkgdir"/opt/google/chrome/google-chrome.desktop "$pkgdir"/usr/share/applications/

« First ‹ Previous 1 .. 11 12 13 14 15 16 17 18 19 20 21 .. 27 Next › Last »