This is not a new topic. I have been reading all about it even over at Reddit. But what is puzzling me is why this is happening at all. It only started about a day ago. So now I log into my computer and then when I go to run my Vivaldi browser I have to put my password in again. How is this “security related”? I mean if someone got into my computer (which will never happen because I am the only one using it) then they already know my password.
I read all about possible “solutions”, some of which I will not do like using Seahorse to change the password. I also read suggestions about deleting certain files or the keyring itself. But what is the cause of this issue to begin with? It is only happening on the older computer…
None of these things… Why would it not be needed one day and the next day this nonsense pops up all of a sudden. Also someone must know the way to get rid of it besides using Seahorse. I guess I can ask my son tomorrow. Seems like he figured it out the last time it happened.
It really is more of an inconvenience than anything. But it truly seems stupid to have to put your password in twice just to use a browser that you always use…
Also I was trying to look up the dnf history to see if it was something that happened in a recent update, but all dnf history info came up with was Strawberry… I think before that there might have been Network Manager or something like that. But both computers get updated daily so why is it happening on one computer and not the other?
Alright I asked my son and he didn’t really have any idea. He says I am guessing about it being caused by the Network Manager update and he is right about that.
I am on the newer computer now. That prompt is not showing up. So when I go to Accessories in the menu and then choose Passwords and Keys, it comes up and under Passwords there is a folder that is unlocked called Login… On the older computer there is the same folder but it is locked. How can this be? What is going on? Otherwise everything else looks exactly the same once I unlock that folder.
BTW, I also don’t use my browser to store any passwords…
I really am at a loss as to why this is happening and what purpose any of this keyring nonsense serves. As I said, I don’t store passwords for any sites in my browser. That is exactly the same on both computers. I have both computers set up exactly the same. Obviously there was some failure that occurred because this has only recently started happening.
When I go to Passwords and keys I can just put my password in there and everything works just fine. There is a listing for Vivaldi inside that Login folder. Probably why I get the message when attempting to run Vivaldi. Firefox would probably run without the prompt.
I really don’t want to have to change the password because it matches my login password. I could just leave it blank as well, but that is more of a workaround than an actual solution. There is an option in Passwords and Keys to change the password so it seems that Seahorse would not even be needed if I chose to go that way. I am still looking for that “Sync and Publish” option that I saw yesterday. I clicked on it but it didn’t seem to do anything at all.
Well, now I am even more confused. I just booted up the second computer and decided to look at Preferences in the Passwords and Keys. I found that menu. It was at the top next to the words “Passwords and Keys”… And BTW on the newer computer it said that the Login folder was locked but all I had to do was click on unlock and I didn’t even have to enter any password…
So here is a screenshot of what comes up after you choose Preferences from the menu.
Does any of this matter? Should I just leave the password blank for the keyring and be done with it. Would seem to be a lot simpler. Also it makes me think that is what I already did on the newer computer but I can’t remember…
Finally just said F it and changed the login keyring password to nothing. Life goes on… I am the only one who uses this computer and I don’t really store any passwords so that was the easiest thing to do. I really don’t consider it a solution because it doesn’t get to the core of why the error started in the first place. But at least it is a workaround.
