Chromium forgeting its cookies at random intervals

Hi all, I have a very weird, moderately annoying issue. My Chromium browser clears/forgets some of its cookies at random intervals (about once a week) and i have to login again everywhere, including here. Google is no help here, because the first 100 Million results are for clearing cookies automatically on exit (which is not enabled).

The cookies are not expired, because there are persistent ones among them (like cookie tracking settings… of sites that I manage so i know they are persistent). On many sites i also know the re-login policy, at least on 2 of them the cookie life is one month, so anything short of that is a “bug”. The weird thing is, not everything is cleared, i think. If i then open the settings, i still see some “site data” to clear, so not everything is cleared.

Has anyone any idea?

Here are the browser customizations:

Flags
--disk-cache-dir=/dev/null 
--media-cache-dir=/dev/null

#enable-quic
#enable-system-notifications
#allow-insecure-localhost
#enable-force-dark
#read-anything (disabled)
#permission-chip
#chrome-labs
#enable-tab-audio-muting
#quick-intensive-throttling-after-loading
#heuristic-memory-saver-mode (balanced)
#memory-saver-savings-reporting-improvements


Extensions:
Chrome Remote Desktop
Keep Awake
User-Agent Switcher for Chrome
enhanced-h264ify
Picture-in-Picture Extension (by Google)
Google Docs Offline
uBlock Origin

The only things that in my opinion can remotely have some impact, are the adblocker and the disabled caching. But i use Ublock origin since about 5 years on many different computers and browsers and it never happened before.
And if the cache was the problem, how does everything works flawlessly for a week or two then?

Hi there. A couple of thoughts. Have you tried uninstalling Chromium using the -Rns command & doing a complete reinstall? Also, are you open to using Brave? I utilise it & find it a very good browser & takes care of ad-blocking, fingerprinting etc - all of which can be set to off/moderate/severe for every site you visit. Either way, I trust you sort this irritating problem soon.

I think if there is something wrong, it should be in the .config and not in the app itself, so reinstalling is probably not the solution.
I have to check out brave.

Somewhat related can be my current ISP situation, it is a big pool of IP addresses that change often, so i “jump through different cities” from the point of view of the websites. Which can trigger some security. Except, that is certainly not the case with some of the used sites, and i think (not sure) i had that problem also in Germany on a completely different ISP.

There is one thing in the journal that was different when that happened, but it does not sound very logical to be the problem, and i have to wait until it happens again, maybe it was a coincidence.

00:04:05 chromium: [1813:1813:0816/000405.159878:ERROR:chrome_browser_cloud_management_controller.cc(162)] Cloud management controller initialization aborted as CBCM is not enabled.

The primary suspect for me is uBlockOrigin for now.

After so much time, i now at least have some idea what is happening and can reproduce the bug every time. It seems to be a bug either in gnome-keyring and/or chrome (or maybe the portals).

The thing is, if chromium is not started, and i open for example pamac (but the same thing happens with all flatpaks) and click a hyperlink from there, like a web site in a description of the app, it opens in a new chromium window. I then close it.
The next time chromium is manually started from me via the launcher icon, it has forgotten all the logins. On its start, it prints to the journal

gnome-keyring-daemon[951]: asked to register item /org/freedesktop/secrets/collection/login/1, but it's already registered

If however, there is already running a browser window in the background when i click a link in flatpak or pamac (maybe every other app, have still not tested), nothing bad happens and the journal says

xfce4-web-browser.desktop[5770]: Opening in existing browser session.

Cookies are not stored in the keyring. That can’t be it.

There is no logic in it, but it is the only thing appearing in journal -f, and it is reproducible.

I am happy to announce, it does not happen anymore. I did not happen for several months now, so today i tried to deliberately reproduce it, and it is not reproducible anymore. And the journal message is still happening, so it was not that.

So it probably was a bug in chromium itself. Or some other package, but it seems patched now, so i am closing without a real solution because i am a bad boy :slight_smile:

This topic was automatically closed 3 days after the last reply. New replies are no longer allowed.