On 13.10.2023 19:11, cagsm wrote:

Support,

15.5, todays or recent chromium release 118.0.5993.70

just yesterday I used the release prior to that chromium, and the default chromium starting page already offered my google account with the user logo and gmail would automatically display my content.

This is similar to what I observed after having replaced snap Chromium with Debian package. It stopped automatically login into Google account. It still remembers my user name, but I have to explicitly log in and provide password. I still do not know why or what changed. This happened a couple of months ago and currently I have Chromium 117.

todays chromium triggers the kde wallet (chromium wants to access kdewallet) and i need to enter the kdewalletmanager credential first to allow the app to access its own content inside the wallet. thats at least how i understand the stiation.

Are you using automatic login in openSUSE?

what i always wondered, the chromum settings about passwords/credentials

...

chrome://password-manager/passwords

was empty before and is still empty in this todays chromium release. but the kdewalletmanager shows kdewallet content with a top category/folder in the tree named "Chromium Keys" and it has a password sub area and that has a chromium safe storage subelement.

now i wonder if all the passwords never will appear inside chromium gui itself or what went wrong to begin with and why todays update cleared away maybe some session, tokens, cookies or whatnot.

should chromium actuallly store and present visibly the passsword stuff inside its own gui?

Chromium normally should automatically chose password store and you should see stored passwords. If they are empty, something went wrong and Chromium selected the wrong backend. One possible reason is if Chromium detects libsecret (which IIRC is supported by KWallet). I am not sure whether it is compatible with native KWallet. https://chromium.googlesource.com/chromium/src/+/refs/heads/main/docs/linux/...