Gnome keyring: applications prompt to make default keyring but there are many "un"locked ones that were made but they are all locked
OK so I think I solved it on my own, but I do think it is causing issues with other programs as well so I am posting this.
My system:
Samsung CB 4
OS: q4os Aquarius (debian bookworm)
So the issue has been present for a while, everytime I would open evolution mail either from flatpak or the repos, I would get prompts about timeouts, secrets, and an application creating the default keyring, (that went unnoticed because of all the other prompts in evolution that were popping up) etc. I also noticed Brave also prompted to make a default keyring when it was started as well, and slack to (not sure if slack uses the keyring though). While trying to find the issue with evolution here in this thread: evolution-ews#268 (closed) I realized that I always clicked on the keyring notification to continue without a password, and then I clicked on the warning that popped up, and realized I had done this like 40 or more times.
I downloaded seahorse to see what was going on, and I noticed all the default keyrings that were there. Then Realized that all of them were locked even though I never gave them a password. This means applications could not log into emails, or access stored passwords correctly. I deleted all the extra default keyrings (and the passwords stored within) before I caught on that they were not suppoed to be locked. So on the last one I changed the password to my OS log in password instead of choosing no password. Now I get a single prompt to unlock the key ring when I open a program that uses it. I use this along with gnome-online-accounts as well. Doing this messed up the accounts I had in gnome-online-accounts, so I had to remove them, then re-add them. And I no longer have 50 default keyrings, but I also noticed I have less issues with evolution now to. I am assuming not being able to access the passwords stored caused issues with emails and calendars loading.
I have it fixed for now because I gave the default keyring a password, then erased it with seahorse, now it asks to unlock it and I put in my password and no further issues. Best I can explain it, sorry. But I think this may be the root issue for a lot of people and a lot of other projects.