Package Details: google-chrome 66.0.3359.117-1

Git Clone URL: https://aur.archlinux.org/google-chrome.git (read-only)
Package Base: google-chrome
Description: The popular and trusted web browser by Google (Stable Channel)
Upstream URL: https://www.google.com/chrome
Keywords: chromium
Licenses: custom:chrome
Submitter: None
Maintainer: Det
Last Packager: Det
Votes: 1694
Popularity: 31.785291
First Submitted: 2010-05-25 20:25
Last Updated: 2018-04-19 17:45

Dependencies (13)

Required by (16)

Sources (3)

Pinned Comments

Det commented on 2017-10-01 00:35

The final vote. “What should be the pkgdesc of AUR/google-chrome?” With 82 votes:

● "One fast, simple, and secure browser for all your devices (Stable Channel)" - 17 votes (21%)
● "The popular and trusted web browser by Google (Stable Channel)" - 65 votes (79%)

Now, my deciding vote of 49 votes will be cast and the winner is...










..no, I’m kidding, I’m kidding. Pkgdesc changed. ^^

Det commented on 2016-03-09 05:01

✔ NOTE If the md5sums don't match, don't post the makepkg output. Simply flag the package.

You can check for new Linux releases in: http://googlechromereleases.blogspot.com/search/label/Stable%20updates, or use: $ curl -s https://dl.google.com/linux/chrome/rpm/stable/x86_64/repodata/other.xml.gz | gzip -df | awk -F\" '/pkgid/{ sub(".*-","",$4); print $4": "$10 }'

Latest Comments

foutrelis commented on 2018-04-19 17:32

@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

@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

@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

@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

@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

@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

@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

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).

Pryka commented on 2018-04-18 18:51

Hello!

Probably since v64 every time I perform chrome update to next major version like 64-->65 or now to 66. Chrome is losing all my sessions and I need to relog to almost every single site I use. Not ground breaking but annoying.

Anyone noticed similar behaviour?

PS. This bug or whatever it is do not occur when update are performed is in the same line, like: 65.0.3325.162 --> 65.0.3325.181.

EDIT: Did a little digging and it's looks that I have lost a whole lot of cookies after update. So this was probably the culprit in the previous ones(updates). Still no idea why this is happening.

Det commented on 2018-04-18 16:39

Oh my god, don't post a comment about it.

All comments