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: 11.94
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 .. 15 16 17 18 19 20 21 22 23 24 25 .. 32 Next › Last »

LarcBP commented on 2015-01-27 12:06 (UTC)

to solve this last problem, change the line on PKGBUILD: md5sums_x86_64=('0bd66eeac16d62778ad7cb33d608eb68') to md5sums_x86_64=('ac0e961f5001a38c087942570ac65178')

catalin.hritcu commented on 2015-01-27 09:20 (UTC)

I can confirm bmbaker's problem. I get a similar problem with aura: ==> Validating source files with md5sums... google-chrome-stable_40.0.2214.91_amd64.deb ... FAILED

bmbaker commented on 2015-01-27 08:44 (UTC)

there seems to be a problem with PKBUILD Validating source files with md5sums... google-chrome-stable_40.0.2214.91_amd64.deb ... FAILED ==> ERROR: One or more files did not pass the validity check! ==> ERROR: Makepkg was unable to build google-chrome.

Det commented on 2015-01-16 09:29 (UTC)

Pacman 4.2.0 is apparently in [testing] for Manjaro: http://mirror.premi.st/manjaro/testing/core/x86_64/ You can get the previous (4.1.x compatible) PKGBUILD in: http://pkgbuild.com/git/aur-mirror.git/tree/google-chrome/PKGBUILD?id=670b3f5f6cc45f9a28652316ba17d02b60023cf3

annhill commented on 2015-01-16 09:24 (UTC)

If I build this in Manjaro (0.8.11), I get the following error: error: target not found: pacman>= 4.2.0 My version of pacman is 4.1.2, how can I fix this?

nogweii commented on 2015-01-13 21:13 (UTC)

the stable channel was updated to 39.0.2171.99. Here are the md5sums: md5sums=('037cef95bea64ffa87e926af59ae117b' 'b7e752f549b215ac77f284b6486794b6')

derrickcope commented on 2015-01-07 04:41 (UTC)

since the last upgrade it keeps freezing up on me. Mainly when I turn on/off the vpn. never happened before.

feighur commented on 2014-12-23 01:39 (UTC)

Even with ttf-dejavu and ttf-liberation installed, I had Chinese characters show up as boxes. Tested on http://zh.wikipedia.org. I had to install ttf-droid to get them to display properly. Perhaps another optional dependency?

rafaelff commented on 2014-12-10 15:18 (UTC)

@grayich: This is related to your configuration in /etc/yaourtrc (or maybe in /etc/makepkg.conf), where you set to store built packages in /var/cache/pacman/pkg/ Set another folder where you can store without needing root permissions, or always provide password. Anyway, this issue is not related to this package, so further issues, ask for help in Arch Linux forums.

Det commented on 2014-12-10 11:50 (UTC)

Nothing at all to do with this package.

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

cyrilccros commented on 2014-10-27 21:39 (UTC)

Hi, I just ran the usual pacman -Syu today and all my troubles went away. I still had the bug this morning, though. Anyway, thanks for your help.

cyrilccros commented on 2014-10-27 09:02 (UTC)

Sorry for the delay in my answer. I have spent some time googling my issues, but google's error messages are of little use. I see several different causes for the same message... See below for a full error example: [cyril@synapse ~]$ google-chrome-stable ATTENTION: default value of option force_s3tc_enable overridden by environment. [17667:17735:1027/095325:ERROR:get_updates_processor.cc(240)] PostClientToServerMessage() failed during GetUpdates [17667:17701:1027/095329:ERROR:channel.cc(316)] RawChannel read error (connection broken) Bus error (core dumped) What I do remember is that my computer crashed very shortly before my troubles began. I use Openbox + Slim as login manager, and slim failed to launch openbox repeatedly. I just used the console to log in and correct slim.conf, which solved my issues.

drak3 commented on 2014-10-25 18:41 (UTC)

I, too, am having issues with Chrome 38 crashing frequently. It doesn't do it for every page, but it does it frequently, even after disabling all my extensions, re-installing, and making a new profile. after a few minutes, it will also lock up the system, requiring a hard reboot. also, as with cyrilccros, firefox seems to be fine. one thing I've noticed that will definitely trigger the tab crash is playing video in multi-monitor fullscreen.

Det commented on 2014-10-22 22:59 (UTC)

Did you try https://www.google.com/search?q=ERROR%3Aget_updates_processor.cc+PostClientToServerMessage first?

cyrilccros commented on 2014-10-22 22:56 (UTC)

Hi, google-chrome crashes whenever I load a page. This happens with chromium too, but Firefox is fine. I get an error in ...:ERROR:get_updates_processor.cc(240)] PostClientToServerMessage() failed during GetUpdates Bus error (core dumped) Chrome also crashes shortly after start up, and I often get "Aw snap" error windows. I tried launching it with no plugins or gpu support. I use Bumblebee (Intel and Nvidia laptop). Thanks for your help, I will post a bug report if anyone confirms. Version: google-chrome=38.0.2125.104 (l test)

Det commented on 2014-10-20 13:31 (UTC)

It's now an optional dependency.

catalin.hritcu commented on 2014-10-18 13:27 (UTC)

Chrome doesn't display many PDFs correctly without ttf-liberation (https://code.google.com/p/chromium/issues/detail?id=369991). Shouldn't that be a package dependency?

Det commented on 2014-10-16 11:16 (UTC)

Please Google first: https://www.google.com/search?q=NVIDIA%3A+could+not+open+the+device+file+%2Fdev%2Fnvidia0+Operation+not+permitted (E.g. the very first results).

zlopi commented on 2014-10-16 08:40 (UTC)

NVIDIA: could not open the device file /dev/nvidia0 (Operation not permitted). NVIDIA: could not open the device file /dev/nvidia0 (Operation not permitted). how to fix it?

abhixec commented on 2014-10-15 04:09 (UTC)

Updated PKGBUILD : https://gist.github.com/binarysage/8888d6492f9a194b9541

yodalee commented on 2014-10-15 02:43 (UTC)

The hash of google-chrome.deb should be a2b61a623da973f12e1cb18674b9fb93 now

lviggiani commented on 2014-10-08 07:32 (UTC)

Every time I get an update of the package, Google complains that cannot load my profile. Even by re loggin in does not solve the isssue. I have to delete ~/.config/google-chrome folder and re do the access to all my profiles. This is happening since the last three or four updates...

Det commented on 2014-10-01 05:32 (UTC)

Same as with all the other OS's: https://code.google.com/p/chromium/wiki/ChromiumBrowserVsGoogleChrome

Barry commented on 2014-10-01 03:07 (UTC)

What's the difference between chrome and chromium on Arch?

Det commented on 2014-09-25 11:42 (UTC)

@corvinusz: "The stable channel has been updated to 37.0.2062.124 for _Windows_ and _Mac_." - http://googlechromereleases.blogspot.com/2014/09/stable-channel-update_24.html

capoeira commented on 2014-09-21 13:02 (UTC)

Oh I see. now I just need to convince my bank to stop using it lol

Det commented on 2014-09-21 12:43 (UTC)

No it's not blocked, the whole support for the plugin API is gone.

capoeira commented on 2014-09-21 11:29 (UTC)

i understand that Java is blocked...the thing is, it's not even in chrome://plugins/

Det commented on 2014-09-20 20:09 (UTC)

It (NPAPI support) has been gone from Linux builds since v35: http://blog.chromium.org/2013/09/saying-goodbye-to-our-old-friend-npapi.html

capoeira commented on 2014-09-20 20:00 (UTC)

for the last 2 builds java doesn't apear anymore in about:plugins.......anyone?

cleanrock commented on 2014-09-12 12:43 (UTC)

PKGBUILD is broken for i686: PKGBUILD: line 28: md5sums[0]: cannot assign list to array member Just remove the (), line should be like this: [[ "$CARCH" = 'i686' ]] && md5sums[0]='fc4fd42aa00222a7df9ad89417f8d219'

x7.0 commented on 2014-09-12 01:46 (UTC)

"an error in package()" may be caused by SSL certificate error in line 44-45 in PKGBUILD, commenting out would help. I wonder if it is possible to put the license out of `package()`, because in China we cannot connect to Google directly without any proxy.

Det commented on 2014-09-11 14:40 (UTC)

I really am unable to help with that.

passchaos commented on 2014-09-11 08:17 (UTC)

Help!!When I build chrome, I get "an error in package()"

phoenixlzx commented on 2014-09-11 02:48 (UTC)

Hi, Why the PKGBUILD says its `37.0.2062.120-1` but title shows `37.0.2062.94-1`? BTW version `37.0.2062.120-1` md5sum: x86_64: ad13b2cd986933a57cf348dc0efc50cf i686: fc4fd42aa00222a7df9ad89417f8d219

Det commented on 2014-09-06 22:07 (UTC)

No problem bringing it up. I didn't even know it was a Chromium bug, but usually these aren't Chrome-specific. Otherwise these bugs would be closed anyway, because that's code we don't get to see. p.s. I appreciate you liking my writing. I like it as well.

<deleted-account> commented on 2014-09-06 03:34 (UTC)

@Det I really like the way you reply to people on the packages you maintain (no sarcasm, I really do like it). Anyway, by "anyone here" I meant someone running Arch and using this package (or maybe chromium). I got this bug initially when M37 was on Dev and it still wasn't fixed, so I just wanted to point to the bug report in case someone got Chrome hanging for "no apparent reason" or for the somewhat easily, and almost certainly annoyingly, visible tooltip. The stack trace on comment #10 is probably enough to fix, but if anyone else gets any useful information it might be helpful to comment there. Or star it if you just want to get updates.

Det commented on 2014-09-05 23:32 (UTC)

Yeah. It was confirmed on Fedora also in your report. Also using Gnome Shell.

« First ‹ Previous 1 .. 15 16 17 18 19 20 21 22 23 24 25 .. 32 Next › Last »