Chromium asking for re-login after each Plasma 5 re-login

[heyjoe]

Hi,

Recently I started experiencing this strange issue.

I logout from Plasma 5 and log back in, start Chromium and I need to login again in my Google profile as well as in all other websites. I have never seen this before and now it happens every time. Interestingly - while my openSUSE user session is active (i.e. I don't logout) there is no problem to close Chromium completely and then start it again - all site sessions are preserved.

I checked my settings (although I haven't changed them) - for Cookies I have "Allow local data to be set (recommended)" which is the default. I have "Block third-party cookies and site data" on but so far it has never been a problem. And it obviously isn't while my Plasma 5 session is active.

I browsed the web for different solutions. I recreated a new Chromium profile from scratch etc but that changed nothing. I also tried stopping the browser, deleting ~/.config/chromium/Default/Cookies and Cookies-journal and starting the browser again. Nothing seems to help.

In case that matters: I am using seahorse for passwords storage and I unlock my keyring manually after each login to Plasma 5, before starting any browser. It has been this way for a long time and never caused any issues.

I wonder what might be happening.

Any ideas?

[nrickert]

I'm not having a problem here.

I mainly use "firefox". But when I do start "chromium" I am already logged in.

However, I am not using "seahorse" with "chromium". I have "chromium-desktop-kde" installed, which is supposed to be use kdewallet (I'm not sure if it uses the Plasma 5 wallet or the older plasma 4 wallet). I'm guessing that, instead, you have "chromium-desktop-gnome" installed, which probably uses "seahorse".

[heyjoe]

I'm not having a problem here.

I mainly use "firefox". But when I do start "chromium" I am already logged in.

However, I am not using "seahorse" with "chromium". I have "chromium-desktop-kde" installed, which is supposed to be use kdewallet (I'm not sure if it uses the Plasma 5 wallet or the older plasma 4 wallet). I'm guessing that, instead, you have "chromium-desktop-gnome" installed, which probably uses "seahorse".

Yes, I have chromium-desktop-gnome installed.

I have no problem with Firefox and I use seahorse for storing FF credentials too (with the extension called GNOME Keyring integration). I have been using this setup with both browsers for a long time (many months). The issue with chromium is from about 2-3 weeks. I thought it was a bug but even after 2 upgrades it is still here. Plus if it works for you - it obviously isn't a bug, right?

[nrickert]

I recall seeing a bug report on chromium password handling. I didn't follow it closely, but the gist was that upstream changes affected the way that passwords were saved. I did not notice a problem. But I think the bug reporter was also using seahorse. So maybe it affected how seahorse is used. I seem to recall that the advice was to ask chromium to store passwords at google (or wherever).

[wherewolf]

Hi,

Recently I started experiencing this strange issue.

I logout from Plasma 5 and log back in, start Chromium and I need to login again in my Google profile as well as in all other websites. I have never seen this before and now it happens every time. Interestingly - while my openSUSE user session is active (i.e. I don't logout) there is no problem to close Chromium completely and then start it again - all site sessions are preserved.

I checked my settings (although I haven't changed them) - for Cookies I have "Allow local data to be set (recommended)" which is the default. I have "Block third-party cookies and site data" on but so far it has never been a problem. And it obviously isn't while my Plasma 5 session is active.

I browsed the web for different solutions. I recreated a new Chromium profile from scratch etc but that changed nothing. I also tried stopping the browser, deleting ~/.config/chromium/Default/Cookies and Cookies-journal and starting the browser again. Nothing seems to help.

In case that matters: I am using seahorse for passwords storage and I unlock my keyring manually after each login to Plasma 5, before starting any browser. It has been this way for a long time and never caused any issues.

I wonder what might be happening.

Any ideas?

Are you getting the orange triangle with keyring is that what you mean when you open Chromium

[heyjoe]

I recall seeing a bug report on chromium password handling. I didn't follow it closely, but the gist was that upstream changes affected the way that passwords were saved. I did not notice a problem. But I think the bug reporter was also using seahorse. So maybe it affected how seahorse is used. I seem to recall that the advice was to ask chromium to store passwords at google (or wherever).

Do you remember where you saw that bug? On openSUSE bugzilla or somewhere else? I do sync my passwords with my google account but that has nothing to do with the case I think. Chromium always needs to have a local copy of the passwords too. There is no option to keep passwords only remotely and it makes sense.

Are you getting the orange triangle with keyring is that what you mean when you open Chromium

No. I am just being asked to login again on each site on which I previously was. It can be quite annoying for sites on which use 2-step verification with SMS etc. The whole thing sounds like cookies are being cleaned up when logging out of Plasma 5 which is weird because they are persistent if I only exit chromium. Also such thing is against what is in chromium settings. Really strange.

Facebook also asks me to confirm my browser again as if I am logging in from a new device which I never used.

[nrickert]

Do you remember where you saw that bug? On openSUSE bugzilla or somewhere else?

That was opensuse bugzilla. I browse the mailing list daily. This was probably back in May or June, though it extended over several months. It was probably related more to Tumbleweed.

[heyjoe]

I found it reported on chromium bugs and added info to the bug report. It is still unconfirmed though.

[nrickert]

The whole thing sounds like cookies are being cleaned up when logging out of Plasma 5 which is weird because they are persistent if I only exit chromium. Also such thing is against what is in chromium settings. Really strange.

As far as I know, cookies and other settings are saved in ".config/chromium". Check whether you are doing anything that would zap this directory on login or logout.

[heyjoe]

As far as I know, cookies and other settings are saved in ".config/chromium". Check whether you are doing anything that would zap this directory on login or logout.

I am not. It seems to be a bug. Cookies are stored in ~/.config/chromium/<Profile>/Cookies afaik.