Package Details: google-chrome 135.0.7049.95-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: 2270
Popularity: 8.47
First Submitted: 2010-05-25 20:25 (UTC)
Last Updated: 2025-04-16 07: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 .. 49 50 51 52 53 54 55 56 57 58 59 .. 158 Next › Last »

Det commented on 2018-02-23 18:13 (UTC)

Manjaro? You'll be doing another perfect update in a minute.

Jorre commented on 2018-02-23 16:22 (UTC)

I also ran into the md5 checksum error: ==> Validating source files with md5sums... google-chrome-stable_64.0.3282.167_amd64.deb ... FAILED

I decided to run yaourt with skipping validity checks: yaourt --m-arg "--skipchecksums --skippgpcheck" -Syua

This works fine for me and chrome updated perfectly.

Det commented on 2018-02-06 12:46 (UTC)

+1

I just use pkill.

beoldhin commented on 2018-02-06 09:51 (UTC)

Added a Github page describing the shutdown problems observed with chrome and chromium (includes fix to "Chrome didn't shutdown correctly"): https://github.com/beoldhin/killgroup

rakotomandimby commented on 2018-02-05 19:05 (UTC)

You're right, the synchronization screws it all. If I dont sync, it restarts all right. If I ever sign in, it syncs then I cant relaunch it unless I remove config.

Workaround it to stay signed out for the moment. But that's weird.

I'll configure synchronization one by one and tell.

Det commented on 2018-02-05 18:59 (UTC)

Probably you're not closing it right. Or it happens after syncing extensions, etc.

I'd go step by step.

rakotomandimby commented on 2018-02-05 18:44 (UTC)

But it only works 1 launch after the remove of the directory: if I close Chrome and relaunch again, it fails.

rakotomandimby commented on 2018-02-05 18:41 (UTC)

"rm -rf ~/.config/google-chrome ; rm -rf ~/.cache/google-chrome" made it works for me...

Det commented on 2018-02-03 13:21 (UTC) (edited on 2018-02-03 13:22 (UTC) by Det)

What else is there besides the sums?

MarcinWieczorek commented on 2018-02-03 09:40 (UTC)

Please retire md5 and switch to sha256 at least for checksums :)

« First ‹ Previous 1 .. 49 50 51 52 53 54 55 56 57 58 59 .. 158 Next › Last »