Package Details: google-chrome 137.0.7151.55-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: 12.07
First Submitted: 2010-05-25 20:25 (UTC)
Last Updated: 2025-05-27 18:02 (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 .. 47 48 49 50 51 52 53 54 55 56 57 .. 159 Next › Last »

huiser commented on 2018-04-28 16:01 (UTC)

AUR Packages (1) google-chrome-66.0.3359.139-1

:: Proceed with installation? [Y/n] y :: Retrieving package(s)... :: Checking google-chrome integrity... ==> ERROR: PKGBUILD contains CRLF characters and cannot be sourced.

==> ERROR: An unknown error has occurred. Exiting... :: failed to verify google-chrome integrity

ohmysql commented on 2018-04-27 20:08 (UTC)

I get this message in build. I googled and couldn't see if it was bad :

==> Verifying database signature... ==> WARNING: No existing signature found, skipping verification. ==> Extracting database to a temporary location... ==> Verifying database signature... ==> WARNING: No existing signature found, skipping verification. ==> Extracting database to a temporary location... ==> Adding package 'google-chrome-66.0.3359.139-1-x86_64.pkg.tar.xz' -> Computing checksums... -> Removing existing entry 'google-chrome-66.0.3359.117-1'... -> Creating 'desc' db entry... -> Creating 'files' db entry...

foutrelis commented on 2018-04-19 17:32 (UTC)

@Pryka: Probably the same thing that happened to me: Chrome lost the random password it stores in the keyring as "Chrome Safe Storage", which it uses to encrypt cookies. After that is lost, any new cookies created don't overwrite their old counterparts and thus we end up with duplicate cookies.

The cookie handling behavior has changed in Chrome 66 and duplicate cookies should no longer be created (it was a rare issue in the first place). There might still be some problematic behavior though, as I noted in the upstream bug. It's also still the case that losing "Chrome Safe Storage" will make all cookies encrypted with it unreadable.

Pryka commented on 2018-04-19 16:58 (UTC)

@foutrelis Yeah, bunch of dupes.

But I don't understand now... Why creating a new profile fixed that on my machine? I jumped back and fort from 64 to 66 just to check it. And I'm not losing anything now. Chrome stays log in on sites an google account after each update.

foutrelis commented on 2018-04-19 16:48 (UTC)

@Pryka: If you have a backup of your Chrome 65 profile, you can run this query on its Cookies database: https://crbug.com/800414#c26

If it returns anything other than 0, then duplicate cookies was the reason you lost your cookies after upgrading to Chrome 66.

Pryka commented on 2018-04-19 16:45 (UTC) (edited on 2018-04-19 16:45 (UTC) by Pryka)

@foutrelis

Could be. But it seams to work normal after creating clean profile files. At least for now. Have to wait for the v67 to be sure.

foutrelis commented on 2018-04-19 16:37 (UTC)

@Pryke: Cookie loss after upgrading to M66 can be due to https://crbug.com/800414#c37

@Det: You can remove gconf from the dependencies. It's not been needed since Chrome 65 I believe.

Pryka commented on 2018-04-19 16:26 (UTC)

@Det:

Couldn't reproduce it in Chromium 65 and 66.

Apparently it was some kind of corruption of my Google-Chrome profile. Created new one. Downgraded/Updated(65<-->66) and everything is working fine now(with sync on and off). Thank You.

Pryka commented on 2018-04-18 19:51 (UTC) (edited on 2018-04-18 19:52 (UTC) by Pryka)

@Det Thank you for the interest.

I'll do this tomorrow, anyway I will get back to You and post results.

Det commented on 2018-04-18 19:37 (UTC)

It'd be interesting, if you could test this with Chromium also: https://archive.archlinux.org/packages/c/chromium/

And if can't reproduce, then with clean profile on Chrome (non-synced) (see /var/cache/pacman/pkg or e.g. https://dl.google.com/linux/deb/pool/main/g/google-chrome-stable/google-chrome-stable_65.0.3325.181-1_amd64.deb).

« First ‹ Previous 1 .. 47 48 49 50 51 52 53 54 55 56 57 .. 159 Next › Last »