New issue
Advanced search Search tips

Issue 632993 link

Starred by 4 users

Issue metadata

Status: Archived
Owner: ----
Closed: Jul 2017
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux
Pri: 2
Type: Bug



Sign in to add a comment

cookies are gone due to eg. [*.]google.com getting transformed into http://google.com:80 after restart

Reported by icanreal...@gmail.com, Jul 31 2016

Issue description

UserAgent: Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/54.0.2814.0 Safari/537.36

Steps to reproduce the problem:
1. use 54.0.2804.0_r923.5f2924f-1
login to gmail and twitter while having [*.]twitter.com and [*.]google.com and [*.]google.cr in your cookie exceptions, and ensuring the setting for chrome://settings/content  is:
* Keep local data until you quit your browser
* Block third-party cookies and site data

where cr (in google.cr above) is your country code

cookie exceptions are here: chrome://settings/contentExceptions#cookies

Othere relevant settings:
on chrome://settings/  have this set:
On Startup: Continue Where you left off

2. upgrade from chromium-dev 54.0.2804.0_r923.5f2924f-1
to 54.0.2814.0_r2922.7077c9c-1

on Manjaro linux:
upgraded chromium-dev (54.0.2804.0_r923.5f2924f-1 -> 54.0.2814.0_r2922.7077c9c-1)

2. start chromium and see that your twitter and gmail accounts are still logged in
3. quit chromium (eg. shutdown system)
4. start chromium and see that your session cookies are gone and you are totally logged off gmail and twitter - gmail doesn't even remember your email username as having ever been logged on this PC.

5. go to chrome://settings Privacy->Content Settings -> Manage Exceptions
aka chrome://settings/contentExceptions#cookies
and see that all those [*.]gmail.com style exception are transformed into: http://gmail.com:80 ones

I think this is the culprit.

What is the expected behavior?
cookies are maintained after chromium restart (this worked before update!)

What went wrong?
cookies are seemingly gone or inaccessible therefore sites don't know I am already logged on to them and act as if I'm a new user.

Did this work before? Yes in this chromium version 54.0.2804.0_r923.5f2924f-1   the latest used commit must be this: 5f2924f

Chrome version: 54.0.2814.0  Channel: n/a
OS Version: 4.7.0-rc6-ga99cde4 #1 SMP PREEMPT
Flash Version: none

I'll post a new comment if, after posting this and restarting chromium, my newly added [*.]gmail.com exception rules got transformed into http://gmail.com:80 again! (did not yet test this)
 
Screenshot_2016-07-31_06-19-39.png
87.5 KB View Download
I did a chromium restart and the cookies are still here and my newly added [*.]google.com was kept as is.
I'll do a system restart, since this is what I did last time that caused this in the morning.

Oh my mistake above if you see [*.]gmail.com please use [*.]google.com instead ! (I did have just gmail.com too though, see screenshot)


chrome://version

Chromium	54.0.2814.0 (Developer Build) (64-bit)
Revision	7077c9c09ee068bfeb7623c8ac58e7a21b7143c8-refs/heads/master@{#408870}
OS	Linux 
JavaScript	V8 5.4.301
Flash	
User Agent	Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/54.0.2814.0 Safari/537.36
Command Line	/usr/lib/chromium/chromium --disk-cache-dir=/tmp/chromiumcache --disable-sync-preferences --disable-plugins --cipher-suite-blacklist=0x0001,0x0002,0x0004,0x0005,0x0017,0x0018,0xc002,0xc007,0xc00c,0xc011,0xc016,0xff80,0xff81,0xff82,0xff83 --disable-component-extensions-with-background-pages --disable-background-networking --disable-internal-flash --disable-bundled-ppapi-flash --disable-default-apps --ssl-version-min=tls1 --disallow-autofill-sync-credential --disable-device-discovery-notifications --no-pings --disable-media-source --disable-ntp-other-sessions-menu --disable-prefixed-encrypted-media --disable-touch-adjustment --disable-views-rect-based-targeting --disable-webgl --disable-account-consistency --enable-async-dns --enable-deferred-image-decoding --enable-download-resumption --enable-drop-sync-credential --disable-material-design-ntp --disable-new-avatar-menu --disable-new-profile-management --enable-offline-auto-reload-visible-only --disable-offline-auto-reload --enable-offline-load-stale-cache --enable-one-copy --enable-panels --disable-password-generation --enable-permissions-bubbles --disable-extensions-on-chrome-urls --disable-pinch-virtual-viewport --disable-pinch --enable-quic --disable-save-password-bubble --enable-session-crashed-bubble --disable-settings-window --use-simple-cache-backend=off --disable-smooth-scrolling --disable-sync-app-list --disable-sync-synced-notifications --enable-tcp-fastopen --disable-touch-editing --enable-web-based-signin --disable-zero-copy --enable-harfbuzz-rendertext --enable-impl-side-painting --enable-lcd-text --num-raster-threads=4 --disable-origin-chip --disable-overlay-scrollbar --remember-cert-error-decisions=-1 --enable-search-button-in-omnibox-always --disable-spelling-auto-correct --tab-capture-downscale-quality=fast --tab-capture-upscale-quality=fast --touch-events=disabled --wallet-service-use-sandbox=0 --enable-gpu-vsync --show-component-extension-options --disable-gpu-rasterization --disable-hyperlink-auditing --enable-vertical-tabs --disable-audio-support-for-desktop-share --disable-gpu --wm-user-time-ms=1797829 --flag-switches-begin --flag-switches-end --window-depth=32 --x11-visual-id=97
Executable Path	/usr/lib/chromium/chromium
Profile Path	/home/z/.config/chromium/Default
Variations	16e0dd70-3f4a17df
ba3f87da-92cc81ec
f049a919-3f4a17df
43d0dd1e-3f4a17df
9e243dd-3f4a17df
64cbdfc2-3f4a17df
f5dd6118-2f5721af
b7786474-d93a0620
7382e39a-3f4a17df
868bda90-3f4a17df
4ea303a6-3f4a17df
9736de91-3f4a17df
30e679f-3f4a17df
ad6d27cc-3e870323
867c4c68-3f4a17df
d747916f-d747916f
fe05be5f-4ad60575
It still works even after computer restart!
Therefore I do not know what made those exceptions from [*.]google.com into http://google.com:80
Something did! But I don't know what. Was it done only one on chromium version change/upgrade? (but had effect only on next chromium restart then)

I'll upgrade chromium next to see if it happens on version change.
upgraded chromium-dev (54.0.2814.0_r2922.7077c9c-1 -> 54.0.2815.0_r2934.ca0e8af-1)

still cannot reproduce.
Therefore this must've been a one time thing. Or it highly depends on the current profile state and then upgrading from (54.0.2804.0_r923.5f2924f-1 -> 54.0.2814.0_r2922.7077c9c-1) like I did in OP.

Sorry for the noise. If you think I should try something else let me know. Always open to squashing them buggies.

Cheers.
Project Member

Comment 4 by sheriffbot@chromium.org, Jul 31 2017

Status: Archived (was: Unconfirmed)
Issue has not been modified or commented on in the last 365 days, please re-open or file a new bug if this is still an issue.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

Sign in to add a comment