Package Details: google-chrome-beta 75.0.3770.38-1

Git Clone URL: (read-only)
Package Base: google-chrome-beta
Description: The popular and trusted web browser by Google (Beta Channel)
Upstream URL:
Keywords: chromium
Licenses: custom:chrome
Provides: google-chrome
Submitter: None
Maintainer: luzifer
Last Packager: luzifer
Votes: 343
Popularity: 0.232878
First Submitted: 2009-12-08 19:09
Last Updated: 2019-05-15 20:51

Dependencies (13)

Required by (24)

Sources (3)

Pinned Comments

Det commented on 2016-03-09 05:02

✔ NOTE. If the sha512sums don't match, there's a new version. Simply flag the package.

You can check for new Linux releases in:, or use:

$ curl -sL | gzip -df | tr ' ' '\n' | grep -e name= -e ver= | cut -d '"' -f2 | sed 'N;s/\n/ /'

For new MD5: $ curl -sL | sed -n '16p'

Latest Comments

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

wilberfan commented on 2016-02-10 02:33

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

Det commented on 2015-11-25 06:31

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

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:


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

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

schultzter commented on 2015-11-05 02:57

So it looks like the problem I'm having is a known issue over at the Chromium project.

The problem is some older CPU don't have the LAHF instruction.

schultzter commented on 2015-11-04 20:56

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.


freijon commented on 2015-10-07 16:40

Please modify the following line in the PKGBUILD:

- sed -i "/Exec=/i\StartupWMClass=Google-chrome-$_channel" "$pkgdir"/usr/share/applications/google-chrome-$_channel.desktop

+ sed -i "/Exec=/i\StartupWMClass=google-chrome-$_channel" "$pkgdir"/usr/share/applications/google-chrome-$_channel.desktop

The upper case "G" causes plank to show double icons when Chrome is running

schultzter commented on 2015-09-25 01:12

Yeah, the gdb-chromium.txt file is empty.

I've also tried upgrading to the latest version, same problem though.
Name : google-chrome-beta
Version : 46.0.2490.42-1

I guess I need to figure out how to use gdb...

Det commented on 2015-09-18 22:17

You don't have to reinstall the thing, it doesn't do anything at all. What you're doing with that command is just writing gdb-chromium.txt to the current directory. You could also try GDB or Strace, if gdb-chromium.txt is empty.

schultzter commented on 2015-09-18 22:07

I figured I might as well dance, so I completely deleted those two directories, then re-installed google-chrome-beta - same result.

Then I tried this command to debug, google-chrome-beta --debug 2>&1 | tee gdb-chromium.txt (found on the Ubuntu forums, for Chromium), but nothing happens, Nothing at all!!!