Package Details: google-chrome-beta 124.0.6367.49-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: 354
Popularity: 0.30
First Submitted: 2009-12-08 19:09 (UTC)
Last Updated: 2024-04-12 23:23 (UTC)

Dependencies (12)

Required by (37)

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 2 3 4 5 6 7 8 9 10 11 .. 27 Next › Last »

Det commented on 2016-02-10 06:48 (UTC)

And the source_i686 / md5sums_i686.

brycec commented on 2016-02-10 06:47 (UTC)

@Det Oh, good point. I didn't even think to check both files... Sorry for my noise. Guess the PKGBUILD needs to have i686 removed from its `arch=` line then, eh?

Det commented on 2016-02-10 06:42 (UTC)

Thanks, but he probably means the 32-bit build, which apparently was dropped (as you would see in the upstream download section as well): http://linux.slashdot.org/story/15/12/01/1524259/google-to-drop-chrome-support-for-32-bit-linux

brycec commented on 2016-02-10 04:13 (UTC)

@wilberfan Just tested with yaourt, makepkg, and wget'ing the URL itself: all work for me. wget https://dl.google.com/linux/direct/google-chrome-beta_current_amd64.deb --2016-02-09 20:12:05-- https://dl.google.com/linux/direct/google-chrome-beta_current_amd64.deb Resolving dl.google.com (dl.google.com)... 2607:f8b0:400a:800::200e, 216.58.193.78 Connecting to dl.google.com (dl.google.com)|2607:f8b0:400a:800::200e|:443... connected. HTTP request sent, awaiting response... 200 OK Length: 48486470 (46M) [application/x-debian-package] Saving to: ‘google-chrome-beta_current_amd64.deb’ google-chrome-beta_current_am 100%[===================================================>] 46.24M 7.76MB/s in 5.8s 2016-02-09 20:12:11 (7.93 MB/s) - ‘google-chrome-beta_current_amd64.deb’ saved [48486470/48486470]

wilberfan commented on 2016-02-10 02:33 (UTC)

I've been getting a consistent "404" error ("not found") when I try to update.

Det commented on 2015-11-25 06:31 (UTC)

You can also use 'SKIP' or "makepkg --skipinteg (-si)" or just wait for me to update it.

Retro_Gamer commented on 2015-11-25 05:47 (UTC)

After it failed for me using yaourt I left it at the build failed want to Restart Y/N question. Opened /tmp/yaourt-tmp-retro/aur-google-chrome-beta/ directory. I ran md5sum google-chrome-beta_47.0.2526.69_amd64.deb to get the correct md5sum of 52a999c38b1f1622f9db4c6e280cd549. Opened the PKGBUILD and changed line 30 to read: md5sums_x86_64=('52a999c38b1f1622f9db4c6e280cd549') Went back to still open terminal running yaourt and typed Y to redo and it finished as it should.

bendavis78 commented on 2015-11-20 21:56 (UTC)

The MD5SUM for the .deb file needs to be updated. I'm showing 39e1c95f411b3371e5368658dde42556

schultzter commented on 2015-11-05 02:57 (UTC)

So it looks like the problem I'm having is a known issue over at the Chromium project. https://code.google.com/p/chromium/issues/detail?id=525751 The problem is some older CPU don't have the LAHF instruction.

schultzter commented on 2015-11-04 20:56 (UTC)

Unfortuately I'm still having the "Illegal instruction (core dumped)" issue with google-chrome-beta, but now it's happening with -stable too. I guess whatever changes Google made to -beta at the time have made their way into -stable now. Anyone have any tips to help me debug this? Or at least help focus on what the problem could be? I've tried running with the --debug flag but I don't get any more output; and I can't find the core file any where so I have no idea what's dumped. Thanks,

« First ‹ Previous 1 2 3 4 5 6 7 8 9 10 11 .. 27 Next › Last »