Originally Posted by Dutchy
I also have one pc where gnome-keyring/seahorse is a pain in the butt, but it is not related to chrome but to gmail. In my case it keeps complaining the password is wrong even after I recreate the keyring and make damn sure it is right. I can't find much info on how this needs to be debugged, the only thing is compiling seahorse with some debug flags.
If it's asking you to unlock the login/default keyring then it's a similar problem to the OP's.
If however it's complaining that the gmail account password is incorrect then that's a different issue; most likely it's gnome-online-accounts (where you added your gmail account) that's complaining, I don't use gnome-online-accounts so I am not sure if there's currently a bug with authenticating gmail accounts or not.
You can try removing the account from gnome-control-center -> online accounts.
---------- Post added at 01:25 PM ---------- Previous post was at 01:20 PM ----------
Originally Posted by robertg
I did a Google search and found there are two file in one of the Gnome folders that has two file in it related to the keyring I deleted them and the problem went away. But each time I do a installation of korora on this machine it appears again
Generally speaking, you can control which password-storage backend chromium uses using the <b>--password-store</b> cli argument. Have a look at this
for more details.
You can then modify the .desktop file used to launch chromium to make the change permanent.
IMHO, using either gnome-keyring or kwallet is preferred to storing the passwords using plain text....