Package Details: google-chrome 136.0.7103.113-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: 2277
Popularity: 12.19
First Submitted: 2010-05-25 20:25 (UTC)
Last Updated: 2025-05-14 19:12 (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 .. 19 20 21 22 23 24 25 26 27 28 29 .. 32 Next › Last »

w1ntermute commented on 2014-01-14 20:13 (UTC)

I agree with the other commenters, you really should have incremented pkgrel. That's the reason why pkgrel exists, like Scimmia said. OK, you made a mistake at first, but there's no reason to keep digging a deeper hole for yourself - just admit that you made a mistake and don't let it happen again.

nDray commented on 2014-01-14 20:07 (UTC)

And if you must know, pkgrel should have been incremented

nDray commented on 2014-01-14 20:07 (UTC)

New version is out, just put people out of their misery with the update.

Scimmia commented on 2014-01-14 17:44 (UTC)

The real problem is that you didn't bump the pkgrel when you fixed the package in the first place. If the final binary package changes, you're supposed to bump the pkgrel. You failed.

big_bum commented on 2014-01-14 17:06 (UTC)

It will really be easier for all of us to simply increase the pgkrel. You are not rebuilding anything, you just have to edit one file...

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

Unfortunately there's no such pkgrel that only affects those who have a "broken" system. When something that breaks things moves from [testing] to [core]/[extra] I'm against every single step of raising the pkgrel on any package that's not small as hell. It would have to be something seriously major and AUR rarely counts as such. That's life, that's Arch. If you don't have those libraries yet, then rebuild it or manually put them there. Those who do don't care.

Scimmia commented on 2014-01-14 16:39 (UTC)

nagging? It's required to rebuild it with the new libgcrypt, not nagging to help keep a working system.

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

Not really. I did that change a long time ago and don't care about nagging anybody to rebuild it.

ushi commented on 2014-01-14 12:44 (UTC)

you could increase the pkgrel number. this is exactly the use case.

Det commented on 2014-01-13 21:37 (UTC)

Roughly, no, because for one, I would not bump the _version_ number to do that (which is '31.0.1650.63'), it would be the _release_ number (that is, '1') and two, the new libgcrypt 1.6.0-1 is the reason Google Chrome/Chromium/SRWare Iron do not work without the previous libraries being put in place (which is what I'm currently doing for you). Chrome is a binary package. I can't just go forward with my ambitious plans to rebuild it for a newer library that has been pulled in on another distribution, totally different fromt the ones they support. To sum up: - Chrome is built for libgcrypt 1.5.x - We use libgcrypt 1.6.x - They do NOT work together - Only Google can fix this - We (I) use the 1.5.x libraries in these packages to make Chrome working again - Big smile

RubenKelevra commented on 2014-01-13 21:25 (UTC)

could you please just increase the version-number while adding a depency to the new version libgcrypt-1.6.0-1? That would fix it for everybody. :)

franziskus commented on 2014-01-13 21:03 (UTC)

@jz_train just reinstall the package, also gets you libgcrypt.so.11. for a proper fix you have to wait for chromium/google to fix this

Det commented on 2014-01-13 20:16 (UTC)

And it's not out-of-date because of it..

Det commented on 2014-01-13 20:16 (UTC)

Or if you rebuild this thing.

jz_train commented on 2014-01-13 20:16 (UTC)

error while loading shared libraries: libgcrypt.so.11: cannot open shared object file: No such file or directory libccrypt was updated today 12-16-14 to version libgcrypt-1.6.0-1-x86_64.pkg.tar.xz. If you downgrade to libgcrypt-1.5.3-1-x86_64.pkg.tar.xz chrome will run.

Det commented on 2014-01-09 19:45 (UTC)

Well, since I'm not the official bug tracker of Chromium, there's not much I can do. You should try the Arch forums or the actual bug tracker.

JoveYu commented on 2014-01-09 07:32 (UTC)

Hi, Det, remember my bug? I found my chrome render textinput without css to a input with 0px width, maybe this is the reason. i write <input type="text"> to a html file, and it display not really well!

Det commented on 2014-01-01 00:33 (UTC)

Even, if you redownload it? As in not using the one already in $startdir.

a1russell commented on 2013-12-30 07:44 (UTC)

eula_txt checksum is for me: 6d57da7476a4b1b7a81821d9c036425c

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

Fixed. The package will now pull the previous libgcrypt.so(.11.8) from [core] (libgcrypt 1.5.3-1) and place it in /opt/google/chrome/. I decided to make this happen even, if libgcrypt 1.6.0-1 isn't currently installed on the system to allow the previous version to be installed _before_ upgrading to the new one.

Det commented on 2013-12-26 11:19 (UTC)

Oh.

hadrons123 commented on 2013-12-26 11:17 (UTC)

gentoo has some fix for this post libgcrypt 1.6 update.

Det commented on 2013-12-26 11:16 (UTC)

Then how did you get in here? Liar.

hadrons123 commented on 2013-12-26 11:16 (UTC)

Doesn't start after new libgcrypt 1.6 update.

JoveYu commented on 2013-12-15 04:08 (UTC)

yeah nothing changed! same as chromium! version number is 31.0.1650.63 and my DE is cinnamon, everything is up-to-date!

Det commented on 2013-12-14 16:54 (UTC)

You sure? Cleared/renamed both ~/.cache/google-chrome/ and ~/.config/google-chrome/? The system itself is up-to-date? What's the version number in the "About" page?

JoveYu commented on 2013-12-14 08:00 (UTC)

I have tried, but nothing changed!

Det commented on 2013-12-13 08:56 (UTC)

Have you tried with a clean profile? Are you sure it's this channel and the thing is up-to-date?

JoveYu commented on 2013-12-12 01:19 (UTC)

why chrome render pages like this http://imgur.com/6WLs5R9 is it chrome's bug? or my computer's?

reed1 commented on 2013-12-11 04:41 (UTC)

@nhasian, not really for those who faces strange icon grouping issue with kde task manager, go here: http://forums.opensuse.org/english/get-technical-help-here/applications/492582-google-chrome-kde-quick-launcher-issue.html

Det commented on 2013-12-07 22:31 (UTC)

You.

tioammar commented on 2013-12-06 15:58 (UTC)

I got this error message.. ./opt/google/chrome/PepperFlash/libpepflashplayer.so: Lzma library error: Corrupted input data. Is that the problem with the pkg or my system?

nhasian commented on 2013-12-06 04:53 (UTC)

@reed1 I imagine some links were broken due to the name of the application changing from google-chrome to google-chrome-stable.

tarkin88 commented on 2013-12-04 20:04 (UTC)

Here a PKGBUILD, works for me http://pastebin.com/hJm8zX0Q Just change the source chrome link and md5sum

na12 commented on 2013-12-04 15:20 (UTC)

I get "[1204/160811:ERROR:nacl_helper_linux.cc(233)] NaCl helper process running without a sandbox! Most likely you need to configure your SUID sandbox correctly" error and chrome then crash.

a1russell commented on 2013-12-04 01:36 (UTC)

eula_text checksum is failing.

reed1 commented on 2013-12-03 09:35 (UTC)

Anyone notice the shorcut isn't working anymore on KDE's task manager ? http://i.imgur.com/sXd2Rac.png

magicalChicken commented on 2013-11-25 18:08 (UTC)

Could you please add libxtst to the dependencies, chrome crashes without it.

Det commented on 2013-11-25 08:44 (UTC)

Did you also notice the first comment from top?

mumbel commented on 2013-11-25 04:09 (UTC)

Does "google-chrome" exist in PATH currently? Right now I only have "google-chrome-stable" or is my PATH not including everything it should? Just noticed this when trying to set default browser.

Det commented on 2013-11-17 17:24 (UTC)

Just came here to say that now that the "Google Chrome Introduction Book" (http://www.google.com/googlebooks/chrome/) is becoming increasingly outdated the official Chromium blog is still here to keep you pretty damn interested in what they're doing to their project and the modern internet as a whole: http://blog.chromium.org/. I've also updated the Stable and Beta channel packages' .install files to also notify about the newly added -stable/-beta suffixes in the /usr/bin/ symlinks.

Commander commented on 2013-11-14 22:43 (UTC)

New version out: http://googlechromereleases.blogspot.se/ 31.0.1650.57

dmoebius commented on 2013-11-14 09:36 (UTC)

eula changed again. The new md5 sum is '6d57da7476a4b1b7a81821d9c036425c'.

ruario commented on 2013-10-23 08:19 (UTC)

@SysGhost: You have misunderstood. The checksum is not wrong for 30.0.1599.101. The reason it doesn't match the download is that the current stable Chrome is now 30.0.1599.114 (notice the higher stabilization branch number '114'). The problem is simply that the PKGBUILD is out of date, resulting in the version number and both the 32 and 64 bit checksums no longer matching. P.S. Read the PKGBUILD comments to understand how to check what the current version number is.

SysGhost commented on 2013-10-23 08:07 (UTC)

This PKGBUILD includes a 64 bit version of google-chrome too (Should be included in the "sources" section of this page) However, the md5sum in the PKGBUILD for the amd64 version "google-chrome-stable_30.0.1599.101_amd64.deb" is not correct. The correct md5sum should be: 7ff0eed996de3015683e0159b87d4d6e Replace the line that reads: [ "$CARCH" = 'x86_64' ] && md5sums[0]='9abdef7ee0422f7dabb16941453551cc' ...with: [ "$CARCH" = 'x86_64' ] && md5sums[0]='7ff0eed996de3015683e0159b87d4d6e'

Det commented on 2013-10-18 19:25 (UTC)

+1 yeah :D. If nothing else, glad to see new users acquainting themselves with PKGBUILDs.

petko10 commented on 2013-10-17 21:33 (UTC)

+1 for the a3a49767c80e92cca63b7a33aadfb2af for eula . I put that hash as the second md5sum (above the line [ "$CARCH" = 'x86_64' ] && md5sums[0]='e4ab342703de87ec117cfea3951acce8' ) , and the package installed normally.

« First ‹ Previous 1 .. 19 20 21 22 23 24 25 26 27 28 29 .. 32 Next › Last »