| 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: | 2246 |
| Popularity: | 8.96 |
| First Submitted: | 2010-05-25 20:25 (UTC) |
| Last Updated: | 2024-11-19 19:19 (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.
@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.
@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.
@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.
@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.
@Det Thank you for the interest.
I'll do this tomorrow, anyway I will get back to You and post results.
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).
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.
Oh my god, don't post a comment about it.
Please, update the PKGBUILD, the release to
pkgver=66.0.3359.117
and md5sums to
md5sums=('c979c8fac57b9f78de0b899f1b09ce39' 'd50d8f0a6940791eabc41c4f64e6a3cf' '99fa93d5e7fb5d622cef0f9621f3ffa3')
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:
Do not report updates for ChromeOS, Android or other platforms stable versions as updates here.