Package Details: google-chrome 137.0.7151.68-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: 2281
Popularity: 11.82
First Submitted: 2010-05-25 20:25 (UTC)
Last Updated: 2025-06-03 13:24 (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 .. 51 52 53 54 55 56 57 58 59 60 61 .. 159 Next › Last »

beoldhin commented on 2018-01-17 08:51 (UTC) (edited on 2018-01-18 21:25 (UTC) by beoldhin)

I get the message "Chrome didn't shutdown correctly" always when I start Chrome after restarting the computer. I found out that Chrome leaves some processes running even after the browser is closed. Closing these processes with "killall chrome" before restart fixes this problem. The default signal sent by killall is "sigterm" but systemd probably sends something "faster" to the processes during shutdown, leaving them in unclean state.

Update: grepping chrome process tree root process with "pgrep -o chrome" and then killing that process + waiting for the directory to disappear from proc works better than "killall" that sometimes works, sometimes doesn't.

zerophase: "Is anyone else having issues with Chrome refusing to launch lately?". Yes. I just moved from chromium to chrome in one system with Cinnamon and other with Gnome 3. Launching chrome in Cinnamon doesn't work (hangs forever) but in Gnome 3 it does so there does seem to be that almost required dependency to gnome-keyring.

zerophase commented on 2018-01-12 06:32 (UTC) (edited on 2018-01-12 07:03 (UTC) by zerophase)

Is anyone else having issues with Chrome refusing to launch lately?

Just getting this error:

Gkr-Message: secret service operation failed: The name org.freedesktop.secrets was not provided by any .service files

EDIT: Well, I just had to install gnome-keyring. Have no idea what changed requiring that for Chrome to run.

xgdgsc commented on 2017-12-26 05:02 (UTC)

I also see severe memory usage issue in recent versions. I open hundreds of tabs and use tab suspender. It used to work with only less than 2GB, now I have to restart it once every day to free 6GB of memory or it will take all of swap.

angelv commented on 2017-12-20 21:26 (UTC) (edited on 2017-12-20 22:05 (UTC) by angelv)

I see. Didn't realize about the previous high memory comment. I guess it is probably the same thing. I don't know, since I was not monitoring memory usage and the computer became truly unusable even after waiting for a few minutes, so I couldn't even change to a terminal. I will check today and see if the memory is also the issue in my case.

After doing some tests, my issue seems different. Memory usage was a total of about 1.7GB (in a system with 8GB) with 8 tabs open. I tried to resize the Chrome window and suddenly the whole thing froze....

Det commented on 2017-12-20 21:09 (UTC) (edited on 2017-12-20 21:09 (UTC) by Det)

As in like as per the previous comments?

angelv commented on 2017-12-20 21:08 (UTC)

Anybody experiencing troubles with the latest google-chrome-stable? I updated the system during this week, and now I cannot use chrome properly: it works OK for some time, but at some point the computer freezes (I can move the mouse) but cannot click on anything and the keyboard is also unresponsive and I have to hard boot. I'm not completely sure chrome is responsible, but it has always happened (at least 5-6 times in a few hours) when I was using it and none when I have switched to Firefox.

Det commented on 2017-12-13 16:12 (UTC) (edited on 2017-12-13 16:12 (UTC) by Det)

Previous one: https://dl.google.com/linux/deb/pool/main/g/google-chrome-stable/google-chrome-stable_62.0.3202.94-1_amd64.deb

Also see /var/cache/pacman/pkg/ (it's good to move AUR packages there also).

pazof commented on 2017-12-13 16:08 (UTC)

Also need to report the memory issue with 63.0.3239.84-1 - it now eats up at least 3 times the memory it used to - running it on a 16GB RAM system, the computer can hardly operate without lagging after opening the 5th Chrome tab or so.

DeadMetaler commented on 2017-12-09 09:53 (UTC)

google-chrome 63.0.3239.84-1 has memory leak for me. After some time it eats 4GB of memory, when normal for my situation is 1GB.

Det commented on 2017-11-25 01:29 (UTC)

https://github.com/ContinuumIO/anaconda-issues/issues/368#issuecomment-214506450 ?

« First ‹ Previous 1 .. 51 52 53 54 55 56 57 58 59 60 61 .. 159 Next › Last »