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 .. 20 21 22 23 24 25 26 27 28 29 30 .. 32 Next › Last »

grimsbain commented on 2013-10-17 17:28 (UTC)

After having an install error I downloaded the eula and checked the md5sum and it came back a3a49767c80e92cca63b7a33aadfb2af same as Cameri.

ichramm commented on 2013-10-17 16:28 (UTC)

Weird, just updated google-chrome and eula's MD5 is 7ae235c61533ba1108b03d42c49e00bd /cc @Cameri

Cameri commented on 2013-10-17 13:54 (UTC)

The eula changed. New md5sum: a3a49767c80e92cca63b7a33aadfb2af

beststone commented on 2013-10-17 07:40 (UTC)

I have same error. So I temporarily upgraded with "packer" command. $ packer -S --skipinteg google-chrome-beta Later fixed this package, it will upgraded normally.

mariusn commented on 2013-10-17 07:12 (UTC)

eula_text.html ... FAILED

joe1984 commented on 2013-10-16 22:00 (UTC)

I'm getting checksum a3a49767c80e92cca63b7a33aadfb2af for the file eula_text.html. Please fix this PKGBUILD.

MindfulMonk commented on 2013-10-03 11:34 (UTC)

Just change the PKGBUILD line [ "$CARCH" = 'x86_64' ] && md5sums[0]='e4ab342703de87ec117cfea3951acce8' to [ "$CARCH" = 'x86_64' ] && md5sums[0]='7f055de3dc3a62cedb5156420c1bc99a'

thujone commented on 2013-10-02 09:33 (UTC)

On x86_64 I'm getting checksum: 7f055de3dc3a62cedb5156420c1bc99a

haaja commented on 2013-10-01 20:47 (UTC)

Just letting you know that there's an unnecessary .directory file in the tarball.

Det commented on 2013-09-20 18:26 (UTC)

Well, that's a bit longer than the line you already gave me anyway and the output is: <channel> <version> [...] Instead of: <channel>: <version> [...] And to be honest I don't really care about the "feeling" either, as long as it _is_ correct.

ruario commented on 2013-08-11 17:41 (UTC)

@Det: Just a thought, regarding your comment in the PKGBUILD that suggests using the rpm repo meta data to find out the latest version. Since you are now using the deb as the source perhaps this command (or a variant) might be more appropriate as it uses the deb repository metadata? Doesn't really matter given the version number is the same either way but perhaps it feels more correct. $ curl -s https://dl.google.com/linux/chrome/deb/dists/stable/main/binary-amd64/Packages.gz | gzip -d | awk -F "[ -]" '/Package: google-chrome/ { print $4; getline ; print $2 }'

Det commented on 2013-08-09 16:26 (UTC)

Yeah, I've noticed that too back when I made that decision.

zatricky commented on 2013-08-06 15:02 (UTC)

Minor non-bug: I've noticed the end-result is a .tar whereas most packages get packaged as .tar.xz

Det commented on 2013-08-02 15:09 (UTC)

I update it when I can.

lks commented on 2013-08-01 21:54 (UTC)

Save fast and stable browsers exists(See links in core). Google chrome has a nice user interface (and is not so save and sents all your data to google and NSA). Please add/ change your description. lks

workdowg commented on 2013-08-01 20:15 (UTC)

x64 new - md5sum 6d4367302896e62942184997770ddfa2

blackout24 commented on 2013-07-29 15:52 (UTC)

chrome://settings -> Advanced -> [ ] Enable Hardware Acceleration when available. To disable HW acceleration. It seems like it fixed it for me. No more zombie processes and freezes, when using NVIDIA.

oman002 commented on 2013-07-13 23:22 (UTC)

Chrome creates application shortcuts that look like this: /opt/google/chrome/chrome --app=https://mail.google.com/mail/u/0 But they don't work: $ /opt/google/chrome/chrome --app=https://mail.google.com/mail/u/0 /opt/google/chrome/chrome: error while loading shared libraries: libudev.so.0: cannot open shared object file: No such file or directory The following does work: $ /opt/google/chrome/google-chrome --app=https://mail.google.com/mail/u/0 Do I have to manually change my application shortcuts or can this be fixed in the PKGBUILD?

<deleted-account> commented on 2013-07-11 06:39 (UTC)

Yeah its crazy it sometimes literaaly locks my computer up for about 1 minute. It seems the iowait percentage goes up to about 60% and than drops when it stops in resource monitor.

gadget3000 commented on 2013-07-09 14:27 (UTC)

I'm recently switched to using Chromium and I'm also getting weird freezes both on Chromium and Chrome. For me journald starts going mad whenever a freeze happens. I've submitted a bug to Chromium here: https://code.google.com/p/chromium/issues/detail?id=257998

TheWretched commented on 2013-07-08 14:48 (UTC)

I've had that sometimes (the random freezing). Moreso with chrome and it's stagnant processes than with chromium. I've had the occasional weird freeze with chromium too. Honestly chrome / chromium has become a major pain for me with the myriad of problems it seems to have ever since KDE 4.10, mostly because it's still the only decent browser despite all these problems, meaning one has to just live with it.

<deleted-account> commented on 2013-07-08 05:08 (UTC)

Is it just me or does chrome or chromium just randomly lock up your machine for like 4 or 5 seconds randomly...... Not too sure what it maybe but it happens alot ..... It locks up only in chrome for about 5-10 seconds its very annoying ....

Det commented on 2013-07-03 22:41 (UTC)

You can just flag it.

fiveofakind commented on 2013-07-03 17:45 (UTC)

v71 md5sums: 03de683b0e9b8bf77db17060c8113d4d google-chrome-stable_current_amd64.deb 19ec74343b5396760d5d6c88d7282cfb google-chrome-stable_current_i386.deb

mike.cloaked commented on 2013-07-03 17:00 (UTC)

and hot on the heels of v70 now google-chrome-stable-28.0.1500.71-209842 is out!

Det commented on 2013-06-29 16:01 (UTC)

Added, but it'll be faster to just add that yourself. This just moves it to /tmp anyway so it's not a real fix.

JoveYu commented on 2013-06-28 11:22 (UTC)

chrome always create "libpeerconnection.log" in my HOME google say https://code.google.com/p/chromium/issues/detail?id=239048 maybe you can fix it for the moment https://bbs.archlinux.org/viewtopic.php?id=163086

Det commented on 2013-06-26 20:11 (UTC)

Yeah, I really wish our libarchive was built against lrzip: https://bugs.archlinux.org/task/34655 It's hugely faster than anything else and the compression is almost as good as with xz. If it actually became the default in Arch some day it'd be even better. I'm just not sure about the state of its downsides today.

mike.cloaked commented on 2013-06-26 16:29 (UTC)

Thank you for the change to .tar - it does save time to get the install done even if the file is a bit larger than the xz compressed one.

Det commented on 2013-06-26 10:32 (UTC)

Never ever heard of it (the software I mean). I mentioned this to e36freak.

mariusn commented on 2013-06-26 09:37 (UTC)

I'm using cower and meat

Det commented on 2013-06-26 09:36 (UTC)

I changed to PKGEXT='.pkg.tar' to speed up the compression that I'm so tired of waiting to finish. If you want it back you can just remove that line or add the ".xz" to the end. But I'm curious as to how did you guys actually encounter that error. Is it just another one of those AUR tools that don't support .pkg.tar's?

<deleted-account> commented on 2013-06-26 08:24 (UTC)

@Det Seems to work like a charm - thanks ! :-) Besides the zombie processes that is. Even after a full update including nvidia drivers. So stupid ...

<deleted-account> commented on 2013-06-26 08:13 (UTC)

Apparently it's the tar file google-chrome-28.0.1500.52-1-x86_64.pkg.tar. But it used to be a xz file indeed. Just run "pacman -U google-chrome-28.0.1500.52-1-x86_64.pkg.tar". At least, that works for me...

mariusn commented on 2013-06-26 07:40 (UTC)

==> Finished making: google-chrome 28.0.1500.52-1 (Wed Jun 26 10:39:54 EEST 2013) Installing `google-chrome'... error: error: no package file seems to have been created Any ideas?

mike.cloaked commented on 2013-06-24 08:55 (UTC)

In response to the comment on zombie processes by jan_goyvaerts - I also had occurrences of hanging chrome processes in version 27, but after I changed the setting under the advanced settings menu page, by unchecking "Continue running background apps when Google Chrome is closed" I have not had any hanging processes once I did that. However I still have not tried to modify the PKGBUILD file and update to v28 since I was not sure if there was a problem with building the new version on arch since this aur version was still not yet updated for a week.

<deleted-account> commented on 2013-06-22 13:03 (UTC)

The url format has also changed to: "https://dl.google.com/linux/direct/google-chrome-${_channel}_current_${_arch}.rpm"

<deleted-account> commented on 2013-06-22 13:03 (UTC)

The url format has also changed to: "https://dl.google.com/linux/direct/google-chrome-${_channel}_current_${_arch}}.rpm"

<deleted-account> commented on 2013-06-22 13:02 (UTC)

The url format has also changed to: "https://dl.google.com/linux/direct/google-chrome-${_channel}_current}${_arch}}.rpm"

donniezazen commented on 2013-06-20 15:10 (UTC)

@Imaulle https://code.google.com/p/chromium/issues/detail?id=239048

<deleted-account> commented on 2013-06-20 13:37 (UTC)

anyone else getting libpeerconnection.log in home folder now on 28.0.1500.45? that doesn't seem right...

Det commented on 2013-06-19 20:33 (UTC)

Pacman has lots of hacks and it destroys binaries.

<deleted-account> commented on 2013-06-19 20:22 (UTC)

Why are there no zombie processes on other distro's ? Something in Arch has to interfere with Chrome...

<deleted-account> commented on 2013-06-19 17:06 (UTC)

still get zombie processes on 28.0.1500.45-205727 with nvidia driver. back to nouveau driver :(

<deleted-account> commented on 2013-06-19 14:27 (UTC)

The new version is 28.0.1500.45-205727 and the md5 sum for x86_64 is 7d2d46378af0f4a2e10a1ece957bd20a for anyone that wants to manually change the PKGBUILD manually until it gets changed.

ruario commented on 2013-06-18 08:31 (UTC)

@colinkeenan: Because there is a new version (28.0.1500.45-205727). Here is an easy way to find out what the current version is: curl -s https://dl.google.com/linux/direct/google-chrome-stable_current_x86_64.rpm | head -c96 | strings

colinkeenan commented on 2013-06-17 23:17 (UTC)

The download url doesn't work anymore (Monday June 17, 2013) ==> Retrieving sources... -> Downloading google-chrome-stable-27.0.1453.110-202711.x86_64.rpm... % Total % Received % Xferd Average Speed Time Time Time Current Dload Upload Total Spent Left Speed 0 0 0 0 0 0 0 0 --:--:-- --:--:-- --:--:-- 0 curl: (22) The requested URL returned error: 404 Not Found ==> ERROR: Failure while downloading google-chrome-stable-27.0.1453.110-202711.x86_64.rpm Aborting... ==> ERROR: Makepkg was unable to build google-chrome.

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